[jira] Commented: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=143847#action_143847
]
Dave Sinclair commented on MWAR-116:
Pardon me, I got it to work. I had tried the @s around the
{artifact.artifactId}, but after looking at the source I realize it should be
only @[EMAIL PROTECTED] My bad! Thanks
The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
Key: MWAR-116
URL: http://jira.codehaus.org/browse/MWAR-116
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Chris Moesel
Assignee: Olivier Lamy
Fix For: 2.1-alpha-2
Attachments: mwar_93_webapp.zip
I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
the following to my POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1-SNAPSHOT/version
configuration
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/configuration
/plugin
This results in really oddly named files in my web-inf/lib now. A typical
example:
org.springframework-mywebapp.null
So, the resulting files are really mapped more like: ${groupId of the
dependency}-${artifactId of my war module}.null
I've attached an example Maven 2 project that demonstrates this. Just run
mvn package and look at the result in target.
--
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
[jira] Commented: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=143798#action_143798
]
Dave Sinclair commented on MWAR-116:
I have 2.1-alpha-2-SNAPSHOT and am still seeing this problem. Here is the
section from my pom. Any ideas?
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-2-SNAPSHOT/version
configuration
archiveClassestrue/archiveClasses
outputFileNameMapping${artifact.artifactId}.${artifact.extension}/outputFileNameMapping
filters
filtersrc/main/filters/${wile.filter.properties}/filter
/filters
webResources
webResource
directory${basedir}/src/main/webapp/WEB-INF/directory
includes
includebeans.xml/include
includeweb.xml/include
/includes
targetPathWEB-INF/targetPath
filteringtrue/filtering
/webResource
/webResources
/configuration
/plugin
The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
Key: MWAR-116
URL: http://jira.codehaus.org/browse/MWAR-116
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Chris Moesel
Assignee: Olivier Lamy
Fix For: 2.1-alpha-2
Attachments: mwar_93_webapp.zip
I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
the following to my POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1-SNAPSHOT/version
configuration
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/configuration
/plugin
This results in really oddly named files in my web-inf/lib now. A typical
example:
org.springframework-mywebapp.null
So, the resulting files are really mapped more like: ${groupId of the
dependency}-${artifactId of my war module}.null
I've attached an example Maven 2 project that demonstrates this. Just run
mvn package and look at the result in target.
--
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
[jira] Commented: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121727
]
Olivier Lamy commented on MWAR-116:
---
FYI. I have added a new constructor in p-u to use an alternate regexp
(http://fisheye.codehaus.org/changelog/plexus/?cs=7188).
I prefer an expression like @{}@ . I have tested it locally and it works.
The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
Key: MWAR-116
URL: http://jira.codehaus.org/browse/MWAR-116
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Chris Moesel
Assignee: Stephane Nicoll
Fix For: 2.1-alpha-2
Attachments: mwar_93_webapp.zip
I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
the following to my POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1-SNAPSHOT/version
configuration
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/configuration
/plugin
This results in really oddly named files in my web-inf/lib now. A typical
example:
org.springframework-mywebapp.null
So, the resulting files are really mapped more like: ${groupId of the
dependency}-${artifactId of my war module}.null
I've attached an example Maven 2 project that demonstrates this. Just run
mvn package and look at the result in target.
--
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
[jira] Commented: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121726
]
Stephane Nicoll commented on MWAR-116:
--
sounds good.
The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
Key: MWAR-116
URL: http://jira.codehaus.org/browse/MWAR-116
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Chris Moesel
Assignee: Stephane Nicoll
Fix For: 2.1-alpha-2
Attachments: mwar_93_webapp.zip
I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
the following to my POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1-SNAPSHOT/version
configuration
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/configuration
/plugin
This results in really oddly named files in my web-inf/lib now. A typical
example:
org.springframework-mywebapp.null
So, the resulting files are really mapped more like: ${groupId of the
dependency}-${artifactId of my war module}.null
I've attached an example Maven 2 project that demonstrates this. Just run
mvn package and look at the result in target.
--
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
[jira] Commented: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121819
]
Olivier Lamy commented on MWAR-116:
---
Stephane can you fix file permissions on apache snapshot repo ? I can't deploy
a new SNAPSHOT.
Thanks.
The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
Key: MWAR-116
URL: http://jira.codehaus.org/browse/MWAR-116
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Chris Moesel
Assignee: Olivier Lamy
Fix For: 2.1-alpha-2
Attachments: mwar_93_webapp.zip
I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
the following to my POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1-SNAPSHOT/version
configuration
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/configuration
/plugin
This results in really oddly named files in my web-inf/lib now. A typical
example:
org.springframework-mywebapp.null
So, the resulting files are really mapped more like: ${groupId of the
dependency}-${artifactId of my war module}.null
I've attached an example Maven 2 project that demonstrates this. Just run
mvn package and look at the result in target.
--
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
[jira] Commented: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121705
]
Olivier Lamy commented on MWAR-116:
---
we have to change the expressions in this mojo field to something lile @{ }.
Because it won't work. Maven always interpolate expressions like ${} in the pom.
MappingUtils must be changed too because currently it use
RegexBasedInterpolator from p-u because it use only expression like ${ }.
WDYT ?
The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
Key: MWAR-116
URL: http://jira.codehaus.org/browse/MWAR-116
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Chris Moesel
Assignee: Stephane Nicoll
Fix For: 2.1-alpha-2
Attachments: mwar_93_webapp.zip
I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
the following to my POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1-SNAPSHOT/version
configuration
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/configuration
/plugin
This results in really oddly named files in my web-inf/lib now. A typical
example:
org.springframework-mywebapp.null
So, the resulting files are really mapped more like: ${groupId of the
dependency}-${artifactId of my war module}.null
I've attached an example Maven 2 project that demonstrates this. Just run
mvn package and look at the result in target.
--
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
[jira] Commented: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112430
]
Stephane Nicoll commented on MWAR-116:
--
Still trying to figure out how to avoid the filtering
The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
Key: MWAR-116
URL: http://jira.codehaus.org/browse/MWAR-116
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Chris Moesel
Assignee: Stephane Nicoll
Fix For: 2.1-alpha-2
Attachments: mwar_93_webapp.zip
I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
the following to my POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1-SNAPSHOT/version
configuration
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/configuration
/plugin
This results in really oddly named files in my web-inf/lib now. A typical
example:
org.springframework-mywebapp.null
So, the resulting files are really mapped more like: ${groupId of the
dependency}-${artifactId of my war module}.null
I've attached an example Maven 2 project that demonstrates this. Just run
mvn package and look at the result in target.
--
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
[jira] Commented: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107165
]
Chris Moesel commented on MWAR-116:
---
I failed to mention this in the description, but I only tested using Maven
2.0.4. I do not have Maven 2.1-beta-1 on my system. So in this case, the war
plugin was the only component from 2.1-beta-1.
The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
Key: MWAR-116
URL: http://jira.codehaus.org/browse/MWAR-116
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Chris Moesel
Assignee: Stephane Nicoll
Attachments: mwar_93_webapp.zip
I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
the following to my POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1-SNAPSHOT/version
configuration
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/configuration
/plugin
This results in really oddly named files in my web-inf/lib now. A typical
example:
org.springframework-mywebapp.null
So, the resulting files are really mapped more like: ${groupId of the
dependency}-${artifactId of my war module}.null
I've attached an example Maven 2 project that demonstrates this. Just run
mvn package and look at the result in target.
--
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
[jira] Commented: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107176
]
Stephane Nicoll commented on MWAR-116:
--
maven 2.1-beta-1 does ot exist :)
I've tried myself with maven 2.0.4 to 2.0.7 so it's something unrelated. I 've
feedback from the dev list. I'll check later
The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
Key: MWAR-116
URL: http://jira.codehaus.org/browse/MWAR-116
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Chris Moesel
Assignee: Stephane Nicoll
Attachments: mwar_93_webapp.zip
I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
the following to my POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1-SNAPSHOT/version
configuration
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/configuration
/plugin
This results in really oddly named files in my web-inf/lib now. A typical
example:
org.springframework-mywebapp.null
So, the resulting files are really mapped more like: ${groupId of the
dependency}-${artifactId of my war module}.null
I've attached an example Maven 2 project that demonstrates this. Just run
mvn package and look at the result in target.
--
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
[jira] Commented: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107098
]
Stephane Nicoll commented on MWAR-116:
--
fun. The value of the outputFileNameMapping is actually translated when the pom
is read and the parameters are injected. So artifactId resolves to the current
project and extension is not set, hence it resolves to null.
The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
Key: MWAR-116
URL: http://jira.codehaus.org/browse/MWAR-116
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Chris Moesel
Assignee: Stephane Nicoll
Attachments: mwar_93_webapp.zip
I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
the following to my POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1-SNAPSHOT/version
configuration
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/configuration
/plugin
This results in really oddly named files in my web-inf/lib now. A typical
example:
org.springframework-mywebapp.null
So, the resulting files are really mapped more like: ${groupId of the
dependency}-${artifactId of my war module}.null
I've attached an example Maven 2 project that demonstrates this. Just run
mvn package and look at the result in target.
--
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
[jira] Commented: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107104
]
Stephane Nicoll commented on MWAR-116:
--
apparently it is a regression in Maven itself that translates the value of the
plugin's parameter.
I'm not sure though since I can reproduce with maven 2.0.4
The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
Key: MWAR-116
URL: http://jira.codehaus.org/browse/MWAR-116
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Chris Moesel
Assignee: Stephane Nicoll
Attachments: mwar_93_webapp.zip
I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
the following to my POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1-SNAPSHOT/version
configuration
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/configuration
/plugin
This results in really oddly named files in my web-inf/lib now. A typical
example:
org.springframework-mywebapp.null
So, the resulting files are really mapped more like: ${groupId of the
dependency}-${artifactId of my war module}.null
I've attached an example Maven 2 project that demonstrates this. Just run
mvn package and look at the result in target.
--
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
