[jira] (MEAR-155) Building multiple EARs containing different modules with classifiers doesn't work with skinnyWars set to true
[
https://jira.codehaus.org/browse/MEAR-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MEAR-155:
Description:
I have a multi-module project with following structure:
{noformat}
root
|- content
|- WAR
\- EAR
{noformat}
In which all modules (except root) generate 2 artifacts: a 'normal' artifact
(no classifier), that gets deployed on the server and a 'dev' artifact
(classifier=dev), that is used for local development.
This has worked fine until the skinnyWar was set to true:
The EAR-plugin now extracts the normal WAR into a temp-dir and repackages it.
Then it creates the EAR -- this version is alright.
When it wants to package the 'dev'-version, it extract the WAR into the SAME
directory as the previous WAR, repackages it and creates the EAR.
The problem here, is that the 'dev'-EAR now contains a 'dev'-WAR that has mixed
libraries inside -- both the 'normal' and 'dev' content-JAR!
Wouldn't it be better to either delete the temp-dir after creating the first
EAR or unpacking the module into a different temp-dir (eg including the
classifier in the name)?
was:
I have a multi-module project with following structure:
root
|- content
|- WAR
\- EAR
In which all modules (except root) generate 2 artifacts: a 'normal' artifact
(no classifier), that gets deployed on the server and a 'dev' artifact
(classifier=dev), that is used for local development.
This has worked fine until the skinnyWar was set to true:
The EAR-plugin now extracts the normal WAR into a temp-dir and repackages it.
Then it creates the EAR -- this version is alright.
When it wants to package the 'dev'-version, it extract the WAR into the SAME
directory as the previous WAR, repackages it and creates the EAR.
The problem here, is that the 'dev'-EAR now contains a 'dev'-WAR that has mixed
libraries inside -- both the 'normal' and 'dev' content-JAR!
Wouldn't it be better to either delete the temp-dir after creating the first
EAR or unpacking the module into a different temp-dir (eg including the
classifier in the name)?
Building multiple EARs containing different modules with classifiers doesn't
work with skinnyWars set to true
-
Key: MEAR-155
URL: https://jira.codehaus.org/browse/MEAR-155
Project: Maven Ear Plugin
Issue Type: Bug
Reporter: Roland Asmann
Attachments: MEAR-155.zip
I have a multi-module project with following structure:
{noformat}
root
|- content
|- WAR
\- EAR
{noformat}
In which all modules (except root) generate 2 artifacts: a 'normal' artifact
(no classifier), that gets deployed on the server and a 'dev' artifact
(classifier=dev), that is used for local development.
This has worked fine until the skinnyWar was set to true:
The EAR-plugin now extracts the normal WAR into a temp-dir and repackages it.
Then it creates the EAR -- this version is alright.
When it wants to package the 'dev'-version, it extract the WAR into the SAME
directory as the previous WAR, repackages it and creates the EAR.
The problem here, is that the 'dev'-EAR now contains a 'dev'-WAR that has
mixed libraries inside -- both the 'normal' and 'dev' content-JAR!
Wouldn't it be better to either delete the temp-dir after creating the first
EAR or unpacking the module into a different temp-dir (eg including the
classifier in the name)?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-155) Building multiple EARs containing different modules with classifiers doesn't work with skinnyWars set to true
[ https://jira.codehaus.org/browse/MEAR-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roland Asmann updated MEAR-155: --- Attachment: MEAR-155.zip A simple project that shows the problem. When the parameter 'skinnyWars' in the EAR-project is set to 'false'. the generated EAR is correct. Building multiple EARs containing different modules with classifiers doesn't work with skinnyWars set to true - Key: MEAR-155 URL: https://jira.codehaus.org/browse/MEAR-155 Project: Maven 2.x Ear Plugin Issue Type: Bug Reporter: Roland Asmann Attachments: MEAR-155.zip I have a multi-module project with following structure: root |- content |- WAR \- EAR In which all modules (except root) generate 2 artifacts: a 'normal' artifact (no classifier), that gets deployed on the server and a 'dev' artifact (classifier=dev), that is used for local development. This has worked fine until the skinnyWar was set to true: The EAR-plugin now extracts the normal WAR into a temp-dir and repackages it. Then it creates the EAR -- this version is alright. When it wants to package the 'dev'-version, it extract the WAR into the SAME directory as the previous WAR, repackages it and creates the EAR. The problem here, is that the 'dev'-EAR now contains a 'dev'-WAR that has mixed libraries inside -- both the 'normal' and 'dev' content-JAR! Wouldn't it be better to either delete the temp-dir after creating the first EAR or unpacking the module into a different temp-dir (eg including the classifier in the name)? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-155) Building multiple EARs containing different modules with classifiers doesn't work with skinnyWars set to true
[ https://jira.codehaus.org/browse/MEAR-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=307917#comment-307917 ] Stéphane Nicoll commented on MEAR-155: -- please attach a sample that reproduces the issue Building multiple EARs containing different modules with classifiers doesn't work with skinnyWars set to true - Key: MEAR-155 URL: https://jira.codehaus.org/browse/MEAR-155 Project: Maven 2.x Ear Plugin Issue Type: Bug Reporter: Roland Asmann I have a multi-module project with following structure: root |- content |- WAR \- EAR In which all modules (except root) generate 2 artifacts: a 'normal' artifact (no classifier), that gets deployed on the server and a 'dev' artifact (classifier=dev), that is used for local development. This has worked fine until the skinnyWar was set to true: The EAR-plugin now extracts the normal WAR into a temp-dir and repackages it. Then it creates the EAR -- this version is alright. When it wants to package the 'dev'-version, it extract the WAR into the SAME directory as the previous WAR, repackages it and creates the EAR. The problem here, is that the 'dev'-EAR now contains a 'dev'-WAR that has mixed libraries inside -- both the 'normal' and 'dev' content-JAR! Wouldn't it be better to either delete the temp-dir after creating the first EAR or unpacking the module into a different temp-dir (eg including the classifier in the name)? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-155) Building multiple EARs containing different modules with classifiers doesn't work with skinnyWars set to true
Roland Asmann created MEAR-155: -- Summary: Building multiple EARs containing different modules with classifiers doesn't work with skinnyWars set to true Key: MEAR-155 URL: https://jira.codehaus.org/browse/MEAR-155 Project: Maven 2.x Ear Plugin Issue Type: Bug Reporter: Roland Asmann I have a multi-module project with following structure: root |- content |- WAR \- EAR In which all modules (except root) generate 2 artifacts: a 'normal' artifact (no classifier), that gets deployed on the server and a 'dev' artifact (classifier=dev), that is used for local development. This has worked fine until the skinnyWar was set to true: The EAR-plugin now extracts the normal WAR into a temp-dir and repackages it. Then it creates the EAR -- this version is alright. When it wants to package the 'dev'-version, it extract the WAR into the SAME directory as the previous WAR, repackages it and creates the EAR. The problem here, is that the 'dev'-EAR now contains a 'dev'-WAR that has mixed libraries inside -- both the 'normal' and 'dev' content-JAR! Wouldn't it be better to either delete the temp-dir after creating the first EAR or unpacking the module into a different temp-dir (eg including the classifier in the name)? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
