[
https://issues.apache.org/jira/browse/PIG-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Francisoud updated PIG-68:
-----------------------------------
Attachment: build.xml-PIG-68-v03.patch
When I did this patch, I didn't notice that pig.jar was use in script or
documentation.
The fact that this patch set it's name to pig-r1234.jar is convenient on a
developer /release manager point of view but less when it comes to scripts and
documentation like in [deploying pig
page|http://incubator.apache.org/pig/deployment.html]
In this patch version, I added a <copy ...> at the end of the jar target to
make a copy of dist/pig-r1234.jar to pig.jar
> Improving build.xml in many ways :)
> -----------------------------------
>
> Key: PIG-68
> URL: https://issues.apache.org/jira/browse/PIG-68
> Project: Pig
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Benjamin Francisoud
> Priority: Minor
> Attachments: build.xml-PIG-68-v01.patch, build.xml-PIG-68-v02.patch,
> build.xml-PIG-68-v03.patch
>
>
> The build file can be improve in many ways:
> * add revision number to pig.jar name (like: pig-r1234.jar)
> * put pig.jar in the dist dir
> * "clean" target leave a "depend" folder undeleted
> * use a regexp to delete files in "org\apache\pig\impl\logicalLayer\parser"
> folder instead of listing all files one by one that you want to delete
> * put all artifacts (classes, jar, etc...) in the dist folder so that when
> doing clean you just need to specify dist
> * provide a description for targets (for "ant -projecthelp" command)
> * use spaces or tabs but not both (spaces are better for patch and diff in my
> opinion)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
