aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Meyer (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ARIES-1495) Provide ability to give a name mapping for maven dependencies
Date Mon, 08 Feb 2016 16:12:39 GMT
Thomas Meyer created ARIES-1495:
-----------------------------------

             Summary: Provide ability to give a name mapping for maven dependencies
                 Key: ARIES-1495
                 URL: https://issues.apache.org/jira/browse/ARIES-1495
             Project: Aries
          Issue Type: Improvement
          Components: ESA Maven Plugin
            Reporter: Thomas Meyer


Hi,

the eba-maven-plugin sadly lacks the ability to give a name mapping of maven dependencies
to some provided name in the plugin's configuration in the resulting eba file.

Given a maven dependency:
		<dependency>
			<groupId>com.company</groupId>
			<artifactId>wab-project</artifactId>
			<version>1.2.3</version>
		</dependency>

the resulting eba file will include above dependency as jar file with the file name of the
artefact (wab-project-1.2.3.jar)

Sadly the IBM Websphere Liberty Profile server is very picky about how it resolves the EBA
dependencies.

So when above WAB/JAR is included in the APPLICATION.MF file with:
Application-Content: com.company.wab-project;version="1.2.3", [...]

the WLP server will search it under the name:
com.company.wab-project_1.2.3.jar
 in the root directory of the EBA file.

Normally the maven artefact is named like this:
wab-project-1.2.3.jar

This filename (wab-project-1.2.3.jar) will also be used by the EBA maven in the created EBA
resp. zip file.

It would be nice to provide a file name mapping for the resulting EBA file, like the maven
assembly plugin is capable.

What do you think about this problem?







--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message