You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Jonathan Coveney (JIRA)" <ji...@apache.org> on 2012/06/11 20:50:42 UTC
[jira] [Commented] (PIG-2748) Change the names of the jar produced
in the build folder to match maven conventions
[ https://issues.apache.org/jira/browse/PIG-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292976#comment-13292976 ]
Jonathan Coveney commented on PIG-2748:
---------------------------------------
Given that this is apropos of nothing (well, apropos of a much needed conversion to maven which may or may not ever happen), is there a compelling reason to change this? Why not offer a new target with the new names, but keep it as is? I feel like this would break builds for dubious gain.
Though, in theory, I 100% support it.
> Change the names of the jar produced in the build folder to match maven conventions
> -----------------------------------------------------------------------------------
>
> Key: PIG-2748
> URL: https://issues.apache.org/jira/browse/PIG-2748
> Project: Pig
> Issue Type: Bug
> Reporter: Julien Le Dem
> Assignee: Julien Le Dem
>
> {noformat}
> pig-{version}-core.jar becomes pig-{version}.jar
> pig-{version}.jar becomes pig-{version}-withdependencies.jar
> - <property name="output.jarfile" value="${build.dir}/${final.name}.jar" />
> + <property name="output.jarfile" value="${build.dir}/${final.name}-withdependencies.jar" />
> - <property name="output.jarfile.core" value="${build.dir}/${final.name}-core.jar" />
> + <property name="output.jarfile.core" value="${build.dir}/${final.name}.jar" />
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira