Whether they are tagged or not (they could be).
I'm saying it's possible for each component of org.jboss.javaee
to have its own releases and to use individual components in other
projects.
You said below that this wasn't possible.
"However the way we have structured this is not consumable by individual
projects"
I would expect that even if the individual components have their
own bug fix releases there would still be an overall assembly release
for the appserver which accumulates all the bug fixes across the
components.
On Thu, 2008-04-10 at 12:56 +0300, Dimitris Andreadis wrote:
But those are not tagged versions, right?
> <dependency>
> <groupId>org.jboss.javaee</groupId>
> <artifactId>jboss-jca-api</artifactId>
> <version>1.5.0.20070913080910</version>
> </dependency>
Adrian Brock wrote:
> On Wed, 2008-04-09 at 20:39 +0300, Dimitris Andreadis wrote:
>> This has been partially discussed on the forums, but I want to get some wider
consensus on
>> how to proceed, especially from the various jboss projects that
consume/implement javax APIs:
>>
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139711#...
>>
>> AFAIK, jboss-javaee.jar is supposed to serve as the authoritative javaEE API
supported and
>> implemented by AS (JavaEE5 in our case). The .jar itself is made up by the
individual
>> sub-apis listed here (e.g. jms, jacc, etc):
>>
https://svn.jboss.org/repos/jbossas/projects/javaee/
>>
>> However the way we have structured this is not consumable by individual projects
(like WS or
>> Hibernate). We tag the whole thing, like 5.0.0.Beta3 or 5.0.0.Beta3Update1,
while a project
>> may want to use/implement specifically, e.g. JMS 1.1
>
> The jboss-integration project is quite happily consuming
> individual parts of the javaee project now.
>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>jboss</groupId>
> <artifactId>jboss-common-logging-spi</artifactId>
> <version>2.0.4.GA</version>
> </dependency>
> <dependency>
> <groupId>org.jboss</groupId>
> <artifactId>jboss-common-core</artifactId>
> <version>2.2.1.GA</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.javaee</groupId>
> <artifactId>jboss-jca-api</artifactId>
> <version>1.5.0.20070913080910</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.javaee</groupId>
> <artifactId>jboss-transaction-api</artifactId>
> <version>1.0.1.20070913080910</version>
> </dependency>
> <dependency>
> <groupId>jacorb</groupId>
> <artifactId>jacorb</artifactId>
> <version>2.3.0jboss.patch4-brew</version>
> </dependency>
> </dependencies>
> </dependencyManagement>
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development --
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx