[jira] Created: (MNG-1958) we need a var that always points to the root direcotry in multi module builds

we need a var that always points to the root direcotry in multi module builds - Key: MNG-1958 URL: http://jira.codehaus.org/browse/MNG-1958 Project: Maven 2 Type: Improvement Reporter:

[jira] Commented: (MNG-441) surefire plugin needs to be able to fork tests

[ http://jira.codehaus.org/browse/MNG-441?page=comments#action_52064 ] Mark Proctor commented on MNG-441: -- Is that .java and .pom working? If so any chance we could have a surefire snapshot release? We are currently blocked from moving Drools to M2 as

[jira] Created: (MNG-1692) Project scoped Repository

Project scoped Repository - Key: MNG-1692 URL: http://jira.codehaus.org/browse/MNG-1692 Project: Maven 2 Type: Wish Components: Artifacts and Repositories Reporter: Mark Proctor Fix For: 2.1 In multi module builds I would like

[jira] Created: (MNG-1694) Build execution order control in fine grained projects.

Build execution order control in fine grained projects. --- Key: MNG-1694 URL: http://jira.codehaus.org/browse/MNG-1694 Project: Maven 2 Type: Wish Components: maven-compiler-plugin Reporter: Mark Proctor

[jira] Commented: (MNG-1694) Build execution order control in fine grained projects.

[ http://jira.codehaus.org/browse/MNG-1694?page=comments#action_52114 ] Mark Proctor commented on MNG-1694: --- skipping is fine by me, as long as its fast. Thats what I did for M1, I implemented my own build goal that iterates the reactor and calls jar:jar

[jira] Commented: (MNG-710) Add ability to fork the maven-compiler-plugin

[ http://jira.codehaus.org/browse/MNG-710?page=comments#action_52044 ] Mark Proctor commented on MNG-710: -- Will this allow different java versions to be specified on a per module basis, in a multi module build? Add ability to fork the

[jira] Commented: (MAVEN-1545) Specify target jdk per project in multibuild

[ http://jira.codehaus.org/browse/MAVEN-1545?page=comments#action_38727 ] Mark Proctor commented on MAVEN-1545: - Brett, Not quite so simple. Groovy would not compiled under jdk1.5, so we had to do our own custom jdk forking within maven, not nice,

[jira] Commented: (MAVEN-1545) Specify target jdk per project in multibuild

[ http://jira.codehaus.org/browse/MAVEN-1545?page=comments#action_38728 ] Mark Proctor commented on MAVEN-1545: - I forgot to mention that b) would not solve the groovy issue. b) set maven.compile.source, maven.compile.target appropriately for

[jira] Commented: (MAVEN-1545) Specify target jdk per project in multibuild

[ http://jira.codehaus.org/browse/MAVEN-1545?page=comments#action_38729 ] Mark Proctor commented on MAVEN-1545: - I'm adding this converation bob and I had with trygvis, to see if it sheds any more light: [13:35] trygvis why didn't brett's solution