maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (MEAR-157) FullFileNameMapping should not replace groupId dots with dashes
Date Wed, 04 Nov 2015 12:27:27 GMT

     [ https://issues.apache.org/jira/browse/MEAR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Heinz Marbaise reopened MEAR-157:
--------------------------------------

> FullFileNameMapping should not replace groupId dots with dashes
> ---------------------------------------------------------------
>
>                 Key: MEAR-157
>                 URL: https://issues.apache.org/jira/browse/MEAR-157
>             Project: Maven Ear Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.7
>         Environment: Maven 3.0.4
>            Reporter: frederic.chuong
>
> Using the following configuration for maven-ear-plugin:
> {noformat}
>                 <plugin>
>                     <groupId>org.apache.maven.plugins</groupId>
>                     <artifactId>maven-ear-plugin</artifactId>
>                     <version>2.7</version>
>                     <configuration>
>                         <fileNameMapping>full</fileNameMapping>
>                     </configuration>
>                 </plugin>
> {noformat}
> Considering the following artifact:
> GroupId: org.groupId
> ArtifactId: artifact-id
> Version: 1.2.3
> This generates path having the following form in the EAR file:
> {noformat}
> org-group-id-artifact-id-1.2.3.jar
> {noformat}
> As you can see, the groupId is altered (org-groupId instead of org.groupId).
> This is incompatible with the following archiver CLASSPATH configuration for the EJB
plugin:
> {noformat}
>                 <plugin>
>                     <groupId>org.apache.maven.plugins</groupId>
>                     <artifactId>maven-ejb-plugin</artifactId>
>                     <version>2.3</version>
>                     <configuration>
>                         <archive>
>                             <manifest>
>                                 <addClasspath>true</addClasspath>
>                                 <classpathLayoutType>custom</classpathLayoutType>
>                                 <customClasspathLayout>$${artifact.groupId}-$${artifact.artifactId}-$${artifact.version}$${dashClassifier?}.$${artifact.extension}</customClasspathLayout>
>                             </manifest>
>                         </archive>
>                     </configuration>
>                 </plugin>
> {noformat}
> This archiver configuration generated the following entry in MANIFEST.MF:
> {noformat}
> Class-Path: org.groupId-artifact-id-1.2.3.jar
> {noformat}
> Obviously, this Class-Path entry won't match the filename generated by the Maven EAR
plugin.
> EAR plugin doesn't seem to offer a way to disable replacement neither does Archiver plugin
seem to offer a way to replace dots with dashes.
> Is there a specific reason for replacing dots with dashes?
> As a result, we have to remove the groupId information from the filenames which does'nt
protect us against artifactId conflicts.
> Thanks



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

Mime
View raw message