[
http://jira.codehaus.org/browse/MSHARED-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222655#action_222655
]
Cameron Fieber commented on MSHARED-131:
----------------------------------------
We've run into the same issue. We have a 'test' classifier for our test build
and an empty classifier for our production build. Updating maven-ejb-plugin
from 2.1 to 2.2.1 and maven-jar-plugin from 2.2 to 2.3 caused this to occur, it
didn't happen in the original versions. I'm currently rolling back to the
older plugin versions and hoping this one can be fixed.
Thanks!
> Maven archiver does not manager empty classifier correclty in manifest.mf
> classpath
> -----------------------------------------------------------------------------------
>
> Key: MSHARED-131
> URL: http://jira.codehaus.org/browse/MSHARED-131
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Reporter: fabrice
>
> When I have a dependency
> <dependency>
> <groupId>com.almerys.pec</groupId>
> <artifactId>ws-ag2r-client</artifactId>
> <version>2.2.0.0.0</version>
> <classifier>${env}</classifier>
> </dependency>
> and $env define as empty like that
> <env></env> or <env/>
> Maven download the correct dependency without classifier but in the
> manifest.mf I have in the classpath : ws-ag2r-client-2.2.0.0.0-.jar
> '-' is not correct !!
> Fabrice
--
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
