My original question was

>>1. How to distinguish snapshot build versions correctly? So that one 
>>snapshot build would not overwrite previous one in the repository.
>
>You don't, that's not the purpose. If you truly care about a particular
>snapshot version, then it should have been a release. It's meant only
for >looking at the latest version of unreleased code.

And I was confused with your answer. I believe it is still possible to
assign a unique version with -SNAPSHOT suffix to each snapshot build.
Thus we can distinguish snapshot builds and still pack them to the
snapshot repository. 
I think now that maven profiles could also be used to differentiate
target repositories depending on the build type.

The feature I miss (aside of my incompetence to answer a question why
maven is limited to only release and snapshot build types) is an
automatic project version update in the pom file that gets deployed to
the repository. Something similar to the maven 2.1 "feature" that
substitutes property references with actual values in the version
elements of the project dependencies (read about it in the adjacent
topic).


>And
>these features are not so flexible to cover all requirements of ISO
>driven development for instance. For example, need to distinguish and
be
>able to recreate everything that gets officially built. If you say,
that
>in this case we need to do only releases, then we don't need snapshots
>at all and would loose an option to use different repos for different
>build types.

I don't understand this statement. We produce releases whenever it needs
to be traceable, those releases are
deterministic and rebuildable if needed from source. In a previous
company, the snapshots were not used by qa, all
deliveries to qa where release builds. We used a 4 digit versioning
where the last number was just a build number. We
did this because it wasn't known ahead of time if a given build would
pass qa and be officially released. How you use
the system is up to your individual requirements.



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to