maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephane Nicoll (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MEAR-51) Exploded (unpacked) ear
Date Wed, 06 Dec 2006 20:25:42 GMT
    [ http://jira.codehaus.org/browse/MEAR-51?page=comments#action_81931 ] 
            
Stephane Nicoll commented on MEAR-51:
-------------------------------------

I am pretty sure the application server does not care at all if a manifest is not present.

Regarding your questions:

# uh? /opt/jboss/server/default/deploy/${pom.artifactId}-${pom.currentVersion}.ear 
# True but then work directory should be the same or the unpack goal should copy everything
over the "exploded directory"
# Why?
# Yes it is. The EAR plugin is designed to build the EAR in this directory. 

I can add an ear:exploded goal but I am not sure it will help.

Please provide more details, use case, etc and I will add the functionnality for sure if it
makes sense. For now, I don't really see a problem.


> 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
>         Assigned To: 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

        

Mime
View raw message