[
https://issues.apache.org/jira/browse/PIG-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Slawski updated PIG-4942:
-------------------------------
Attachment: PIG-4942.4.patch
It looks like set-version is required. Otherwise, stale poms files are used
from the ivy directory. (Or, possibly fail because the pom files are not
present for a newly cloned or cleaned repository)
In my test, I changed the pig version to be 0.18.0-SNAPSHOT, however, since
set-version was not performed, these 0.18.0-SNAPSHOT jars were installed as
0.16.0-SNAPSHOT jars:
Installing
/Users/petersla/Projects/Aws157Pig/build/pig-0.18.0-SNAPSHOT-smoketests.jar to
/Users/petersla/.m2/repository/org/apache/pig/pigsmoke/0.16.0-SNAPSHOT/pigsmoke-0.16.0-SNAPSHOT.jar
I have attached an updated patch fixing this. mvn-deploy does depend on
set-version indirectly via mvn-publish.
> Fix mvn-install ant target
> --------------------------
>
> Key: PIG-4942
> URL: https://issues.apache.org/jira/browse/PIG-4942
> Project: Pig
> Issue Type: Bug
> Components: build
> Affects Versions: 0.16.0
> Reporter: Peter Slawski
> Assignee: Peter Slawski
> Fix For: 0.16.1
>
> Attachments: PIG-4942.1.patch, PIG-4942.2.patch, PIG-4942.3.patch,
> PIG-4942.4.patch
>
>
> The mvn-install ant target which allows pig artifacts to be placed in the
> local repository became broken by PIG-4499 in Pig 0.15. That patch removed
> the mvn-jar target which the mvn-install target had dependent on. Instead,
> the jar-h12 target was used as a replacement. However, this target is
> insufficient as it does not move built jars to their expected output
> locations and does not handle well the case where we are building Pig only
> for Hadoop 2 via the {{-Dhadoopversion=23}} option.
> There is an important detail to make note. The {{jar-h12}} target uses
> propertyreset scripts to change the hadoopversion property before it calls
> ant targets to change the behavior of the ant targets. These propertyreset
> scripts do nothing when the {{-Dhadoopversion}} option is provided through
> the command line. This is because ant does not allow overwriting user
> properties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
