[
http://jira.codehaus.org/browse/MINVOKER-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MINVOKER-4.
-------------------------------
Assignee: Olivier Lamy (was: John Casey)
Resolution: Won't Fix
Fix Version/s: 1.1
I mark this issue as "Won't fix".
IMHO, it's not to the invoker plugin to do this kind of job (use a ci server :
continuum handles this correctly).
The invoker plugin is only here to run unit tests on a set of maven projects
and not to handle dependencies between projects.
The plugin description says :"The invoker Plugin is used to run a set of Maven
projects and makes sure that *each* project execution is successful, and
optionally verifies the output from a given project execution.".
> Use order of invocations as specified in pomIncludes
> ----------------------------------------------------
>
> Key: MINVOKER-4
> URL: http://jira.codehaus.org/browse/MINVOKER-4
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
> Affects Versions: 1.0
> Reporter: Wouter Hermeling
> Assignee: Olivier Lamy
> Fix For: 1.1
>
>
> I use the invoker plugin to create a multi-multiproject build. In fact, this
> is like using maven as a build server.
> It would be nice if the invoker plugins does its invocations in the order as
> specied in pomIncludes, just like maven does on modules in pom projects. Now,
> it seems to use some kind of alphabetical order.
--
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
