[jboss-dev] jbossxb at 2.0.0-SNAPSHOT or 2.0.0.CR5

[Adrian Brock]

Good luck :-)

Judging by what I'm seeing (downloading it for the first time),
there's all sorts of rubbish in the dependencies.

I've already seen xerces 2.2.0 and 2.4.1 being downloaded
jboss-test 1.0.3 and 1.0.5
and a couple of different versions of the jaxb apis.

I think I need to buy a new disk :-)

What's ironic is that the only way I've managed to make
Maven usable/stable is to blow away my whole maven repository
on a regular basis (especially before doing releases!)

If I don't do that, it starts doing weird things
that aren't reproducable by anybody else or even
myself once I've deleted the repository.

At this rate its going to take me "hours" to repopulate it
for the appserver build when I do that. :-(

Time to investigate how to use different local repositories
for different builds.

On Thu, 2008-03-13 at 19:50 +0200, Dimitris Andreadis wrote:
> I'll go through root pom.xml to see what are the differences with build/build-thirdparty.xml 
> when it was removed.
> 
> Adrian Brock wrote:
> > JBossXB is currently at 2.0.0.CR7, why use a snapshot?
> > 
> > The error message indicates some other problem anyway
> > since that class has been in JBossXB "forever".
> > 
> > e.g. did you see Alex's comment about Xerces 2.6.1 getting
> > downloaded by maven instead of 2.9.1?
> > 
> > Looks like a spurious transient dependency to me.
> > 
> > I've fixed a lot of this kind of thing in the MC build
> > use 
> > 
> > mvn dependency:list
> > 
> > and fix them
> > 
> > e.g. Don't let jboss-test choose an older version
> > of jboss-common-core, etc....
> > 
> >     <dependency>
> >       <groupId>org.jboss</groupId>
> >       <artifactId>jboss-test</artifactId>
> >       <exclusions>
> >         <exclusion>
> >           <groupId>jboss</groupId>
> >           <artifactId>jboss-common-core</artifactId>
> >         </exclusion>
> >         <exclusion>
> >           <groupId>jboss</groupId>
> >           <artifactId>jboss-common-logging-spi</artifactId>
> >         </exclusion>
> >       </exclusions>
> >     </dependency>
> > 
> > 
> > On Thu, 2008-03-13 at 19:37 +0200, Dimitris Andreadis wrote:
> >> The root AS5 pom.xml refers to jbossxb 2.0.0-SNAPSHOT. The removed 
> >> build/build-thirdparty.xml was referencing 2.0.0.CR5 instead.
> >>
> >> Do we need to revert? The server fails to start with the snapshot:
> >>
> >> 18:52:41,578 INFO  [ServerImpl] Starting Microcontainer, bootstrapURL=file:/X:/c
> >> vs/jboss-public/jboss-head/build/output/jboss-5.0.0.CR1/server/all/conf/bootstra
> >> p-beans.xml
> >> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/xb/binding/
> >> UnmarshallerFactory
> >>          at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.<clinit>(Bas
> >> icXMLDeployer.java:52)
> >>          at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java
> >> :98)
> >>          at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:
> >> 398)
> >>          at org.jboss.Main.boot(Main.java:209)
> >>          at org.jboss.Main$1.run(Main.java:544)
> >>          at java.lang.Thread.run(Thread.java:595)
> >> 18:52:41,593 INFO  [ServerImpl] Runtime shutdown hook called, forceHalt: true
> >> 18:52:41,593 INFO  [ServerImpl] Shutdown complete
> >> _______________________________________________
> >> jboss-development mailing list
> >> jboss-development at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jboss-development
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx