[jira] Resolved: (HADOOP-3305) Publish hadoop-core to the apache repository with an appropriate POM file

["Doug Cutting (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting resolved HADOOP-3305.
----------------------------------

    Resolution: Fixed
      Assignee: Giridharan Kesavan

I just committed this, with two changes:
 - add 'unless="offline"' to the downloads of Ivy, so that developers can work offline by specifying 'ant -Doffline=true'.
 - include jars in lib/ directory of release builds, for back-compatibility.


> Publish hadoop-core to the apache repository with an appropriate POM file
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-3305
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3305
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: build
>    Affects Versions: 0.16.2, 0.16.3
>            Reporter: Steve Loughran
>            Assignee: Giridharan Kesavan
>            Priority: Minor
>         Attachments: HADOOP-3305-v3.patch, HADOOP-3305.patch, HADOOP-3305.patch, HADOOP-3305_V2.patch, hadoop-core-0.16.2.pom, ivy-support-first-pass.zip, ivysupport.zip, ivysupport.zip, rmlib-v3.sh, rmlib.sh, rmlib_V2.sh
>
>
> To let people downstream build/test with hadoop, using Apache Ivy or Apache Maven2 to pull it down, hadoop-core needs to be published to the apache repository with a .pom file that lists its mandatory dependencies.
> In an automated build process, this means
> -having a template XML pom defining all included dependencies (and excluded transient dependency artifacts)
> -having a property file driving version numbering of all artifacts
> -copying this template with property expansion to create the release POM file
> -public releases only: sticking this POM file up on people.apache.org in the right place, along with the JAR and some .md5 checksums
> There's a risk that if the hadoop team dont do this, someone else will (as mahout are doing under http://people.apache.org/~kalle/mahout/maven2/org/apache/hadoop/ )
> This is bad as hadoop end up fielding the support calls from someone elses files. 
> Before automating the process, existing hadoop-core JARs can be pushed out with hand-encoded POM files. The repository police dont allow pom files ever to be changed, so supporting existing releases (.16.2, 0.16.3 ... ) is a way of beta testing the POMs. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.