You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Peter Slawski (JIRA)" <ji...@apache.org> on 2016/07/03 22:56:10 UTC

[jira] [Updated] (PIG-4942) Fix mvn-install ant target

     [ 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.1.patch

The attached patch fixes the mvn-install target so that it works in both desired use cases:
  1. Pig is built for both Hadoop 1 and 2.
  2. Pig is built for only Hadoop 2.
 
Note the second use case is useful for the Apache Bigtop project as they only build Pig for Hadoop 2.

> 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
>         Attachments: PIG-4942.1.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)