[
http://jira.codehaus.org/browse/MDEPLOY-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257903#action_257903
]
Florian Brunner commented on MDEPLOY-93:
----------------------------------------
This is really strange.
I have a project with:
groupId=mySite.myProject
artifact=lib-core
To avoid name clashes (e.g. when copying dependencies to a directory) and to
easily identify a jar in the library view of IDEs (NetBeans, Eclipse), I
renamed the artifacts to:
myProject-${project.artifactId}-v${project.version}
I was surprised that the deployed file name was "lib-core-0.1.jar", which
really doesn't say much about the jar.
I actually don't see the lookup issue. In Nexus the the files are organized
like:
mySite.myProject.artifactId.version
Afterwards the file names should be allowed to have arbitrary names, as long as
the file extensions are correct. It would be slightly more complex, but not
much, I think.
> Deploy plugin does not honor modification of final name by assembly plugin
> --------------------------------------------------------------------------
>
> Key: MDEPLOY-93
> URL: http://jira.codehaus.org/browse/MDEPLOY-93
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Thorsten Möller
> Assignee: Benjamin Bentmann
>
> When using the Maven assembly plugin to create an assembly for a project and
> using "fileName" parameter inside the plugin to change the final name of the
> assembly this new name will not be used by the deploy plugin. The deploy
> plugin always uses the default behavior. The following excerpt from a POM
> illustrates this:
> <groupId>myGoupID</groupId>
> <artifactId>myArtifactID</artifactId>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptors>
>
> <descriptor>src/main/assembly/bin.xml</descriptor>
> </descriptors>
> <appendAssemblyId>false</appendAssemblyId>
> <finalName>foo</finalName>
> <tarLongFileMode>gnu</tarLongFileMode>
> </configuration>
> <executions>
> <execution>
> <id>minimal</id>
> <phase>package</phase>
> <goals>
> <goal>single</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> With this configuration an assembly named "foo.{tar.gz|zip}" will be created
> in the target folder of the project (note that the artifact is attached
> because the assembly plugin is attached to the package lifecycle phase).
> However, when deploying the project file to the distribution repository it
> will be named "myArtifactId.{tar.gz|zip}", which is the default behavior if
> "finalName" is not specified. Interesting is that in the local repository the
> file name always corresponds to what is specified by "fileName", just for the
> distribution repository the parameter is not honored.
> BTW, the other parameter "appendAssemblyId" is honored correctly, i.e,
> depending on the boolean value the assembly Id will be appended to the name,
> or not.
--
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
