[jboss-dev] Javaee Spec Jars

[Emmanuel Bernard]

It does not ease my management to have to deploy them twice to Maven. One is already annoying enough.

* and before you complain: I play as a team except that the team that, in practice, does this job is of size 1 and the team cares very much about not wasting time.

On 22 janv. 2010, at 20:24, David M. Lloyd wrote:

> Any reason we shouldn't just make it uniform though?  Seems like we'd want 
> to keep them all in the same place, in maven and in svn, just for ease of 
> management.
> 
> - DML
> 
> On 01/22/2010 01:18 PM, Emmanuel Bernard wrote:
>> Note that we own a couple of specs like CDI and Bean Validation. For these we do use javax.blah as the genuine owner and implementor of that namespace.
>> 
>> On 22 janv. 2010, at 19:01, Paul Gier wrote:
>> 
>>> Hi everyone,
>>> 
>>> There was some discussion about naming conventions and svn structure for the
>>> javaee api spec projects this morning.  There is also more info in jira [1].
>>> Here is the plan at this point.
>>> 
>>> GroupId: org.jboss.spec.<sun groupId>
>>> ArtifactId:<spec name>_<spec version>_spec
>>> Version: Standard OSGI versions starting with 1.0.0
>>> 
>>> For example:
>>> <dependency>
>>>   <groupId>org.jboss.spec.javax.servlet</groupId>
>>>   <artifactId>servlet-api_2.5_spec</artifactId>
>>>   <version>1.0-SNAPSHOT</version>
>>> </dependency>
>>> 
>>> The structure in svn will look similar to the structure that the geronimo
>>> project uses for their spec jars [2].  Meaning that each spec version will have
>>> a separate trunk and a separate release cycle.
>>> 
>>> In addition to deploying the spec jars (and pom) to the Maven repository, there
>>> will also be an aggregate pom, but not an aggregate jar.  The aggregate pom will
>>> be a project with packaging "pom" and will list each included spec in the
>>> dependencyManagement and dependencies sections.  This will allow the app server
>>> build to declare a single dependency on the combined javaee pom and it will
>>> automatically get all the individual spec jars added to the dependency tree.
>>> 
>>> Going forward, we would like to have all spec jars in same area in svn, and each
>>> will have it's own release lifecycle and projects that need the spec jars can
>>> either depend on the individual jars or on the aggregator pom.
>>> 
>>> [1]https://jira.jboss.org/jira/browse/JBEE-15
>>> [2]http://svn.apache.org/repos/asf/geronimo/specs/trunk/
>>> _______________________________________________
>>> 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
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development