[jboss-dev] AS5 testsuite failures

Adrian abrock at redhat.com
Fri Oct 19 11:02:03 EDT 2007


It's beta4 of the integration project not the AS.

On Fri, 2007-10-19 at 16:01 +0100, Andrew Dinn wrote:
> Hi Adrian,
> 
> I notice that you mentioned a 5.0.0.Beta4 release being in progress. I 
> have been using AS trunk to get some of the WS functionality that was in 
> Beta3 but missing from Beta2. Is there a stable(-ish :) tagged Beta3 
> release I can use? I don't see anything in the AS svn tags directory.
> 
> regards,
> 
> 
> Andrew Dinn
> -----------
> 
> Adrian wrote:
> > I checked out the Beta4 tag and built the assembly.
> > 
> > I've added it to the repository, so we're just waiting
> > for the mirroring to catch up so we can test it.
> > 
> > For some reason the assembly name has been changed to
> > jboss-integration-parent.jar ??????
> > 
> > build/pom.xml
> >   <artifactId>jboss-integration-parent</artifactId>
> >   <version>5.0.0.Beta4</version>
> > 
> > I've got no idea what is going on with this crap?
> > 
> > Why can't people just leave things alone when they are
> > working? Or if you are going to play around, do a proper
> > standup test like a full clean checkout!
> > 
> > On Fri, 2007-10-19 at 15:56 +0200, Adrian wrote:
> >> Somebody's broken the integration project release.
> >>
> >> There should be a jboss-integration.jar maven assembly.
> >> See build/build-distr.xml
> >>
> >> It was there in beta3
> >> http://repository.jboss.com/jboss/integration/5.0.0.Beta3/component-info.xml
> >>
> >> but the structure of this release has been totally changed in beta4
> >> http://repository.jboss.com/jboss/integration/5.0.0.Beta4/component-info.xml
> >>
> >> There's no assembly any more?????
> >>
> >> On Fri, 2007-10-19 at 16:23 +0300, Dimitris Andreadis wrote:
> >>> The testsuite runs of AS5 fail:
> >>> https://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15-noip/95/
> >>>
> >>> It cannot instantiate the transaction manager due to missing org/jboss/tm/JBossXATerminator.
> >>>
> >>> It's weird because the 'all' config boots manually.
> >>>
> >>> The missing class is in the jboss-integration.jar
> >> It will boot manually if you previously downloaded the
> >> integration beta3 release.
> >> The build-thirdparty.xml does not delete old jars so
> >> you will still have it in thirdparty.
> >>
> >> It won't build manually if you "rm -rf thirdparty" :-)
> 
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx




More information about the jboss-development mailing list