Maven Shared Components

Maven archiver does not manage empty classifier correctly in manifest.mf classpath

Details

  • Number of attachments :
    0

Description

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

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Cameron Fieber added a comment -

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!

Show
Cameron Fieber added a comment - 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!
Hide
Permalink
Dennis Lundberg added a comment -

Fixed in r1037476.

Show
Dennis Lundberg added a comment - Fixed in r1037476 .

People

  • Assignee:
    Dennis Lundberg
    Reporter:
    fabrice
Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: