jboss-javaee.jar

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#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

I think what we need is for the individual sub-apis to be
independently versioned and 
tagged. So the JMS API whould have versions 1.0, 1.1 and so
on. The jboss project can then 
use specific apis at arbitrary versions, without having
duplicates in their own projects.

Then a higher level javaee project can import the set of
APIs required to create the 
aggregate JavaEE5 (or JavaEE6 and so on) apis.

A single JIRA project could be used to track all those
updates.

One issue to consider is whether the aggregate jar will
include the classes of the apis (in 
which case you only need to ship the aggregate jar), or
reference the external libraries in 
its MANIFEST.MF.

The other issue is when compiling AS and importing the
aggregate jboss-javaee.jar, make sure 
that sub-api libraries that can be imported as transitive
dependencies agree with the 
versions chosen at the aggregate level, and if not flag that
as an error.

I understand that the only way to do this is by using maven
ranges ([ ]) on jboss-javaee.jar.

Any input on this is appreciated.

/D
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

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#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
> 
> I think what we need is for the individual sub-apis to
be independently 
> versioned and tagged. 

agreed

So the JMS API whould have versions 1.0, 1.1 and
> so on. The jboss project can then use specific apis at
arbitrary 
> versions, without having duplicates in their own
projects.
> 
> Then a higher level javaee project can import the set
of APIs required 
> to create the aggregate JavaEE5 (or JavaEE6 and so on)
apis.
> 
> A single JIRA project could be used to track all those
updates.
> 
> One issue to consider is whether the aggregate jar will
include the 
> classes of the apis (in which case you only need to
ship the aggregate 
> jar), or reference the external libraries in its
MANIFEST.MF.

No aggregation of ws related apis please. This would not
allow us to do 
drop in replacements. We have an eight week release cycle
and support 
the last three (taged) AS versions

http://jbws.dyndns.org/mediawiki/ind
ex.php?title=Supported_Target_Containers

> 
> The other issue is when compiling AS and importing the
aggregate 
> jboss-javaee.jar, make sure that sub-api libraries that
can be imported 
> as transitive dependencies agree with the versions
chosen at the 
> aggregate level, and if not flag that as an error.
> 
> I understand that the only way to do this is by using
maven ranges ([ ]) 
> on jboss-javaee.jar.

I still fail to understand the benefit of maven all
together.

> 
> Any input on this is appreciated.
> 
> /D
> _______________________________________________
> jboss-development mailing list
> jboss-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

On Wed, 2008-04-09 at 20:39 +0300, Dimitris Andreadis
wrote:
> 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
> 
> I think what we need is for the individual sub-apis to
be independently versioned and 
> tagged. So the JMS API whould have versions 1.0, 1.1
and so on. The jboss project can then 
> use specific apis at arbitrary versions, without having
duplicates in their own projects.

You can't use the JMS api version as the maven version.
How do you fix a bug and re-release it if there is only one
version?
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

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#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>

-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

Adrian Brock wrote:
> On Wed, 2008-04-09 at 20:39 +0300, Dimitris Andreadis
wrote:
>> 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
>>
>> I think what we need is for the individual sub-apis
to be independently versioned and 
>> tagged. So the JMS API whould have versions 1.0,
1.1 and so on. The jboss project can then 
>> use specific apis at arbitrary versions, without
having duplicates in their own projects.
> 
> You can't use the JMS api version as the maven
version.
> How do you fix a bug and re-release it if there is only
one version?

Maybe use a version that is close to the API one with an
extra qualifier? For JMS that could 
be 1.1.n, with n marking our own release attempts. In any
case, since those are APIs aren't 
fixes supposed to be very infrequent?



_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

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#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-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

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#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-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

Adrian Brock wrote:
> 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.

I didn't know about this possibility. How are those
snapshot-like releases made?

And unless we change the structure of the svn repository we
cannot tag those independently.

> 
> "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.

It seem WS don't like this because it doesn't allow the
updating of individual api 
libraries. Unless we ship an empty javaee.jar that
references the other library apis?
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

On Thu, 2008-04-10 at 13:25 +0300, Dimitris Andreadis
wrote:
> Adrian Brock wrote:
> It seem WS don't like this because it doesn't allow the
updating of individual api 
> libraries. Unless we ship an empty javaee.jar that
references the other library apis?

That's not what I'm saying. You shouldn't be updating
indvidual
components without doing an assembly release as well.

It doesn't make sense. 

WS can't use a new api that AS doesn't have a release for
under javaee.

> _______________________________________________
> jboss-development mailing list
> jboss-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

I understand that WS wants to be able to plugin to AS a
newer version of WS that might be 
implementing a newer version of the API.

Whether that is a valid requirement is debatable.

Adrian Brock wrote:
> On Thu, 2008-04-10 at 13:25 +0300, Dimitris Andreadis
wrote:
>> Adrian Brock wrote:
>> It seem WS don't like this because it doesn't allow
the updating of individual api 
>> libraries. Unless we ship an empty javaee.jar that
references the other library apis?
> 
> That's not what I'm saying. You shouldn't be updating
indvidual
> components without doing an assembly release as well.
> 
> It doesn't make sense. 
> 
> WS can't use a new api that AS doesn't have a release
for under javaee.
> 
>> _______________________________________________
>> jboss-development mailing list
>> jboss-developmentlists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment