You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2015/06/04 23:39:39 UTC
[jira] [Closed] (MSOURCES-57) jar-no-fork should be changed to
something more meaningful
[ https://issues.apache.org/jira/browse/MSOURCES-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Heinz Marbaise closed MSOURCES-57.
---------------------------------------
Resolution: Won't Fix
Assignee: Karl Heinz Marbaise
The term attached has a different meaning in the maven world. So i close the issue if no one has a better suggestion. Don't hesitate to reopen the issue if you have better ideas.
> jar-no-fork should be changed to something more meaningful
> ----------------------------------------------------------
>
> Key: MSOURCES-57
> URL: https://issues.apache.org/jira/browse/MSOURCES-57
> Project: Maven Source Plugin
> Issue Type: Improvement
> Reporter: Paul Gier
> Assignee: Karl Heinz Marbaise
>
> The names "jar-no-fork" and "test-jar-no-fork" are probably meaningless to the average user. They should be changed to something more descriptive related to their use instead of describing how they work. Maybe "jar-attached" and "test-jar-attached"?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)