[jboss-dev] Microntainer CR releases - proper job

[Adrian Brock]

On Fri, 2008-09-05 at 10:56 +0200, Adrian Brock wrote:
> When doing a release, you should always check
> it has the most up-to-date dependencies
> (or at least is using the versions used by
> JBossAS) and that the mvn dependency:tree is not
> using spurious dependencies due to changes
> in dependent poms.
> Otherwise the project's unit tests are not
> going to find problems that will occur
> when the release is included in JBossAS.

As an example:

The JBossCL CR1 wasn't built with the jboss-man CR1
release, which was the point wasn't it?

[ejort at warjort classloading-vfs]$ mvn dependency:tree | grep jboss-man
[INFO] +- org.jboss.man:jboss-managed:jar:2.0.0.Beta16:compile

It also has the wrong version of "integration" which should be CR2

[ejort at warjort classloading-vfs]$ mvn dependency:tree | grep
jboss-classloading-spi
[INFO] |  |  \- org.jboss:jboss-classloading-spi:jar:5.0.0.Beta4:compile

MDR which should be Beta17 (really the non-existant CR1)

[ejort at warjort classloading-vfs]$ mvn dependency:tree | grep jboss-mdr
[INFO] |     \- org.jboss:jboss-mdr:jar:2.0.0.Beta16:compile

VFS which should be Beta22 (really the non-existant CR1)

[ejort at warjort classloading-vfs]$ mvn dependency:tree | grep jboss-vfs
[INFO] +- org.jboss:jboss-vfs:jar:2.0.0.Beta21:compile

etc.
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx