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

Posted to issues@maven.apache.org by "hatchetman82 (JIRA)" <ji...@codehaus.org> on 2010/02/27 07:45:55 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=211876#action_211876 ] 

hatchetman82 commented on MEAR-51:
----------------------------------

using the maven dependency plugin for this is not the perfect solution, because the dep. plugin can only fetch artifacts from the repository. this means that trying to add an exploded-ear-unpack execution to the package phase (where it logically belongs, just after ear:ear) would result in the _previous_ build of the ear being exploded (since the new one will only be copied into the repository at the install phase).
this forces me to bind the unpack-ear to the install phase, which might create problems (since im not aware of any way to guarentee the unpack runs after the artifact was installed to the repository)

> 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