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

Michael Osipov closed MANTTASKS-27.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period 
of time. If you think this issue still applies, retest your problem with the 
most recent version of Maven and the affected component, reopen and post your 
results.

> Ant task to determine build order from a super pom, or from a set of poms
> -------------------------------------------------------------------------
>
>                 Key: MANTTASKS-27
>                 URL: https://issues.apache.org/jira/browse/MANTTASKS-27
>             Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to