[
http://jira.codehaus.org/browse/MANTTASKS-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121435
]
Herve Boutemy commented on MANTTASKS-27:
----------------------------------------
buildlist Ivy task documentation is now here:
http://ant.apache.org/ivy/history/latest-milestone/use/buildlist.html
I doubt the first use case can be done, since I don't see how to find children
pom from a super-pom.
The second one seems more feasible, and ressembles to Ivy's buildlist.
I don't have time to work on this challenging feature, but if someone works on
it, I'll be happy to review: svn location is
http://svn.apache.org/viewvc/maven/ant-tasks/trunk/
> Ant task to determine build order from a super pom, or from a set of poms
> -------------------------------------------------------------------------
>
> Key: MANTTASKS-27
> URL: http://jira.codehaus.org/browse/MANTTASKS-27
> Project: Maven 2.x Ant Tasks
> Issue Type: New Feature
> Environment: all environments
> Reporter: Antoine Levy-Lambert
>
> I am working with the maven-artifact-ant-2.0.4-dep.jar antlib.
> an ant task allowing to determine in which order to build the components
> which are the children of a super pom, or a list of components would be
> useful.
> Ivy has such a task http://www.jayasoft.org/ivy/doc/use/buildlist.
> the following use cases should be supported :
> 1) most simple : take a super pom as input, look for the children poms,
> compute a build order, and create an ant filelist with the build.xml files in
> the right order
> 2) next use case : work from a fileset of build files, assuming there is a
> file called pom.xml in the directory of each build file
> 3) since Maven can support pom files called something else than pom.xml, add
> optionally a mapper to find the pom.xml for a given build.xml
> if someone adds a pointer to the locations in Subversion which need to be
> checked out to prepare such a new task, maybe someone in the community will
> be able to prepare the corresponding task, documentation, testcase.
> I am well aware that this need is not central to Maven. But if this is
> addressed, it can help people who want to first use only the repository
> management functions of maven without migrating to full blown maven
> immediately.
> Regards,
> Antoine
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
