maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephane Nicoll (JIRA)" <>
Subject [jira] Commented: (MEAR-63) Allow subclasses of EarMojo to provide a JarArchiver
Date Sat, 28 Apr 2007 18:10:26 GMT


Stephane Nicoll commented on MEAR-63:

I am familiar with JSR-168 and I need to work on that short term. Are you involved in Apache

Note sure you should open another issue for this. However, let's discuss how the EAR pluging
can gives out-of-the-box portlet deployments. I don't like the ear:exploded goal (even if
we will implement it as soon as the lifecycles of the EAR pluging is externalized; currently
it's set in maven core :/)

Please give me more details or let's schedule a discussion on IRC

> Allow subclasses of EarMojo to provide a JarArchiver
> ----------------------------------------------------
>                 Key: MEAR-63
>                 URL:
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3
>         Environment: Maven 2.x Ear Plugin trunk :
>            Reporter: Elliot Metsger
>            Assignee: Stephane Nicoll
>            Priority: Minor
>         Attachments: EarMojo.diff
> We would like to have the EAR plugin use a custom JarArchiver.  
> In Maven 2.0.x, Plexus component lookups for our custom JarArchiver component fail randomly
(I'm told by one of the Maven developers in the Maven chatroom on that this
behavior is fixed in Maven 2.1).
> Could the EAR plugin provide a protected method (for extending classes to override) which
obtains the JarArchiver?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message