Hi Lachlan,
Lachlan Deck wrote:
> On 09/07/2008, at 2:16 PM, Anjo Krank wrote:
>
> Yep, I'm not sure why maven's pom insists on having the version of a
> parent defined. I would have thought it could be inherited. Swings and
> roundabouts.
>
One reason: You have to declare the version because your parent pom
doesn't need to be on filesystem. You don't have to download an entire
project to work on a single module. You can get a submodule and
successfully build it if the parent POM is on your local repository or
Repository Manager (of course you have one).
Another reason: a child POM can have a parent POM of an old version. For
example, current parent POM has version 1.0-SNAPSHOT. You can have a
submodule pointing to the parent of 0.9 release.
That is why 'mvn clean install' is so important. This way you can rely
on things that are in your repository.
Cheers,
Henrique
This archive was generated by hypermail 2.0.0 : Wed Jul 09 2008 - 23:38:50 EDT