[
https://issues.apache.org/jira/browse/HADOOP-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848637#action_12848637
]
Paolo Castagna commented on HADOOP-6629:
----------------------------------------
Thanks Tom. It's better now.
The same can be done for HDFS-1063 and MAPREDUCE-1619.
One last comment on this...
bq. That said, I still don't get Ivy's configurations, and may have made a hash
of them.
I find Ivy's configuration confusing as well and I do not understand the
benefit of having so many. Steve?
Also, I am not sure how to map them to Maven's scopes.
Should we map the "test" configuration to the "test" scope, instead of
"compile"?
{code}
<ivy:makepom ivyfile="${basedir}/ivy.xml" pomfile="${hadoop-core-test.pom}">
<mapping conf="test" scope="compile"/>
</ivy:makepom>
{code}
> 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.
