You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Avraham Rosenzweig (JIRA)" <ji...@codehaus.org> on 2008/07/30 01:48:26 UTC

[jira] Commented: (MEAR-51) Exploded (unpacked) ear

    [ http://jira.codehaus.org/browse/MEAR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143559#action_143559 ] 

Avraham Rosenzweig commented on MEAR-51:
----------------------------------------

I guess the right thing to do on this case is to use the unpack goal of the maven-dependency-plugin.

You can configure it on the verify or install phase and set outputDirectory to the the desired place.

What do you think?

> Exploded (unpacked) ear
> -----------------------
>
>                 Key: MEAR-51
>                 URL: http://jira.codehaus.org/browse/MEAR-51
>             Project: Maven 2.x Ear Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.2
>            Reporter: Maurice Zeijen
>            Assignee: Stephane Nicoll
>
> It is great that you can unpack the modules within the ear. But it would be also be great if the ear itself could also be delivered unpacked. At this moment I could use the working directory but it doesn't get the Manifest file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira