JavaZone is Scandinavia's biggest meeting place for software developers, and one of Europe's most important. JavaZone has been described as a high-quality, independent conference, and is a forum for knowledge exchange, recruitment and branding.
Some 40 large and mid-sized businesses exhibit their products and services in a separate exhibition space, while more than 90 presentations are given in the conference facilities. Each year, around 2,300 conference tickets are sold. This means that, over the two days the conference lasts, more than 200,000 hours of expertise are delivered. When you add to this the many informal discussions that take place at stands and between attendees, JavaZone stands out as a tremendous arena for knowledge transfer.
Computas is contributing to the agenda as follows:
Why We Should Start Tagging Our Code
- Room: Sal 7
- 10:30 - 10:45, 08.09.10
- Speaker: Filip van Laenen
About: Most languages allow source code to be organized in smaller units, like e.g. packages in Java. Usually, these units can be organized in their turn, thus creating a hierarchy of packages and classes, interfaces, enumerations, etc... In Java, these packages are closely tied to the file system's directory structure, which may not always be an advantage.
Erfaring med konvertering fra CVS til Mercurial i stort Javaprosjekt
- Room: Sal 7
- 09:00 - 09:15, 09.09.10
- Speaker: Geir Andrè Lund
Javaprosjektet jeg jobbet på hadde benyttet CVS i 6-7 år, CVS begynte å bli tungt og upålitelig, spesielt i bygge- og leveranseoppgaver. Vi måtte bytte det versjonskontrollsystemet og valget falt på Mercurial. Lyntalen tar for seg erfaringer med konvertering fra CVS til Mercurial. Hvilke fallgruver en kan møte på, hvordan den distribuerte modellen endrer arbeidsflyt til utviklere, enten de vil eller ikke, og mine tips til andre som har planer til å bytte til den distribuerte modellen av kildekodeversjonering.
Enhance your Maven plugins with Groovy
- Room: Sal 7
- 13:00 - 13:15, 09.09.10
- Speaker: Harald Søvik
Groovy lends extra strengths to the Java programming language. These strenghts can be actively used to enhance Maven plugins. These plugins may often be quick and dirty, written by developers to solve some very specific problem. If they get adopted by projects, it should be compulsory to ensure their quality by code review and 100% test coverage.
Many of the dirty fragments of code can be rewritten with Groovy to become both easier to read and maintan, and easier to cover with unit tests.
This presentation sums up the experiences of having groovy-ised 3 (proprietary) enterprise Maven plugins: cxjboss, cxbuildnumber and mtregelverk.