4 Replies Latest reply on Mar 6, 2007 2:49 PM by starksm64

JBAS-4109, jbossws-2.0.0.CR4?

starksm64 Feb 17, 2007 12:08 PM

We need a non-snapshot release of jbossws that includes an updated remoting dependency that is consistent with the jbm 2.2.0.Alpha7. Currently there is some snapshot that indicates its jbossws-2.0.0.CR3:

09:07:05,109 INFO [ServiceEndpointManager] jbossws-2.0.0.CR3 (build=200702151515)

What will it take to get a jbossws-2.0.0.CR4 release for this?

1. Re: JBAS-4109, jbossws-2.0.0.CR4?

jason.greene Feb 19, 2007 11:43 AM (in response to starksm64)

I can tag a CR4 by tomorrow.
Actions
2. Re: JBAS-4109, jbossws-2.0.0.CR4?

jason.greene Feb 20, 2007 10:23 PM (in response to starksm64)

Sorry, I meant CR3. I have tagged and released CR3.
Actions
3. Re: JBAS-4109, jbossws-2.0.0.CR4?

starksm64 Feb 21, 2007 12:17 AM (in response to starksm64)

jbossas trunk build-thirdparty.xml has been updated to jbossws 2.0.0.CR3 and jboss remoting 2.2.0.Alpha7.
Actions
4. Re: JBAS-4109, jbossws-2.0.0.CR4?

starksm64 Mar 6, 2007 2:49 PM (in response to starksm64)
The jbossas trunk version has been reverted back to snapshot by Thomas. I need a release version this week. Also, the declared mc dependencies for the 2.0.x line seem questionable:

<import componentref="jboss/microcontainer"> <compatible version="snapshot"/> <compatible version="2.0.0.Beta3"/> <compatible version="1.0.2"/> </import>

I added the 2.0.0.Beta3 to the snapshot, but the 1.0.2 compatibility cannot be correct for the mc-2.0.x deployers. We will need to split up environment specific artifiacts like deployers from the core to be able to declare property dependencies.
Actions

Go to original post