You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Frédéric Chuong (JIRA)" <ji...@codehaus.org> on 2012/08/22 14:17:21 UTC

[jira] (MEAR-157) FullFileNameMapping should not replace groupId dots with dashes

Frédéric Chuong created MEAR-157:
------------------------------------

             Summary: FullFileNameMapping should not replace groupId dots with dashes
                 Key: MEAR-157
                 URL: https://jira.codehaus.org/browse/MEAR-157
             Project: Maven 2.x Ear Plugin
          Issue Type: Improvement
    Affects Versions: 2.7
         Environment: Maven 3.0.4
            Reporter: Frédéric 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira