[
https://issues.apache.org/jira/browse/HADOOP-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846840#action_12846840
]
Steve Loughran commented on HADOOP-6629:
----------------------------------------
# You can create pom files containing the right versions of dependencies by
having a template POM that is then copied with property expansion. Yes, you may
duplicate stuff in the ivy files, but it ensures the downstream dependencies
are things you want people to get, not random transitive noise
# I'm clearly biased against Maven, so taking a step back here. One limitation
I've found in the past is its view of testing is/wad fairly simplistic. No
test-cases-bring-up-VM-clusters here. It may have moved on.
# There is nothing to stop the Hadoop scripts being published as a tar artifact
on their own, into the repository. It's not common, but the apache repository
charter allows them to do more than just JAR files.
# RPM and deb files could go in as something downstream from the main projects;
take in the JARs, the script tarball, and the test and example JAR files and
create a set of RPM/deb files for installation. Then you need a test process
that test installs these into the target VMs, walks the scripts through their
lifecycle (ssh can do this), etc, etc. If the Hadoop teams do think that RPM
and deb files are the right way to install hadoop artifacts in production, and
don't want to hand off creating these files to others (so complicating support
calls), then it's worth doing. As usual, I have no knowledge of where Maven
stands here; I use the {{<rpmbuild>}} task to create my RPMs, then {{<scp>}}
and {{<ssh>}} to test.
> versions of dependencies should be specified in a single place
> --------------------------------------------------------------
>
> Key: HADOOP-6629
> URL: https://issues.apache.org/jira/browse/HADOOP-6629
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Attachments: HADOOP-6629.patch, HADOOP-6629.patch
>
>
> Currently the Maven POM file is generated from a template file that includes
> the versions of all the libraries we depend on. The versions of these
> libraries are also present in ivy/libraries.properties, so that, when a
> library is updated, it must be updated in two places, which is error-prone.
> We should instead only specify library versions in a single place.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
