[Jboss-dev-forums] [Design of JBoss Build System] - Re: Requirements - Top level build - versioning

[<ad...@jb...>]

The problem with pegging a version in the top level build
is that the components will move forward to later versions
while the top level build remains on an old version.

There is a conflict here:
1) You need the pegging to communicate how a conflict is being resolved
to other developers.
2) You need the pegging at release time to unambigously describe the release.
3) You also need to be aware that it needs unpegging later.
4) You can later change the release to record that although it was originally
tested with log4j-1.2.8, it also works just as well with 1.2.9

This was my argument against holding versions in the build files
and instead recording which artificats have been tested twith which versions
of a dependency.
Who is going to (or even knows when) a version should be unpegged.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878283#3878283

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878283