You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Maik Richey (JIRA)" <ji...@codehaus.org> on 2010/10/04 10:39:42 UTC
[jira] Created: (MNG-4848) finalName not taken into account for
attached assemblies
finalName not taken into account for attached assemblies
--------------------------------------------------------
Key: MNG-4848
URL: http://jira.codehaus.org/browse/MNG-4848
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 2.2.1
Reporter: Maik Richey
I got a multimodule POM here building two assemblies (jars) attached to the project. Whatever I define in
{code}
<build>
...
<finalName>[The name I want it to be]</finalName>
...
</build>
{code}
is ignored. In the end of the day I'm not able to define the final name of the artifacts?!
--
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
[jira] Commented: (MASSEMBLY-508) finalName not taken into account
for attached assemblies
Posted by "Maik Richey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237365#action_237365 ]
Maik Richey commented on MASSEMBLY-508:
---------------------------------------
So there is no way to change the final name as it is stored on the local/remote repo, right?
Alrigt, then I misunderstood the information found about the <finalName />. Sorry.
> finalName not taken into account for attached assemblies
> --------------------------------------------------------
>
> Key: MASSEMBLY-508
> URL: http://jira.codehaus.org/browse/MASSEMBLY-508
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Reporter: Maik Richey
>
> I got a multimodule POM here building two assemblies (jars) attached to the project. Whatever I define in
> {code}
> <build>
> ...
> <finalName>[The name I want it to be]</finalName>
> ...
> </build>
> {code}
> is ignored. In the end of the day I'm not able to define the final name of the artifacts?!
--
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
[jira] Moved: (MASSEMBLY-508) finalName not taken into account for
attached assemblies
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MNG-4848 to MASSEMBLY-508:
--------------------------------------------------
Complexity: (was: Intermediate)
Affects Version/s: (was: 2.2.1)
Key: MASSEMBLY-508 (was: MNG-4848)
Project: Maven 2.x Assembly Plugin (was: Maven 2 & 3)
> finalName not taken into account for attached assemblies
> --------------------------------------------------------
>
> Key: MASSEMBLY-508
> URL: http://jira.codehaus.org/browse/MASSEMBLY-508
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Reporter: Maik Richey
>
> I got a multimodule POM here building two assemblies (jars) attached to the project. Whatever I define in
> {code}
> <build>
> ...
> <finalName>[The name I want it to be]</finalName>
> ...
> </build>
> {code}
> is ignored. In the end of the day I'm not able to define the final name of the artifacts?!
--
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
[jira] Issue Comment Edited: (MASSEMBLY-508) finalName not taken
into account for attached assemblies
Posted by "Maik Richey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237365#action_237365 ]
Maik Richey edited comment on MASSEMBLY-508 at 10/4/10 4:35 AM:
----------------------------------------------------------------
So there is no way to change the final name as it is stored on the local/remote repo, right?
Alright, then I misunderstood the information found about the <finalName />. Sorry.
was (Author: compi):
So there is no way to change the final name as it is stored on the local/remote repo, right?
Alrigt, then I misunderstood the information found about the <finalName />. Sorry.
> finalName not taken into account for attached assemblies
> --------------------------------------------------------
>
> Key: MASSEMBLY-508
> URL: http://jira.codehaus.org/browse/MASSEMBLY-508
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Reporter: Maik Richey
>
> I got a multimodule POM here building two assemblies (jars) attached to the project. Whatever I define in
> {code}
> <build>
> ...
> <finalName>[The name I want it to be]</finalName>
> ...
> </build>
> {code}
> is ignored. In the end of the day I'm not able to define the final name of the artifacts?!
--
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
[jira] Commented: (MASSEMBLY-508) finalName not taken into account
for attached assemblies
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237364#action_237364 ]
Benjamin Bentmann commented on MASSEMBLY-508:
---------------------------------------------
The name of an artifact in the local/remote repo is exclusively controlled by the repository layout. How the assembly created in the project output directory are named, is controlled by the plugin creating those assemblies.
> finalName not taken into account for attached assemblies
> --------------------------------------------------------
>
> Key: MASSEMBLY-508
> URL: http://jira.codehaus.org/browse/MASSEMBLY-508
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Reporter: Maik Richey
>
> I got a multimodule POM here building two assemblies (jars) attached to the project. Whatever I define in
> {code}
> <build>
> ...
> <finalName>[The name I want it to be]</finalName>
> ...
> </build>
> {code}
> is ignored. In the end of the day I'm not able to define the final name of the artifacts?!
--
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
[jira] Issue Comment Edited: (MASSEMBLY-508) finalName not taken
into account for attached assemblies
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237364#action_237364 ]
Benjamin Bentmann edited comment on MASSEMBLY-508 at 10/4/10 4:28 AM:
----------------------------------------------------------------------
The name of an artifact in the local/remote repo is exclusively controlled by the repository layout. How the assemblies created in the project output directory are named, is controlled by the plugin creating those assemblies.
was (Author: bentmann):
The name of an artifact in the local/remote repo is exclusively controlled by the repository layout. How the assembly created in the project output directory are named, is controlled by the plugin creating those assemblies.
> finalName not taken into account for attached assemblies
> --------------------------------------------------------
>
> Key: MASSEMBLY-508
> URL: http://jira.codehaus.org/browse/MASSEMBLY-508
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Reporter: Maik Richey
>
> I got a multimodule POM here building two assemblies (jars) attached to the project. Whatever I define in
> {code}
> <build>
> ...
> <finalName>[The name I want it to be]</finalName>
> ...
> </build>
> {code}
> is ignored. In the end of the day I'm not able to define the final name of the artifacts?!
--
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
[jira] Closed: (MASSEMBLY-508) finalName not taken into account for
attached assemblies
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-508.
--------------------------------
Resolution: Not A Bug
Assignee: John Casey
> finalName not taken into account for attached assemblies
> --------------------------------------------------------
>
> Key: MASSEMBLY-508
> URL: http://jira.codehaus.org/browse/MASSEMBLY-508
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Reporter: Maik Richey
> Assignee: John Casey
>
> I got a multimodule POM here building two assemblies (jars) attached to the project. Whatever I define in
> {code}
> <build>
> ...
> <finalName>[The name I want it to be]</finalName>
> ...
> </build>
> {code}
> is ignored. In the end of the day I'm not able to define the final name of the artifacts?!
--
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