[jboss-dev] Maven Complaints [Was: Broken builds]

[Ovidiu Feodorov]

Andrew Lee Rubinger wrote:
>
> With the new mandate set to remove all snapshots from the AS 
> component-matrix, we can expect to see reliably reproducible builds. 
> Snapshots were just as horrid with the older Thirdparty setup.
>
I know there was an older discussion on snapshots, but I don't remember 
the conclusion.

Regardless of the dependency management/build tool, if one handles 
artifacts the same way it handles a source code file, in that you never 
"re-tag", then it shouldn't be any problems, or at least I never had any.

Assuming that your sub-project is producing an artifact a.jar and it 
publishes it as a.jar version r100 (the SVN revision number), that r100 
will "forever" stay in the artifact repository, unchanged, so any 
dependents will use that specific "snapshot" unless they explicitly 
declare they want another one.

If I patch my artifact, I release and publish r105 (or whatever), while 
r100 is still available in the repository and all "outdated" dependents 
still have their dependency satisfied and they don't break.

How can this not work?