[
https://issues.apache.org/jira/browse/HDFS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990677#comment-12990677
]
Steve Loughran commented on HDFS-807:
-------------------------------------
ivy report is essential when you are trying to track down why your build isn't
getting the right version of things, HADOOP-560 makes it more useful.
Similarly, ivy-retrieve is handy to grab all the JAR files. The others, yes,
make them less public. We could improve the ivy-report message.
> Move Ivy related build targets from the list of public targets
> --------------------------------------------------------------
>
> Key: HDFS-807
> URL: https://issues.apache.org/jira/browse/HDFS-807
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.22.0
> Reporter: Konstantin Boudnik
>
> Current list of build targets is quite long. It contains targets that aren't
> normally executed by a user, e.g.
> {noformat}
> ivy-download To download ivy
> ivy-report Generate
> ivy-retrieve Retrieve Ivy-managed artifacts
> ivy-retrieve-checkstyle Retrieve Ivy-managed artifacts for the
> checkstyle configurations
> ivy-retrieve-common Retrieve Ivy-managed artifacts for the compile
> configurations
> ivy-retrieve-javadoc Retrieve Ivy-managed artifacts for the javadoc
> configurations
> ivy-retrieve-jdiff Retrieve Ivy-managed artifacts for the javadoc
> configurations
> ivy-retrieve-releaseaudit Retrieve Ivy-managed artifacts for the compile
> configurations
> ivy-retrieve-test Retrieve Ivy-managed artifacts for the test
> configurations
> {noformat}
> I'd suggest to take these out of the list of top-level build targets
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
