Reliance tests failure

[alesj]

OK, a bit off the working topic.
But I noticed that Reliance subproject is failing due to using old Reflection.

Somehow the Beta11 is creeping in all the time.
I tried a few exclusion hacks, but w/o success.

Reliance points to Kernel, Kernel points to Reflection.
Both are set to snapshot and I've deployed them yesterday into the repo.
But there are many other places where it could slip in.

What did you use to find these problems?
And is there anything except direct exclusion that might help.
Or anything other than a complete Maven2 rewrite. :-)

[adrian.brock]

mvn dependency:tree

[alesj]

mvn dependency:tree

C:\projects\microcontainer\reliance>mvn dependency:tree
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] JBoss Reliance Build
[INFO] JBoss Reliance Identity
[INFO] JBoss Microcontainer Reliance Rules
[INFO] JBoss Microcontainer Reliance jBPM
[INFO] JBoss Reliance Aggregator
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Required goal not found: dependency:tree
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Tue Mar 18 12:15:26 CET 2008
[INFO] Final Memory: 2M/5M
[INFO] ------------------------------------------------------------------------

OK, a stupid question, but how do you update this dependency plugin?
I tried putting -cpu, -up all over the place, w/o any success. ;-(

[adrian.brock]

Ask in the build forum or try the old faithful... blowing away your local repository. :-)

The build I've got for reliance shows reflection coming the JBossXB dependency

[INFO] [dependency:tree]
[INFO] org.jboss.reliance:jboss-reliance-jbpm:jar:2.0.0-SNAPSHOT
[INFO] +- jboss:jbpm:jar:3.1.1:compile
[INFO] \- org.jboss.microcontainer:jboss-kernel:jar:2.0.0-SNAPSHOT:compile
[INFO] +- org.jboss.microcontainer:jboss-dependency:jar:2.0.0-SNAPSHOT:compile
[INFO] | \- org.jboss:jboss-mdr:jar:2.0.0-SNAPSHOT:compile
[INFO] \- org.jboss:jbossxb:jar:2.0.0.CR7:compile
[INFO] +- jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile
[INFO] +- org.jboss:jboss-common-core:jar:2.2.3.GA:compile
[INFO] +- org.jboss:jboss-reflect:jar:2.0.0.Beta11:compile
[INFO] +- apache-xerces:xercesImpl:jar:2.9.1:compile
[INFO] +- wutka-dtdparser:dtdparser121:jar:1.2.1:compile
[INFO] +- javax.activation:activation:jar:1.0.2:compile
[INFO] \- javax.xml.bind:jaxb-api:jar:2.1:compile
[INFO] \- javax.xml.stream:stax-api:jar:1.0-2:compile

or

mvn dependency:tree -Dverbose=true

[INFO] [dependency:tree]
[INFO] org.jboss.reliance:jboss-reliance-jbpm:jar:2.0.0-SNAPSHOT
[INFO] +- jboss:jbpm:jar:3.1.1:compile
[INFO] \- org.jboss.microcontainer:jboss-kernel:jar:2.0.0-SNAPSHOT:compile
[INFO] +- org.jboss.microcontainer:jboss-dependency:jar:2.0.0-SNAPSHOT:compile
[INFO] | \- org.jboss:jboss-mdr:jar:2.0.0-SNAPSHOT:compile
[INFO] | +- (org.jboss:jboss-reflect:jar:2.0.0.Beta11:compile - omitted for duplicate)
[INFO] | +- (jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile - omitted for duplicate)
[INFO] | \- (org.jboss:jboss-common-core:jar:2.2.3.GA:compile - omitted for duplicate)
[INFO] \- org.jboss:jbossxb:jar:2.0.0.CR7:compile
[INFO] +- jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile
[INFO] +- org.jboss:jboss-common-core:jar:2.2.3.GA:compile
[INFO] +- org.jboss:jboss-reflect:jar:2.0.0.Beta11:compile
[INFO] | +- (jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile - omitted for duplicate)
[INFO] | \- (org.jboss:jboss-common-core:jar:2.2.3.GA:compile - omitted for duplicate)
[INFO] +- apache-xerces:xercesImpl:jar:2.9.1:compile
[INFO] +- wutka-dtdparser:dtdparser121:jar:1.2.1:compile
[INFO] +- javax.activation:activation:jar:1.0.2:compile
[INFO] \- javax.xml.bind:jaxb-api:jar:2.1:compile
[INFO] +- javax.xml.stream:stax-api:jar:1.0-2:compile
[INFO] \- (javax.activation:activation:jar:1.1:compile - omitted for conflict with 1.0.2)

[alesj]

So what's the solution?
A question of universal Maven transition dependencies. :-)

To explicitly apply Reflection?
But then I can do this for every artifact. :-(

Even if there was some mechanism that would say that the last version (according to OSGi versioning) should be used, how would it treat snapshots?

[alesj]

"alesj" wrote:
So what's the solution?
A question of universal Maven transition dependencies. :-)

Previous related posts:
- http://www.jboss.org/index.html?module=bb&op=viewtopic&t=131467
- http://www.jboss.org/index.html?module=bb&op=viewtopic&t=131413