[ http://jira.codehaus.org/browse/MEAR-51?page=comments#action_81927 ] Maurice Zeijen commented on MEAR-51: ------------------------------------
I am not sure if the MANIFEST.MF file is used with an exploded ear. My JBoss 4.0.5.GA doesn't seem to find it a problem. But I don't know what the official JSR says about it. But there are more reasons to having an unpack option. 1. I would need to set the workDirectory property because the default workdirectory doesn't add the .ear on the end of the name. If I set the workDirectory then I lose the ability that the version is automatically added to the name. 2. The .ear file gets generated for nothing. If I want an unpacked ear directory then I probably don't need an .ear file. 3. I want the ear directory to be created in a different directory then the target directory. For instance in my jboss deploy directory so that I don't need to copy it manually. It just feels wrong to put the workDirectory there. 4. The workDirectory isn't meant to be used as an exploded ear. I can't depend on it to behave the same in future versions. > 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
