-
1. Re: container integration naming issue
heiko.braun Jun 13, 2008 3:53 AM (in response to thomas.diesler)It could simply carry the name for the container it was released (QA'd) for: jbossws-jboss-5.0.0.CR1
-
2. Re: container integration naming issue
ropalka Jun 13, 2008 3:54 AM (in response to thomas.diesler)I don't see it as a problem at least for AS trunk. As you use to say Thomas container integration resides in AS code base. I'm going to sync AS trunk today with jboss501 integration layer, thus there's no maven artifact needed for AS trunk to include our separate jboss integration layer inside. Or did I miss something?
-
3. Re: container integration naming issue
thomas.diesler Jun 13, 2008 6:49 AM (in response to thomas.diesler)Consider this:
#1 you put the container integration in AS trunk
#2 you 'mvn deploy' jbossws-jboss-5.0.0-SNAPSHOT from AS trunk
#3 CR1 gets released
#4 you 'mvn deploy' jbossws-jboss-5.0.0.CR1 from AS trunk
#5 you work on jbossws-3.0.3 and need to update jbossws-jboss-5.0.0.CR1
What now?
Heiko's naming scheme does not work because you cannot have a dependency on the same artifact with different versions<dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-jboss</artifactId> <version>5.0.0.Beta4</version> </dependency> <dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-jboss</artifactId> <version>5.0.0.CR1</version> </dependency>
-
4. Re: container integration naming issue
ropalka Jun 13, 2008 7:05 AM (in response to thomas.diesler)"thomas.diesler@jboss.com" wrote:
What now?
Unfortunately this is the maven artifacts naming issue. AFAIK maven doesn't enable you to specify buildnumber for non-snapshot artifacts :( -
5. Re: container integration naming issue
ropalka Jun 13, 2008 7:14 AM (in response to thomas.diesler)Well this is a general issue that affects all AS modules that have different (shorter) lifecycle than AS as whole has. We should ask other AS folks/leads how do they plan to deal with this kind of issues in the future and if it was investigated before mavenization process. In case there will be no appropriate and correct solution to this problem our release cycle will have to follow AS release cycle what we don't want :(
-
6. Re: container integration naming issue
thomas.diesler Jun 13, 2008 7:31 AM (in response to thomas.diesler)well, there are various other options.
- jbossws-jboss500beta4-3.0.2-SNAPSHOT
- jbossws-jboss-500beta4-3.0.2-SNAPSHOT (classifier)
- module per container with single dependency -
7. Re: container integration naming issue
asoldano Jun 13, 2008 7:39 AM (in response to thomas.diesler)Still thinking if this could be acceptable / could work, however my first understanding of what Heiko said was that the artifact id could carry the name of container it was released for, ie:
<dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-jboss500Beta4</artifactId> <version>3.0.3-SNAPSHOT</version> </dependency> <dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-jboss500CR1</artifactId> <version>3.0.3-SNAPSHOT</version> </dependency>
-
8. Re: container integration naming issue
heiko.braun Jun 13, 2008 7:53 AM (in response to thomas.diesler)Container integration depicts container compatibility, but at the same time SPI compatibility. Furthermore it can have maintenance releases. To me this gives us something like:
[container]-[spi]-[release]
i.e. (leaving square brackets for readability)[jboss5.0.0.CR1]-[3.0.2]-[1]
which is identical to what thomas suggestedjbossws-jboss-[500beta4]-[3.0.2-SNAPSHOT]- [classifier]
-
9. Re: container integration naming issue
heiko.braun Jun 13, 2008 7:57 AM (in response to thomas.diesler)You even break it up using maven conventions
<dependency> <groupId>org.jboss.ws</groupId> <artifactId>[container]-[spi]</artifactId> <version>[release]</version> </dependency>
or<dependency> <groupId>org.jboss.ws</groupId> <artifactId>[jboss501]-[3.0.2]</artifactId> <version>1</version> </dependency>
-
10. Re: container integration naming issue
thomas.diesler Jun 13, 2008 10:06 AM (in response to thomas.diesler)So we have
<dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-jboss500Beta4</artifactId> <version>3.0.3-SNAPSHOT</version> </dependency> <dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-jboss500CR1</artifactId> <version>3.0.3-SNAPSHOT</version> </dependency>
as suggested by Alessio or
module-jboss-5.0.0.Beta4<dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-jboss</artifactId> <version>5.0.0.Beta4-3.0.3-SNAPSHOT</version> </dependency>
module-jboss-5.0.0.CR1<dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-jboss</artifactId> <version>5.0.0.CR1-3.0.3-SNAPSHOT</version> </dependency>
Using a classifier is IMHO not an option because you cant classify the main main build artifact. -
11. Re: container integration naming issue
thomas.diesler Jun 13, 2008 10:09 AM (in response to thomas.diesler)I would go for
<dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-jboss500Beta4</artifactId> <version>3.0.3-SNAPSHOT</version> </dependency> <dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-jboss500CR1</artifactId> <version>3.0.3-SNAPSHOT</version> </dependency>
-
12. Re: container integration naming issue
thomas.diesler Jun 19, 2008 5:28 AM (in response to thomas.diesler)For container integrations that are used with unreleased container versions (i.e. jbossas/trunk, jbossas/branches/Branch_4_2)
we use th e convention that we append 'x' to the container version<dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-jboss423x</artifactId> <version>3.0.3-SNAPSHOT</version> </dependency> <dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-jboss500x</artifactId> <version>3.0.3-SNAPSHOT</version> </dependency>
-
13. Re: container integration naming issue
thomas.diesler Jun 19, 2008 5:30 AM (in response to thomas.diesler)Currently the container integrations jars translate as follows
jbossws-jboss421-3.0.2.GA.jar => jbossws-jboss421.jar
jbossws-jboss422-3.0.2.GA.jar => jbossws-jboss422.jar
jbossws-jboss423x-3.0.2.GA.jar => jbossws-jboss423.jar
jbossws-jboss500Beta4-3.0.2.GA.jar => jbossws-jboss500.jar
jbossws-jboss500x-3.0.2.GA.jar => jbossws-jboss501.jar