[jira] Commented: (MNG-2314) dependencyManagement not inherited more than one level
[ http://jira.codehaus.org/browse/MNG-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90575 ] Cyrill Ruettimann commented on MNG-2314: I still have this issue: The parent pom: dependencyManagement dependencies dependency groupIdcommons-lang/groupId artifactIdcommons-lang/artifactId version2.3/version /dependency dependency groupIdorg.testng/groupId artifactIdtestng/artifactId version5.1/version scopetest/scope classifierjdk14/classifier --- this causes troubles /dependency /dependencies /dependencyManagement The child pom: dependencies dependency groupIdcommons-lang/groupId artifactIdcommons-lang/artifactId scopecompile/scope /dependency dependency groupIdorg.testng/groupId artifactIdtestng/artifactId /dependency /dependencies Running it: + Error stacktraces are turned on. Maven version: 2.0.5 [DEBUG] Building Maven user-level plugin registry from: 'D:\Documents and Settings\t277922\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'D:\Data\t277922\maven-2.0.5\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Searching for parent-POM: com.xxx.swidCTZ.v1.projectgenerator:CTZ_1_ProjectGeneratorBuild::1.0.0-SNAPSHOT of project: com.xxx.swidCTZ.v1.projectgenerator:CTZ_1_ProjectGeneratorJava:jar:1.0.0-SNAPSHOT in relative path: ../CTZ_1_ProjectGeneratorBuild/pom.xml [DEBUG] Using parent-POM from the project hierarchy at: '../CTZ_1_ProjectGeneratorBuild/pom.xml' for project: com.xxx.swidCTZ.v1.projectgenerator:CTZ_1_ProjectGeneratorJava:jar:1.0.0-SNAPSHOT [DEBUG] Searching for parent-POM: com.xxx.CTZ:CTZ_1_I2U8Pom::1.0.0 of project: com.xxx.swidCTZ.v1.projectgenerator:CTZ_1_ProjectGeneratorBuild:pom:1.0.0-SNAPSHOT in relative path: ../pom.xml [DEBUG] Parent-POM: com.xxx.CTZ:CTZ_1_I2U8Pom::1.0.0 not found in relative path: ../pom.xml [DEBUG] Retrieving parent-POM: com.xxx.CTZ:CTZ_1_I2U8Pom::1.0.0 for project: com.xxx.swidCTZ.v1.projectgenerator:CTZ_1_ProjectGeneratorBuild:pom:1.0.0-SNAPSHOT from the repository. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: com.xxx.swidCTZ.v1.projectgenerator:CTZ_1_ProjectGeneratorJava POM Location: D:\Data\Rad\t277922\Projektgenerator\CTZ_1_ProjectGeneratorJava\pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for org.testng:testng Reason: Failed to validate POM [INFO] [DEBUG] Trace org.apache.maven.reactor.MavenExecutionException: Failed to validate POM at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:373) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:286) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to validate POM at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:949) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:760) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:431) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:195) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:523) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:455) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:359) ... 12 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Mar 20 11:31:54 CET 2007 [INFO] Final Memory: 2M/6M [INFO] If I just declare the
[jira] Commented: (SUREFIRE-59) Not compatible with TestNG 5.2: java.lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Z)V
[ http://jira.codehaus.org/browse/SUREFIRE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90576 ] Cyrill Ruettimann commented on SUREFIRE-59: --- Also applies to TestNG 5.5 Not compatible with TestNG 5.2: java.lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Z)V - Key: SUREFIRE-59 URL: http://jira.codehaus.org/browse/SUREFIRE-59 Project: Maven Surefire Issue Type: Improvement Components: TestNG support Environment: plugin artifactIdmaven-surefire-plugin/artifactId version2.2/version /plugin dependency groupIdorg.testng/groupId artifactIdtestng/artifactId version5.2/version classifierjdk15/classifier scopetest/scope /dependency Reporter: Damian Golda Fix For: 2.4 I have project with dependency to testng and surefire plugin as in Environment. I run tests and get exception: org.apache.maven.surefire.booter.SurefireExecutionException: org.testng.xml.XmlSuite.setParallel(Z)V; nested exception i s java.lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Z)V java.lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Z)V at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:135) at org.apache.maven.surefire.Surefire.run(Surefire.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747) Please, correct surefire to be compatible with new testng. -- 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
[jira] Commented: (MNG-2314) dependencyManagement not inherited more than one level
[ http://jira.codehaus.org/browse/MNG-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90581 ] Cyrill Ruettimann commented on MNG-2314: Ok I see. I just wondering about this behavour, since in my opinion the classifier has a smaller impact than the version. If you look at the definition of a dependency: dependency groupIdorg.testng/groupId artifactIdtestng/artifactId version5.1/version scopetest/scope classifierjdk14/classifier /dependency With the classifier you declare to stick with version 5.1, but with a special kind of this version. testng-5.1.jar -- testng-5.1-jdk14.jar The same applies to javadoc and sources (if you upload javadocs and sources with deploy:deploy-file). But maven behaves (what you are saying) different in the case of dependency resolution (at least in reactor builds). The classifier is on the same level as groupId and artifactId. This is different from the view of the repository hierarchy. dependencyManagement not inherited more than one level Key: MNG-2314 URL: http://jira.codehaus.org/browse/MNG-2314 Project: Maven 2 Issue Type: Bug Components: Dependencies, Inheritance and Interpolation Affects Versions: 2.0.4 Reporter: Simon Kepp Nielsen Assigned To: John Casey Fix For: 2.0.5 Attachments: MNG-2314.test.zip Version information from the dependencyManagement section in the parent pom is correctly inherited to dependencies in a child project. But if you try to inherit version information from a grand-parent project, you get the following error: Error Building POM (may not be this project's POM). POM Location: child pom location Validation Messages: [0] 'dependencies.dependency.version' is missing for groupId:artifactId Reason: Failed to validate POM -- 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
