I'm going to try locally remoting 1.4.1_final on 4.x with jdk1.4 

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Ryan Campbell
> Sent: 28 March, 2006 23:49
> To: jboss-development@lists.sourceforge.net
> Subject: RE: [JBoss-dev] Do a clean build before committing 
> changes to build-thirdparty.xml
> 
> I'm going to test jbossws-1.0.0.CR6 with remoting-1.4.1_final 
> in jboss-head with jdk5.  If it passes, I'd like to update 
> the component-info for jbossws-1.0.0.CR6 to reflect this 
> compatibility.
> 
> If this can get resolved today vs. tomorrow, perhaps we have 
> some hope of releasing this week?
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Tom Elrod
> Sent: Tuesday, March 28, 2006 1:23 PM
> To: jboss-development@lists.sourceforge.net
> Subject: Re: [JBoss-dev] Do a clean build before committing 
> changes to build-thirdparty.xml
> 
> Ok.  I have rolled back to 1.4.0.  The web services team can 
> put back to
> 
> 1.4.1 when they are ready.
> 
> Scott M Stark wrote:
> > Start doing a clean build before committing any changes to 
> > build-thirdparty.xml to avoid this consistent problem:
> > 
> > [synchronizeinfo] Checking currentComponentRef:
> > ComponentRef{id=jboss/remoting,n
> >
> ame=jboss/remoting,filename=component-info.xml,location=null,v
> ersion=1.4
> > .0_final
> > ,[EMAIL PROTECTED],
> > version=1.4.0_final}],component=null,im
> > [EMAIL PROTECTED]/jbossws
> > atts={licensetype=lgpl} outpu
> > t=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\jbossws
> version=1.0.0.CR6
> > isLocal
> > =false [EMAIL PROTECTED]
> > output=C:\cvs\JBoss4.0\jboss-4.
> > 0.x\thirdparty\jboss\jbossws\lib\jbossws.sar type=null}, 
> > [EMAIL PROTECTED] sws-client.jar 
> > output=C:\cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\jbossws\lib\j
> > bossws-client.jar type=null}] module=null 
> > location=null},fileResolved=true} [synchronizeinfo] against 
> > newComponent:
> > [EMAIL PROTECTED]/remoting atts= 
> > {projecthome=http://www.jboss.org/products/remoting, 
> licensetype=lgpl}
> > output=C:
> > \cvs\JBoss4.0\jboss-4.0.x\thirdparty\jboss\remoting
> version=1.4.1_final
> > isLocal=
> > false [EMAIL PROTECTED]
> > output=C:\cvs\JBoss4.0\j
> > boss-4.0.x\thirdparty\jboss\remoting\lib\jboss-remoting.jar
> type=null}]
> > module=n
> > ull location=null}
> > setVersion, version=1.4.1_final
> >  
> > BUILD FAILED
> > C:\cvs\JBoss4.0\jboss-4.0.x\build\build.xml:937: The 
> following error 
> > occurred wh ile executing this line:
> > C:\cvs\JBoss4.0\jboss-4.0.x\build\build-thirdparty.xml:125: A
> versioning
> > problem
> >  exists:
> > Component: jboss/remoting is at version: 1.4.1_final  but 
> it is also 
> > required to be compatible with:
> > [EMAIL PROTECTED], version=1.4.0_final}]
> >  by: jboss/jbossws
> > 
> > xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Scott Stark
> > VP Architecture & Technology
> > JBoss Inc.
> > xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >  
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking 
> scripting language
> that extends applications into web and mobile media. Attend 
> the live webcast
> and join the prime developer group breaking into this new 
> coding territory!
> http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
> _______________________________________________
> JBoss-Development mailing list
> JBoss-Development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to