On 04/05/2011 12:31 AM, Brett Porter wrote:
2. mvn --also-make-goals -pl submodule test-compile test
Does the issue make sense now, and is it worth filing a JIRA ticket for this?
It makes sense.
Filed then: http://jira.codehaus.org/browse/MNG-5059
Not sure how it would be implemented, howev
On 05/04/2011, at 1:16 AM, Jesse Glick wrote:
> There seems to be no decent solution using current --also-make. The solutions
> using the styles I proposed previously would look like:
>
> 1. mvn -am -pl submodule test-compile -then -pl submodule test
>
> 2. mvn --also-make-goals -pl submodule
On 10/02/2010 07:27 AM, Brett Porter wrote:
mvn -am -pl main run
would automatically invoke just 'install' (or 'package') on the calculated
dependencies.
I don't agree that "install" on one and package on the dependencies would make
sense - this would put something in the repository that pot
On 10/02/2010 07:27 AM, Brett Porter wrote:
Are there plans for a more clever make mode? The 3.0 compatibility guide
implies that there are, but does not give any specifics.
I'm not sure what you're referring to that gave that indication?
https://cwiki.apache.org/MAVEN/maven-3x-compatibility
On 02/10/2010, at 5:59 AM, Jesse Glick wrote:
> 3. Some way of declaring in general (say, plugin.xml#//mojo/dependencyGoal)
> that a certain goal presupposes a different goal be used on reactor
> dependencies, so that plain
>
> mvn -am -pl main run
>
> would automatically invoke just 'instal
While working on IDE support for running Maven on multi-module projects [1] I have run up against what seems to be a fundamental limitation of --also-make. This "reactor
mode" works fine when the specified goal is standard across all lifecycles in the tree, such as 'install' or 'package'.
But fr
