Jukka Zitting wrote:
Ah, perhaps Maven is using a single timestamp for the entire
multimodule build and deploy process. The sequence numbers are managed
in the maven-metadata.xml files on the snapshot repository. Each
component has it's own sequence number, which will get out of sync
from other component sequences whenever someone deploys a snapshot of
just that component or for example if the multimodule build on the
Jackrabbit zone fails after already deploying a part of the
components.
Yes, that sounds reasonable. I wasn't quite sure where the sequence number came
from, but that explains the behaviour.
> Basically I believe Maven should resolve "SNAPSHOT" to the latest
> build in the repository and internally still use "SNAPSHOT" as the
> version, but I might be mistaken. Perhaps we should replace the
> ${version} variables with actual "1.4-SNAPSHOT" version labels in the
> dependencyManagement part of the parent POM. I'll look into that.
That should actually solve the problem. The problem here is that you
have to
update the parent pom on each release.
That's a small price to pay, as I've in any case used "perl -i -pe
s/x.y-SNAPSHOT/.../" to do the version updates.
Ok then. Go for it ;)
Cheers,
Christoph
