[jira] (MNG-5455) mvn -amd should honour dependencyManagement POM imports

2014-01-23 Thread Jason van Zyl (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339913#comment-339913
 ] 

Jason van Zyl commented on MNG-5455:


DependencyManagement has never affected build ordering because it's a 
specification of a preference for a dependency version, not a dependency 
itself. Therefore it is not used in the calculation for the graph of projects 
to be build when using -am or -amd.

> mvn -amd should honour dependencyManagement POM imports
> ---
>
> Key: MNG-5455
> URL: https://jira.codehaus.org/browse/MNG-5455
> Project: Maven 2 & 3
>  Issue Type: Improvement
>  Components: Dependencies
>Affects Versions: 3.0.4, 3.0.5
> Environment: *JAVA*
> java version "1.7.0_13"
> Java(TM) SE Runtime Environment (build 1.7.0_13-b20)
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
> *MAVEN*
> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 
> 14:51:28+0100)
> Maven home: /home/ansgar/opt/maven3
> Java version: 1.7.0_13, vendor: Oracle Corporation
> Java home: /opt/java/jdk1.7.0_13/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "3.7.9-104.fc17.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: Ansgar Konermann
>
> mvn -amd does not build submodules which depend on a POM via means of a POM
> import in the dependencyManagement section, like so:
> {code}
>   
> 
>   
> amd-test
> dependency-management
> 1.0
> import
> pom
>   
> 
>   
> {code}
> I set up an example project here:
> https://github.com/ansgarkonermann/maven-amd-experiment
> The project has three submodules:
> {code}
>   
> dependency-management
> java-library
> gui
>   
> {code}
> Both 'java-library' and 'gui' import 'dependency-management'.
> We'd expect Maven to build gui and java-library when issuing mvn -amd
> -pl dependency-management, however only dependency-management gets build.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] (MNG-5455) mvn -amd should honour dependencyManagement POM imports

2014-01-23 Thread Jason van Zyl (JIRA)

 [ 
https://jira.codehaus.org/browse/MNG-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl closed MNG-5455.
--

Resolution: Not A Bug

> mvn -amd should honour dependencyManagement POM imports
> ---
>
> Key: MNG-5455
> URL: https://jira.codehaus.org/browse/MNG-5455
> Project: Maven 2 & 3
>  Issue Type: Improvement
>  Components: Dependencies
>Affects Versions: 3.0.4, 3.0.5
> Environment: *JAVA*
> java version "1.7.0_13"
> Java(TM) SE Runtime Environment (build 1.7.0_13-b20)
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
> *MAVEN*
> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 
> 14:51:28+0100)
> Maven home: /home/ansgar/opt/maven3
> Java version: 1.7.0_13, vendor: Oracle Corporation
> Java home: /opt/java/jdk1.7.0_13/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "3.7.9-104.fc17.x86_64", arch: "amd64", family: 
> "unix"
>Reporter: Ansgar Konermann
>
> mvn -amd does not build submodules which depend on a POM via means of a POM
> import in the dependencyManagement section, like so:
> {code}
>   
> 
>   
> amd-test
> dependency-management
> 1.0
> import
> pom
>   
> 
>   
> {code}
> I set up an example project here:
> https://github.com/ansgarkonermann/maven-amd-experiment
> The project has three submodules:
> {code}
>   
> dependency-management
> java-library
> gui
>   
> {code}
> Both 'java-library' and 'gui' import 'dependency-management'.
> We'd expect Maven to build gui and java-library when issuing mvn -amd
> -pl dependency-management, however only dependency-management gets build.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] (MNG-5455) mvn -amd should honour dependencyManagement POM imports

2013-03-19 Thread Ansgar Konermann (JIRA)
Ansgar Konermann created MNG-5455:
-

 Summary: mvn -amd should honour dependencyManagement POM imports
 Key: MNG-5455
 URL: https://jira.codehaus.org/browse/MNG-5455
 Project: Maven 2 & 3
  Issue Type: Improvement
  Components: Dependencies
Affects Versions: 3.0.5, 3.0.4
 Environment: *JAVA*
java version "1.7.0_13"
Java(TM) SE Runtime Environment (build 1.7.0_13-b20)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)

*MAVEN*
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 
14:51:28+0100)
Maven home: /home/ansgar/opt/maven3
Java version: 1.7.0_13, vendor: Oracle Corporation
Java home: /opt/java/jdk1.7.0_13/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "3.7.9-104.fc17.x86_64", arch: "amd64", family: 
"unix"

Reporter: Ansgar Konermann


mvn -amd does not build submodules which depend on a POM via means of a POM
import in the dependencyManagement section, like so:

{code}
  

  
amd-test
dependency-management
1.0
import
pom
  

  
{code}

I set up an example project here:
https://github.com/ansgarkonermann/maven-amd-experiment

The project has three submodules:

{code}
  
dependency-management
java-library
gui
  
{code}

Both 'java-library' and 'gui' import 'dependency-management'.

We'd expect Maven to build gui and java-library when issuing mvn -amd
-pl dependency-management, however only dependency-management gets build.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira