Re: Maven 2 project structure with wicket-parent

[Alastair Maw]

Hi Martijn,

You've evidently been bitten by this and have a set-up that fixes the 
issue and works, and are therefore reluctant to change it. I respect 
that and shall now politely stop haranguing you, even if I think I know 
better. ;)

Regarding Bamboo going the way of Continuum, I'd like to note that if 
people have their build environments set up incorrectly to link against 
the wrong rt.jar version, then they have the potential to push JDK 5 
code into the 1.4 codebase regardless of how Maven 2 is set up. One 
simply doesn't run Maven 2 over the Wicket projects as a developer all 
that much as the dependencies don't change that often.

It's also a pain having to set your JAVA_HOME and paths up specially 
each time, so I'd guess most people don't tend to bother. Having a 
continuous integration server that picks up these issues is therefore 
useful and important regardless. Kudos to people for chasing licenses 
and getting it all setting it up. :-)

Thanks,

Al