You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Jacek Laskowski <ja...@laskowski.net.pl> on 2009/10/12 23:45:37 UTC

Why do we need javaee-api?

Hi,

The subject says it all - what is javaee-api for? I don't understand
the maven-shade-plugin configuration in the pom.xml.

Jacek

-- 
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl

Re: Why do we need javaee-api?

Posted by David Blevins <da...@visi.com>.
On Oct 15, 2009, at 4:07 AM, Jacek Laskowski wrote:

> What I couldn't figure out yet
> was what the following configuration in pom.xml of the javaee-api
> project meant to do:
>
>              <filters>
>                <filter>
>
> <artifact>org.apache.geronimo.specs:geronimo-ejb_3.0_spec</artifact>
>                  <includes>
>                    <include>javax/ejb/**</include>
>                  </includes>
>                </filter>
>              </filters>
>
> Could someone decipher it for me? If that means that
> javax/xml/rpc/handler/MessageContext.class should not be included what
> is this additional step made for? What would break if it was removed?

Right, it filters out MessageContext from that jar.  It's in another  
jar and having it there twice broke the plugin.  I seem to recall I  
actually had to add that include/exclude feature to the maven-shade- 
plugin to get it to work for us.

> p.s. I hate these "[WARNING] We have a duplicate" messages popping up
> during maven-shade-plugin work. I'm looking into turning them off.
> Anyone knows how? It'd be faster, I believe.

I'm not sure what that is about as AFAIK the plugin fails if there are  
actual duplicate classes in the jars.

-David

Re: Why do we need javaee-api?

Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On Thu, Oct 15, 2009 at 4:16 AM, David Blevins <da...@visi.com> wrote:
> I like the one big jar as well, but I can understand the situations where it
> is a hinderance.
>
> We now have the javaee-api.jar and the javaee-api-libs.zip, so hopefully
> that covers everyone's needs.

That's fine and I can see its value. What I couldn't figure out yet
was what the following configuration in pom.xml of the javaee-api
project meant to do:

              <filters>
                <filter>

<artifact>org.apache.geronimo.specs:geronimo-ejb_3.0_spec</artifact>
                  <includes>
                    <include>javax/ejb/**</include>
                  </includes>
                </filter>
              </filters>

Could someone decipher it for me? If that means that
javax/xml/rpc/handler/MessageContext.class should not be included what
is this additional step made for? What would break if it was removed?

p.s. I hate these "[WARNING] We have a duplicate" messages popping up
during maven-shade-plugin work. I'm looking into turning them off.
Anyone knows how? It'd be faster, I believe.

Jacek

-- 
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl

Re: Why do we need javaee-api?

Posted by David Blevins <da...@visi.com>.
I like the one big jar as well, but I can understand the situations  
where it is a hinderance.

We now have the javaee-api.jar and the javaee-api-libs.zip, so  
hopefully that covers everyone's needs.

-David

On Oct 12, 2009, at 3:08 PM, Jonathan Gallimore wrote:

> I'm not too familiar with the configuration of the maven-shade  
> plugin, so
> I'd struggle to explain it. Personally I find javaee-api rather  
> useful -
> saves me having to remember several different API jars as javaee-api
> combines them all.
>
> Jon
>
> On Mon, Oct 12, 2009 at 10:52 PM, Quintin Beukes <quintin@skywalk.co.za 
> >wrote:
>
>> I was looking at those exact things about 20 minutes ago ;> I was
>> actually looking for the source code of some of those
>> interfaces/annotations, but went through the same poms/projects.
>>
>> Quintin Beukes
>>
>>
>>
>> On Mon, Oct 12, 2009 at 11:45 PM, Jacek Laskowski
>> <ja...@laskowski.net.pl> wrote:
>>> Hi,
>>>
>>> The subject says it all - what is javaee-api for? I don't understand
>>> the maven-shade-plugin configuration in the pom.xml.
>>>
>>> Jacek
>>>
>>> --
>>> Jacek Laskowski
>>> Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
>>>
>>

Re: Why do we need javaee-api?

Posted by Jonathan Gallimore <jo...@gmail.com>.
I'm not too familiar with the configuration of the maven-shade plugin, so
I'd struggle to explain it. Personally I find javaee-api rather useful -
saves me having to remember several different API jars as javaee-api
combines them all.

Jon

On Mon, Oct 12, 2009 at 10:52 PM, Quintin Beukes <qu...@skywalk.co.za>wrote:

> I was looking at those exact things about 20 minutes ago ;> I was
> actually looking for the source code of some of those
> interfaces/annotations, but went through the same poms/projects.
>
> Quintin Beukes
>
>
>
> On Mon, Oct 12, 2009 at 11:45 PM, Jacek Laskowski
> <ja...@laskowski.net.pl> wrote:
> > Hi,
> >
> > The subject says it all - what is javaee-api for? I don't understand
> > the maven-shade-plugin configuration in the pom.xml.
> >
> > Jacek
> >
> > --
> > Jacek Laskowski
> > Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
> >
>

Re: Why do we need javaee-api?

Posted by Quintin Beukes <qu...@skywalk.co.za>.
I was looking at those exact things about 20 minutes ago ;> I was
actually looking for the source code of some of those
interfaces/annotations, but went through the same poms/projects.

Quintin Beukes



On Mon, Oct 12, 2009 at 11:45 PM, Jacek Laskowski
<ja...@laskowski.net.pl> wrote:
> Hi,
>
> The subject says it all - what is javaee-api for? I don't understand
> the maven-shade-plugin configuration in the pom.xml.
>
> Jacek
>
> --
> Jacek Laskowski
> Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
>