[jira] (MPIR-288) Add a skipEmptyReport option
[ https://jira.codehaus.org/browse/MPIR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340734#comment-340734 ] Michael Osipov commented on MPIR-288: - Yes, as a whole! > Add a skipEmptyReport option > > > Key: MPIR-288 > URL: https://jira.codehaus.org/browse/MPIR-288 > Project: Maven Project Info Reports Plugin > Issue Type: New Feature >Affects Versions: 2.7 >Reporter: Michael Osipov > > Similar to MPMD-168, it should be possible to skip generation of empty > reports which do not contain any valuable information. > Some canditates are dependencies, cim, scm, issues, mailinglist, etc. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1038) Regression: Method depends on nonexistent group
[
https://jira.codehaus.org/browse/SUREFIRE-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340736#comment-340736
]
Nicolas Liochon commented on SUREFIRE-1038:
---
bq. We should just roll a release some time this month...
Great!
> Regression: Method depends on nonexistent group
> ---
>
> Key: SUREFIRE-1038
> URL: https://jira.codehaus.org/browse/SUREFIRE-1038
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.16
>Reporter: Gili
>Assignee: Andreas Gudian
>Priority: Critical
> Fix For: 2.17
>
> Attachments: SUREFIRE-1038.zip
>
>
> Version 2.16 contains a regression that prevents the use of TestNG groups.
> Version 2.15 works fine.
> When I run my unit tests I get the following error:
> {code}
> Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on
> project web.backend: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed: There was an
> error in the forked process
> org.testng.TestNGException:
> DependencyMap::Method "CallTest.createCall()[pri:0,
> instance:com.vtlr.web.backend.resource.CallTest@53635ac1]" depends on
> nonexistent group "department"
> at org.testng.DependencyMap.getMethodsThatBelongTo(DependencyMap.java:46)
> at org.testng.TestRunner.createDynamicGraph(TestRunner.java:1074)
> at org.testng.TestRunner.privateRun(TestRunner.java:734)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
> at org.testng.TestNG.run(TestNG.java:1057)
> at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:91)
> at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
> at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {code}
> I checked and group "department" exists. Furthermore, downgrading back to
> 2.15 makes the problem go away.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5573) NPE in legacy DefaultWagonManager
[ https://jira.codehaus.org/browse/MNG-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Opalka updated MNG-5573: Environment: Environment agnostic. Affects Version/s: 3.1.1 > NPE in legacy DefaultWagonManager > - > > Key: MNG-5573 > URL: https://jira.codehaus.org/browse/MNG-5573 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.1.1 > Environment: Environment agnostic. >Reporter: Richard Opalka > > When executing the following command: > mvn idea:idea -DdownloadSources=true" -e > I'm getting the following NPE. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea (default-cli) on project > wildfly-cli: Execution default-cli of goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea failed. > NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-idea-plugin:2.2:idea (default-cli) on > project wildfly-cli: Execution default-cli of goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea failed. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-cli of goal org.apache.maven.plugins:maven-idea-plugin:2.2:idea > failed. > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > Caused by: java.lang.NullPointerException > at > org.apache.maven.repository.legacy.DefaultWagonManager.connectWagon(DefaultWagonManager.java:240) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:337) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getArtifact(DefaultWagonManager.java:109) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getArtifact(DefaultWagonManager.java:161) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:155) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.resolveClassifiedArtifact(IdeaModuleMojo.java:966) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.resolveClassifier(IdeaModuleMojo.java:929) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteDependencies(IdeaModuleMojo.java:569) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule(IdeaModuleMojo.java:409) > at > org.apache.maven.plugin.idea.IdeaMojo.rewriteModule(IdeaMojo.java:220) > at org.apache.maven.plugin.idea.IdeaMojo.execute(IdeaMojo.java:200) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > ... 20 more -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5573) NPE in legacy DefaultWagonManager
[ https://jira.codehaus.org/browse/MNG-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Opalka updated MNG-5573: Fix Version/s: 3.2 > NPE in legacy DefaultWagonManager > - > > Key: MNG-5573 > URL: https://jira.codehaus.org/browse/MNG-5573 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.1.1 > Environment: Environment agnostic. >Reporter: Richard Opalka > Fix For: 3.2 > > > When executing the following command: > mvn idea:idea -DdownloadSources=true" -e > I'm getting the following NPE. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea (default-cli) on project > wildfly-cli: Execution default-cli of goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea failed. > NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-idea-plugin:2.2:idea (default-cli) on > project wildfly-cli: Execution default-cli of goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea failed. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-cli of goal org.apache.maven.plugins:maven-idea-plugin:2.2:idea > failed. > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > Caused by: java.lang.NullPointerException > at > org.apache.maven.repository.legacy.DefaultWagonManager.connectWagon(DefaultWagonManager.java:240) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:337) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getArtifact(DefaultWagonManager.java:109) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getArtifact(DefaultWagonManager.java:161) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:155) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.resolveClassifiedArtifact(IdeaModuleMojo.java:966) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.resolveClassifier(IdeaModuleMojo.java:929) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteDependencies(IdeaModuleMojo.java:569) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule(IdeaModuleMojo.java:409) > at > org.apache.maven.plugin.idea.IdeaMojo.rewriteModule(IdeaMojo.java:220) > at org.apache.maven.plugin.idea.IdeaMojo.execute(IdeaMojo.java:200) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > ... 20 more -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1058) TestSetFailedException trying to use maven-surefire-plugin + regular expressions for TestNG groups
[
https://jira.codehaus.org/browse/SUREFIRE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340748#comment-340748
]
Tracey Ruark commented on SUREFIRE-1058:
Sure. Give me some time to whip one up. How should I deliver it? Just zip it
up and attach it here?
> TestSetFailedException trying to use maven-surefire-plugin + regular
> expressions for TestNG groups
> --
>
> Key: SUREFIRE-1058
> URL: https://jira.codehaus.org/browse/SUREFIRE-1058
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.16
>Reporter: Tracey Ruark
>
> I have a Maven project with parent -> child poms. Each child project has
> TestNG tests. What I'd like to be able to do is use regular expressions on
> the TestNG group and execute tests across projects which match the given
> regex.
> Running TestNG tests using a non-regular expression group across projects
> works just fine. For example this works:
> {noformat}mvn test -DargLine="-Denvironment=test"
> -Dgroups="foo.bar.something"{noformat}
> This runs the correct test methods which have that exact tag across all my
> child projects.
> However if I do something like this:
> {noformat}mvn test -DargLine="-Denvironment=test"
> -Dgroups="foo.bar.*"{noformat}
> I get this exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test)
> on project test-automation-ui: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed: There was an
> error in the forked process
> [ERROR] org.apache.maven.surefire.testset.TestSetFailedException: null;
> nested exception is java.lang.reflect.InvocationTargetException: null
> [ERROR] java.lang.reflect.InvocationTargetException
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:601)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGExecutor.getGroupMatchingSelector(TestNGExecutor.java:172)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:66)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> [ERROR] Caused by: org.apache.maven.surefire.group.parse.TokenMgrError:
> Lexical error at line 1, column 13. Encountered: after : ""
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParserTokenManager.getNextToken(GroupMatcherParserTokenManager.java:468)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_scan_token(GroupMatcherParser.java:527)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_7(GroupMatcherParser.java:274)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_3(GroupMatcherParser.java:287)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_3(GroupMatcherParser.java:279)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_1(GroupMatcherParser.java:320)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_1(GroupMatcherParser.java:335)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_2_1(GroupMatcherParser.java:179)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.expr(GroupMatcherParser.java:63)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.parse(GroupMatcherParser.java:56)
> [ERROR] at
> org.apache.maven.surefire.testng.utils.GroupMatcherMethodSelector.setGroups(GroupMatcherMethodSelector.java:83)
> [ERROR] ... 12 more
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> {noformat}
> If I use the bypass surefire and run TestNG directly using same regular
> expression in a testng.xml suite file it works just fine:
> {nofor
[jira] (MNG-5573) NPE in legacy DefaultWagonManager
[ https://jira.codehaus.org/browse/MNG-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5573: --- Fix Version/s: (was: 3.2) > NPE in legacy DefaultWagonManager > - > > Key: MNG-5573 > URL: https://jira.codehaus.org/browse/MNG-5573 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.1.1 > Environment: Environment agnostic. >Reporter: Richard Opalka > > When executing the following command: > mvn idea:idea -DdownloadSources=true" -e > I'm getting the following NPE. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea (default-cli) on project > wildfly-cli: Execution default-cli of goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea failed. > NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-idea-plugin:2.2:idea (default-cli) on > project wildfly-cli: Execution default-cli of goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea failed. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-cli of goal org.apache.maven.plugins:maven-idea-plugin:2.2:idea > failed. > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > Caused by: java.lang.NullPointerException > at > org.apache.maven.repository.legacy.DefaultWagonManager.connectWagon(DefaultWagonManager.java:240) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:337) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getArtifact(DefaultWagonManager.java:109) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getArtifact(DefaultWagonManager.java:161) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:155) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.resolveClassifiedArtifact(IdeaModuleMojo.java:966) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.resolveClassifier(IdeaModuleMojo.java:929) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteDependencies(IdeaModuleMojo.java:569) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule(IdeaModuleMojo.java:409) > at > org.apache.maven.plugin.idea.IdeaMojo.rewriteModule(IdeaMojo.java:220) > at org.apache.maven.plugin.idea.IdeaMojo.execute(IdeaMojo.java:200) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > ... 20 more -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1058) TestSetFailedException trying to use maven-surefire-plugin + regular expressions for TestNG groups
[
https://jira.codehaus.org/browse/SUREFIRE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340755#comment-340755
]
Andreas Gudian commented on SUREFIRE-1058:
--
Yes, just zip and attach to this issue
> TestSetFailedException trying to use maven-surefire-plugin + regular
> expressions for TestNG groups
> --
>
> Key: SUREFIRE-1058
> URL: https://jira.codehaus.org/browse/SUREFIRE-1058
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.16
>Reporter: Tracey Ruark
>
> I have a Maven project with parent -> child poms. Each child project has
> TestNG tests. What I'd like to be able to do is use regular expressions on
> the TestNG group and execute tests across projects which match the given
> regex.
> Running TestNG tests using a non-regular expression group across projects
> works just fine. For example this works:
> {noformat}mvn test -DargLine="-Denvironment=test"
> -Dgroups="foo.bar.something"{noformat}
> This runs the correct test methods which have that exact tag across all my
> child projects.
> However if I do something like this:
> {noformat}mvn test -DargLine="-Denvironment=test"
> -Dgroups="foo.bar.*"{noformat}
> I get this exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test)
> on project test-automation-ui: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed: There was an
> error in the forked process
> [ERROR] org.apache.maven.surefire.testset.TestSetFailedException: null;
> nested exception is java.lang.reflect.InvocationTargetException: null
> [ERROR] java.lang.reflect.InvocationTargetException
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:601)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGExecutor.getGroupMatchingSelector(TestNGExecutor.java:172)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:66)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> [ERROR] Caused by: org.apache.maven.surefire.group.parse.TokenMgrError:
> Lexical error at line 1, column 13. Encountered: after : ""
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParserTokenManager.getNextToken(GroupMatcherParserTokenManager.java:468)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_scan_token(GroupMatcherParser.java:527)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_7(GroupMatcherParser.java:274)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_3(GroupMatcherParser.java:287)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_3(GroupMatcherParser.java:279)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_1(GroupMatcherParser.java:320)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_1(GroupMatcherParser.java:335)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_2_1(GroupMatcherParser.java:179)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.expr(GroupMatcherParser.java:63)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.parse(GroupMatcherParser.java:56)
> [ERROR] at
> org.apache.maven.surefire.testng.utils.GroupMatcherMethodSelector.setGroups(GroupMatcherMethodSelector.java:83)
> [ERROR] ... 12 more
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> {noformat}
> If I use the bypass surefire and run TestNG directly using same regular
> expression in a testng.xml suite file it works just fine:
> {noformat}
> http://testng.org/testng-1.0.dtd"; >
>
>
>
[jira] (SUREFIRE-1058) TestSetFailedException trying to use maven-surefire-plugin + regular expressions for TestNG groups
[
https://jira.codehaus.org/browse/SUREFIRE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tracey Ruark updated SUREFIRE-1058:
---
Attachment: Surefire1058BugExample.zip
Example parent -> child maven project demonstrating this issue. Read the
README for instructions on how to reproduce issues.
> TestSetFailedException trying to use maven-surefire-plugin + regular
> expressions for TestNG groups
> --
>
> Key: SUREFIRE-1058
> URL: https://jira.codehaus.org/browse/SUREFIRE-1058
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.16
>Reporter: Tracey Ruark
> Attachments: Surefire1058BugExample.zip
>
>
> I have a Maven project with parent -> child poms. Each child project has
> TestNG tests. What I'd like to be able to do is use regular expressions on
> the TestNG group and execute tests across projects which match the given
> regex.
> Running TestNG tests using a non-regular expression group across projects
> works just fine. For example this works:
> {noformat}mvn test -DargLine="-Denvironment=test"
> -Dgroups="foo.bar.something"{noformat}
> This runs the correct test methods which have that exact tag across all my
> child projects.
> However if I do something like this:
> {noformat}mvn test -DargLine="-Denvironment=test"
> -Dgroups="foo.bar.*"{noformat}
> I get this exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test)
> on project test-automation-ui: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed: There was an
> error in the forked process
> [ERROR] org.apache.maven.surefire.testset.TestSetFailedException: null;
> nested exception is java.lang.reflect.InvocationTargetException: null
> [ERROR] java.lang.reflect.InvocationTargetException
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:601)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGExecutor.getGroupMatchingSelector(TestNGExecutor.java:172)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:66)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> [ERROR] Caused by: org.apache.maven.surefire.group.parse.TokenMgrError:
> Lexical error at line 1, column 13. Encountered: after : ""
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParserTokenManager.getNextToken(GroupMatcherParserTokenManager.java:468)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_scan_token(GroupMatcherParser.java:527)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_7(GroupMatcherParser.java:274)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_3(GroupMatcherParser.java:287)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_3(GroupMatcherParser.java:279)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_1(GroupMatcherParser.java:320)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_1(GroupMatcherParser.java:335)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_2_1(GroupMatcherParser.java:179)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.expr(GroupMatcherParser.java:63)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.parse(GroupMatcherParser.java:56)
> [ERROR] at
> org.apache.maven.surefire.testng.utils.GroupMatcherMethodSelector.setGroups(GroupMatcherMethodSelector.java:83)
> [ERROR] ... 12 more
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> {noformat}
> If I use the bypass surefire and run TestNG directly using same regular
>
[jira] (SUREFIRE-1058) TestSetFailedException trying to use maven-surefire-plugin + regular expressions for TestNG groups
[
https://jira.codehaus.org/browse/SUREFIRE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340761#comment-340761
]
Tracey Ruark edited comment on SUREFIRE-1058 at 2/6/14 1:42 PM:
Example parent -> child maven project demonstrating this issue attached. Read
the README for instructions on how to reproduce issues.
was (Author: tracey.ruark):
Example parent -> child maven project demonstrating this issue. Read the
README for instructions on how to reproduce issues.
> TestSetFailedException trying to use maven-surefire-plugin + regular
> expressions for TestNG groups
> --
>
> Key: SUREFIRE-1058
> URL: https://jira.codehaus.org/browse/SUREFIRE-1058
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.16
>Reporter: Tracey Ruark
> Attachments: Surefire1058BugExample.zip
>
>
> I have a Maven project with parent -> child poms. Each child project has
> TestNG tests. What I'd like to be able to do is use regular expressions on
> the TestNG group and execute tests across projects which match the given
> regex.
> Running TestNG tests using a non-regular expression group across projects
> works just fine. For example this works:
> {noformat}mvn test -DargLine="-Denvironment=test"
> -Dgroups="foo.bar.something"{noformat}
> This runs the correct test methods which have that exact tag across all my
> child projects.
> However if I do something like this:
> {noformat}mvn test -DargLine="-Denvironment=test"
> -Dgroups="foo.bar.*"{noformat}
> I get this exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test)
> on project test-automation-ui: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed: There was an
> error in the forked process
> [ERROR] org.apache.maven.surefire.testset.TestSetFailedException: null;
> nested exception is java.lang.reflect.InvocationTargetException: null
> [ERROR] java.lang.reflect.InvocationTargetException
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:601)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGExecutor.getGroupMatchingSelector(TestNGExecutor.java:172)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:66)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
> [ERROR] at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> [ERROR] at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> [ERROR] Caused by: org.apache.maven.surefire.group.parse.TokenMgrError:
> Lexical error at line 1, column 13. Encountered: after : ""
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParserTokenManager.getNextToken(GroupMatcherParserTokenManager.java:468)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_scan_token(GroupMatcherParser.java:527)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_7(GroupMatcherParser.java:274)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_3(GroupMatcherParser.java:287)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_3(GroupMatcherParser.java:279)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_1(GroupMatcherParser.java:320)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_1(GroupMatcherParser.java:335)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_2_1(GroupMatcherParser.java:179)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.expr(GroupMatcherParser.java:63)
> [ERROR] at
> org.apache.maven.surefire.group.parse.GroupMatcherParser.parse(GroupMatcherParser.java:56)
> [ERROR] at
> org.apache.maven.surefire.testng.utils.GroupMatcherMethodSelector.setGroups(GroupMatcherMethodSelector.java:83)
> [ERROR] ... 12 more
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of
[jira] (MPLUGIN-257) deprecate classical Maven objects as components
[
https://jira.codehaus.org/browse/MPLUGIN-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPLUGIN-257:
--
Fix Version/s: 3.3
> deprecate classical Maven objects as components
> ---
>
> Key: MPLUGIN-257
> URL: https://jira.codehaus.org/browse/MPLUGIN-257
> Project: Maven Plugin Tools
> Issue Type: Wish
>Affects Versions: 3.2
>Reporter: Herve Boutemy
> Fix For: 3.3
>
>
> such component annotations added in MPLUGIN-204 were a bad idea, because they
> cause confusion with Plexus components
> it's better to remove the feature and add example of {{@Parameter(
> defaultValue="$\{project.xxx}" readonly=true )}}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPLUGIN-257) deprecate classical Maven objects as components
Herve Boutemy created MPLUGIN-257:
-
Summary: deprecate classical Maven objects as components
Key: MPLUGIN-257
URL: https://jira.codehaus.org/browse/MPLUGIN-257
Project: Maven Plugin Tools
Issue Type: Wish
Affects Versions: 3.2
Reporter: Herve Boutemy
such component annotations added in MPLUGIN-204 were a bad idea, because they
cause confusion with Plexus components
it's better to remove the feature and add example of {{@Parameter(
defaultValue="$\{project.xxx}" readonly=true )}}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPLUGIN-257) deprecate classical Maven objects as components
[
https://jira.codehaus.org/browse/MPLUGIN-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPLUGIN-257:
--
Description:
such component annotations added in MPLUGIN-204 were a bad idea, because they
cause confusion with Plexus components
it's better to remove the feature and add examples in documentation:
{code:java}@Parameter( defaultValue="$\{session}" readonly=true )
private MavenSession session;
mavenComponents.put( "org.apache.maven.project.MavenProject", "${project}" );
mavenComponents.put( "org.apache.maven.plugin.MojoExecution", "${mojo}"
);
mavenComponents.put(
"org.apache.maven.plugin.descriptor.PluginDescriptor", "${plugin}" );
mavenComponents.put( "org.apache.maven.settings.Settings",
"${settings}" );
{code}
was:
such component annotations added in MPLUGIN-204 were a bad idea, because they
cause confusion with Plexus components
it's better to remove the feature and add example of {{@Parameter(
defaultValue="$\{project.xxx}" readonly=true )}}
> deprecate classical Maven objects as components
> ---
>
> Key: MPLUGIN-257
> URL: https://jira.codehaus.org/browse/MPLUGIN-257
> Project: Maven Plugin Tools
> Issue Type: Wish
>Affects Versions: 3.2
>Reporter: Herve Boutemy
> Fix For: 3.3
>
>
> such component annotations added in MPLUGIN-204 were a bad idea, because they
> cause confusion with Plexus components
> it's better to remove the feature and add examples in documentation:
> {code:java}@Parameter( defaultValue="$\{session}" readonly=true )
> private MavenSession session;
> mavenComponents.put( "org.apache.maven.project.MavenProject", "${project}" );
>mavenComponents.put( "org.apache.maven.plugin.MojoExecution",
> "${mojo}" );
> mavenComponents.put(
> "org.apache.maven.plugin.descriptor.PluginDescriptor", "${plugin}" );
> mavenComponents.put( "org.apache.maven.settings.Settings",
> "${settings}" );
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPLUGIN-257) deprecate classical Maven objects as components
[
https://jira.codehaus.org/browse/MPLUGIN-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPLUGIN-257:
--
Description:
such component annotations added in MPLUGIN-204 were a bad idea, because they
cause confusion with Plexus components
it's better to remove the feature and add examples in documentation:
{code:java}@Parameter( defaultValue="${session}", readonly=true )
private MavenSession session;
@Parameter( defaultValue="${project}", readonly=true )
private MavenProject project;
@Parameter( defaultValue="${mojo}", readonly=true )
private MojoExecution mojo;
@Parameter( defaultValue="${plugin}", readonly=true )
private PluginDescriptor plugin;
@Parameter( defaultValue="${settings}", readonly=true )
private Settings settings;{code}
was:
such component annotations added in MPLUGIN-204 were a bad idea, because they
cause confusion with Plexus components
it's better to remove the feature and add examples in documentation:
{code:java}@Parameter( defaultValue="$\{session}" readonly=true )
private MavenSession session;
mavenComponents.put( "org.apache.maven.project.MavenProject", "${project}" );
mavenComponents.put( "org.apache.maven.plugin.MojoExecution", "${mojo}"
);
mavenComponents.put(
"org.apache.maven.plugin.descriptor.PluginDescriptor", "${plugin}" );
mavenComponents.put( "org.apache.maven.settings.Settings",
"${settings}" );
{code}
> deprecate classical Maven objects as components
> ---
>
> Key: MPLUGIN-257
> URL: https://jira.codehaus.org/browse/MPLUGIN-257
> Project: Maven Plugin Tools
> Issue Type: Wish
>Affects Versions: 3.2
>Reporter: Herve Boutemy
> Fix For: 3.3
>
>
> such component annotations added in MPLUGIN-204 were a bad idea, because they
> cause confusion with Plexus components
> it's better to remove the feature and add examples in documentation:
> {code:java}@Parameter( defaultValue="${session}", readonly=true )
> private MavenSession session;
> @Parameter( defaultValue="${project}", readonly=true )
> private MavenProject project;
> @Parameter( defaultValue="${mojo}", readonly=true )
> private MojoExecution mojo;
> @Parameter( defaultValue="${plugin}", readonly=true )
> private PluginDescriptor plugin;
> @Parameter( defaultValue="${settings}", readonly=true )
> private Settings settings;{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPLUGIN-258) IT failures with Jdk 8 (EA)
[ https://jira.codehaus.org/browse/MPLUGIN-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MPLUGIN-258: -- Assignee: Robert Scholte > IT failures with Jdk 8 (EA) > > > Key: MPLUGIN-258 > URL: https://jira.codehaus.org/browse/MPLUGIN-258 > Project: Maven Plugin Tools > Issue Type: Bug > Components: maven-plugin-tools-javadoc, Plugin Plugin >Affects Versions: 3.2 >Reporter: Robert Scholte >Assignee: Robert Scholte > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPLUGIN-258) IT failures with Jdk 8 (EA)
Robert Scholte created MPLUGIN-258: -- Summary: IT failures with Jdk 8 (EA) Key: MPLUGIN-258 URL: https://jira.codehaus.org/browse/MPLUGIN-258 Project: Maven Plugin Tools Issue Type: Bug Components: maven-plugin-tools-javadoc, Plugin Plugin Affects Versions: 3.2 Reporter: Robert Scholte -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPLUGIN-258) IT failures with Jdk 8 (EA)
[
https://jira.codehaus.org/browse/MPLUGIN-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MPLUGIN-258:
---
Description:
{noformat:title=Maven Plugin Tools Javadoc}
[INFO] Build Summary:
[INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0
[INFO] -
[ERROR] The following builds failed:
[ERROR] * basic\pom.xml
{noformat}
{noformat:title=Maven Plugin Plugin}
[INFO] Build Summary:
[INFO] Passed: 14, Failed: 7, Errors: 0, Skipped: 0
[INFO] -
[ERROR] The following builds failed:
[ERROR] * ant-basic\pom.xml
[ERROR] * ant-reference-parameter\pom.xml
[ERROR] * ant-simple-usage\pom.xml
[ERROR] * fix-maven-since-3.x\pom.xml
[ERROR] * plugin-info-jdk-default-version\pom.xml
[ERROR] * plugin-report\pom.xml
[ERROR] * plugin-report-annotations\pom.xml
{noformat}
> IT failures with Jdk 8 (EA)
>
>
> Key: MPLUGIN-258
> URL: https://jira.codehaus.org/browse/MPLUGIN-258
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: maven-plugin-tools-javadoc, Plugin Plugin
>Affects Versions: 3.2
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>
> {noformat:title=Maven Plugin Tools Javadoc}
> [INFO] Build Summary:
> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * basic\pom.xml
> {noformat}
> {noformat:title=Maven Plugin Plugin}
> [INFO] Build Summary:
> [INFO] Passed: 14, Failed: 7, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * ant-basic\pom.xml
> [ERROR] * ant-reference-parameter\pom.xml
> [ERROR] * ant-simple-usage\pom.xml
> [ERROR] * fix-maven-since-3.x\pom.xml
> [ERROR] * plugin-info-jdk-default-version\pom.xml
> [ERROR] * plugin-report\pom.xml
> [ERROR] * plugin-report-annotations\pom.xml
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPLUGIN-258) IT failures with Jdk 8 (EA)
[
https://jira.codehaus.org/browse/MPLUGIN-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340769#comment-340769
]
Robert Scholte commented on MPLUGIN-258:
For {{Maven Plugin Tools Javadoc}} the order of attributes has changed within
the javadoc page.
> IT failures with Jdk 8 (EA)
>
>
> Key: MPLUGIN-258
> URL: https://jira.codehaus.org/browse/MPLUGIN-258
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: maven-plugin-tools-javadoc, Plugin Plugin
>Affects Versions: 3.2
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>
> {noformat:title=Maven Plugin Tools Javadoc}
> [INFO] Build Summary:
> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * basic\pom.xml
> {noformat}
> {noformat:title=Maven Plugin Plugin}
> [INFO] Build Summary:
> [INFO] Passed: 14, Failed: 7, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * ant-basic\pom.xml
> [ERROR] * ant-reference-parameter\pom.xml
> [ERROR] * ant-simple-usage\pom.xml
> [ERROR] * fix-maven-since-3.x\pom.xml
> [ERROR] * plugin-info-jdk-default-version\pom.xml
> [ERROR] * plugin-report\pom.xml
> [ERROR] * plugin-report-annotations\pom.xml
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-681) plugin ignores empty finalName and uses default value
[
https://jira.codehaus.org/browse/MASSEMBLY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MASSEMBLY-681:
--
Fix Version/s: 2.5
> plugin ignores empty finalName and uses default value
> -
>
> Key: MASSEMBLY-681
> URL: https://jira.codehaus.org/browse/MASSEMBLY-681
> Project: Maven Assembly Plugin
> Issue Type: Wish
>Affects Versions: 2.4
>Reporter: Paul Millar
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 2.5
>
>
> When used in the 'dir' format, I would argue that an empty finalName is
> reasonable.
> For example, I would expect the following configuration, with the 'dir'
> format, to output the assembled files in ${foo.baseDirectory}
>
>
> src/main/assembly/foo.xml
>
> ${foo.baseDirectory}
>
>
> The actual behaviour is to silently ignore the configured empty finalName and
> use the default finalName value, which is append this to the outputDirectory.
> Arguably there are two bugs here:
> finalName is silently ignored (if this is invalid, it should report an
> error)
> the empty finalName is not honoured.
> Specify '.' as the finalName (.) seems to work as a
> work-around, at least for unix-like systems.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-681) plugin ignores empty finalName and uses default value
[
https://jira.codehaus.org/browse/MASSEMBLY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MASSEMBLY-681:
-
Assignee: Karl Heinz Marbaise
> plugin ignores empty finalName and uses default value
> -
>
> Key: MASSEMBLY-681
> URL: https://jira.codehaus.org/browse/MASSEMBLY-681
> Project: Maven Assembly Plugin
> Issue Type: Wish
>Affects Versions: 2.4
>Reporter: Paul Millar
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 2.5
>
>
> When used in the 'dir' format, I would argue that an empty finalName is
> reasonable.
> For example, I would expect the following configuration, with the 'dir'
> format, to output the assembled files in ${foo.baseDirectory}
>
>
> src/main/assembly/foo.xml
>
> ${foo.baseDirectory}
>
>
> The actual behaviour is to silently ignore the configured empty finalName and
> use the default finalName value, which is append this to the outputDirectory.
> Arguably there are two bugs here:
> finalName is silently ignored (if this is invalid, it should report an
> error)
> the empty finalName is not honoured.
> Specify '.' as the finalName (.) seems to work as a
> work-around, at least for unix-like systems.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1059) Running tests in parallel seems to ignore threadCount
[
https://jira.codehaus.org/browse/SUREFIRE-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340770#comment-340770
]
Henryk Sarat commented on SUREFIRE-1059:
Almost, but I found the solution to my problem by NOT specifying a threadCount
when specifying a threadCountMethods and by specifying perCoreThreadCount.
There is this weird XOR in AbstactSurfireMojo:
{code}
if ( !( getUseUnlimitedThreads() || getThreadCount() > 0 ^
getThreadCountMethods() > 0 ) )
{code}
This if statement was blocked me from entering and executing the statement in
ParallelComputerFactory#resolveConcurrency to get the correct number of threads
if I had threadCount and threadCountMethods set.
Then, inside ParallelComputerFactory#resolveConcurrency, it calls
ParallelComputerFactory#concurrencyFromAllThreadCounts, which sets the number
of threads PER CORE. So by default it was setting the concurrency count to 16
(since I have 8 cores and I'm setting threadCountMethod to 2) and executing 16
threads, not the 2 that I was anticipating.
This might have to be cleaned up a bit to avoid such confusion.
> Running tests in parallel seems to ignore threadCount
> -
>
> Key: SUREFIRE-1059
> URL: https://jira.codehaus.org/browse/SUREFIRE-1059
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.16
>Reporter: Henryk Sarat
>
> I'm trying to run 6 tests in parallel in 2 threads. However, it seems like as
> man threads launch at one time instead of just 2. My proof here is via the
> Thread Id that I print out and because the test finishes in around 18seconds.
> I expect the test to finish in about 38 seconds. I got to this number because
> I have 6 methods that sleep for 10 seconds each. If 2 threads run in
> parallel, then the total run time should be 6methods/2threads = 30 seconds
> (there there is about 8 seconds of build time of everything else). Am I doing
> something wrong? Or has an update over the years broke this in some way?
> POM File:
> {code}
>
>
>
> src/main/resources
> true
>
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.16
>
> methods
> 2
> 2
>
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
> 2.3.2
>
> ${java.version}
> ${java.version}
>
>
>
>
> {code}
> JUnit:
> {code}
>
> junit
> junit
> 4.11
>
> {code}
> Java test class:
> {code}
> public class FourthTest {
> @Test
> public void testOne() throws InterruptedException, ExecutionException,
> IOException {
> for(int i =0;i<10;i++) {
> Thread.sleep(1000);
> System.out.println("one --- " + Thread.currentThread().getId());
> }
> }
> @Test
> public void testTwo() throws InterruptedException, ExecutionException,
> IOException {
> for(int i =0;i<10;i++) {
> Thread.sleep(1000);
> System.out.println("two --- " + Thread.currentThread().getId());
> }
> }
> @Test
> public void testThree() throws InterruptedException, ExecutionException,
> IOException {
> for(int i =0;i<10;i++) {
> Thread.sleep(1000);
> System.out.println("three --- " + Thread.currentThread().getId());
> }
> }
> @Test
> public void testFour() throws InterruptedException, ExecutionException,
> IOException {
> for(int i =0;i<10;i++) {
> Thread.sleep(1000);
> System.out.println("four --- " + Thread.currentThread().getId());
> }
> }
> @Test
> public void testFive() throws InterruptedException, ExecutionException,
> IOException {
> for(int i =0;i<10;i++) {
> Thread.sleep(1000);
> System.out.println("five --- " + Thread.currentThread().getId());
> }
> }
>
> volatile static boolean a = false;
> @Test
> public void testSix() throws InterruptedException, ExecutionException,
> IOException {
> for(int i =0;i<10;i++) {
> Thread.sleep(1000);
> System.out.println("six --- " + Thread.currentThread().getId());
> //if (!a){(new Exception()).printStackTrace(System.out);a=true;}
> }
> }
> }
> {code}
> command line:
> {code}
> mvn clean install test -Dtest=FourthTest -T 2
> {code}
> Output
> {code}
> [INFO] Scanning for projects...
> [I
[jira] (MNG-3608) Reporting Encoding Configuration: ${project.reporting.outputEncoding}
[
https://jira.codehaus.org/browse/MNG-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340776#comment-340776
]
Jason van Zyl commented on MNG-3608:
Just use a standard known property like we do for:
UTF-8
The model doesn't need to be changed for reporting.
> Reporting Encoding Configuration: ${project.reporting.outputEncoding}
> --
>
> Key: MNG-3608
> URL: https://jira.codehaus.org/browse/MNG-3608
> Project: Maven 2 & 3
> Issue Type: Sub-task
> Components: POM, POM::Encoding
>Reporter: Herve Boutemy
> Fix For: Issues to be reviewed for 4.x
>
>
> see [Reporting Encoding Configuration
> proposal|http://docs.codehaus.org/display/MAVEN/Reporting+Encoding+Configuration]
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5479) ExecutionEvent.Type.SessionEnded omited when runtime exception thrown
[
https://jira.codehaus.org/browse/MNG-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340777#comment-340777
]
Jason van Zyl commented on MNG-5479:
Fixed in a7cb1596c1d06cbc20bf23b3c7dede1c8c91b9e0
> ExecutionEvent.Type.SessionEnded omited when runtime exception thrown
> -
>
> Key: MNG-5479
> URL: https://jira.codehaus.org/browse/MNG-5479
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Embedding, IDEs
>Affects Versions: 3.0.4, 3.0.5
>Reporter: Milos Kleint
>Assignee: Jason van Zyl
> Fix For: 3.2
>
> Attachments: maven.patch
>
>
> in LifecycleStarter.java the ExecutionEvent.Type.SessionStarted is always
> fired, but ExecutionEvent.Type.SessionEnded appears only be fired when in
> some cases, omitted in case of RuntimeException thrown. IMHO the event should
> be fired in finally {} block. See attached patch.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5479) ExecutionEvent.Type.SessionEnded omited when runtime exception thrown
[
https://jira.codehaus.org/browse/MNG-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MNG-5479.
--
Resolution: Fixed
> ExecutionEvent.Type.SessionEnded omited when runtime exception thrown
> -
>
> Key: MNG-5479
> URL: https://jira.codehaus.org/browse/MNG-5479
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Embedding, IDEs
>Affects Versions: 3.0.4, 3.0.5
>Reporter: Milos Kleint
>Assignee: Jason van Zyl
> Fix For: 3.2
>
> Attachments: maven.patch
>
>
> in LifecycleStarter.java the ExecutionEvent.Type.SessionStarted is always
> fired, but ExecutionEvent.Type.SessionEnded appears only be fired when in
> some cases, omitted in case of RuntimeException thrown. IMHO the event should
> be fired in finally {} block. See attached patch.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5576) Allow continuous delivery friendly versions
Jason van Zyl created MNG-5576:
--
Summary: Allow continuous delivery friendly versions
Key: MNG-5576
URL: https://jira.codehaus.org/browse/MNG-5576
Project: Maven 2 & 3
Issue Type: Improvement
Affects Versions: 3.1.1
Reporter: Jason van Zyl
Currently warnings will be emitted when there are expressions in versions, a
few exceptions should be deemed valid to make continuous delivery easier. The
use case is to allow easy versioning of an entire multi-module build that can
take a version from an external source like SCM. These are the types of
exceptions that will be allowed:
1.0.0.${changelist}
1.0.0.${revision}
1.0.0.${sha1}
When a whole build is versioned like this we can avoid churning the POMs in the
SCM which makes it a lot easier to see the actual changes in the project. Not a
complete solution for continuous delivery but is a step in the right direction
and doesn't interfere with currently behavior as it is currently allowed, just
warned against.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5576) Allow continuous delivery friendly versions
[
https://jira.codehaus.org/browse/MNG-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-5576:
---
Fix Version/s: 3.2
> Allow continuous delivery friendly versions
> ---
>
> Key: MNG-5576
> URL: https://jira.codehaus.org/browse/MNG-5576
> Project: Maven 2 & 3
> Issue Type: Improvement
>Affects Versions: 3.1.1
>Reporter: Jason van Zyl
> Fix For: 3.2
>
>
> Currently warnings will be emitted when there are expressions in versions, a
> few exceptions should be deemed valid to make continuous delivery easier. The
> use case is to allow easy versioning of an entire multi-module build that can
> take a version from an external source like SCM. These are the types of
> exceptions that will be allowed:
> 1.0.0.${changelist}
> 1.0.0.${revision}
> 1.0.0.${sha1}
> When a whole build is versioned like this we can avoid churning the POMs in
> the SCM which makes it a lot easier to see the actual changes in the project.
> Not a complete solution for continuous delivery but is a step in the right
> direction and doesn't interfere with currently behavior as it is currently
> allowed, just warned against.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5576) Allow continuous delivery friendly versions
[
https://jira.codehaus.org/browse/MNG-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340773#comment-340773
]
Jason van Zyl commented on MNG-5576:
Implemented on 88d0abcd30a0ab040850b3086b3f0ddd8e9607f3
> Allow continuous delivery friendly versions
> ---
>
> Key: MNG-5576
> URL: https://jira.codehaus.org/browse/MNG-5576
> Project: Maven 2 & 3
> Issue Type: Improvement
>Affects Versions: 3.1.1
>Reporter: Jason van Zyl
> Fix For: 3.2
>
>
> Currently warnings will be emitted when there are expressions in versions, a
> few exceptions should be deemed valid to make continuous delivery easier. The
> use case is to allow easy versioning of an entire multi-module build that can
> take a version from an external source like SCM. These are the types of
> exceptions that will be allowed:
> 1.0.0.${changelist}
> 1.0.0.${revision}
> 1.0.0.${sha1}
> When a whole build is versioned like this we can avoid churning the POMs in
> the SCM which makes it a lot easier to see the actual changes in the project.
> Not a complete solution for continuous delivery but is a step in the right
> direction and doesn't interfere with currently behavior as it is currently
> allowed, just warned against.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5576) Allow continuous delivery friendly versions
[
https://jira.codehaus.org/browse/MNG-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MNG-5576.
--
Resolution: Fixed
> Allow continuous delivery friendly versions
> ---
>
> Key: MNG-5576
> URL: https://jira.codehaus.org/browse/MNG-5576
> Project: Maven 2 & 3
> Issue Type: Improvement
>Affects Versions: 3.1.1
>Reporter: Jason van Zyl
> Fix For: 3.2
>
>
> Currently warnings will be emitted when there are expressions in versions, a
> few exceptions should be deemed valid to make continuous delivery easier. The
> use case is to allow easy versioning of an entire multi-module build that can
> take a version from an external source like SCM. These are the types of
> exceptions that will be allowed:
> 1.0.0.${changelist}
> 1.0.0.${revision}
> 1.0.0.${sha1}
> When a whole build is versioned like this we can avoid churning the POMs in
> the SCM which makes it a lot easier to see the actual changes in the project.
> Not a complete solution for continuous delivery but is a step in the right
> direction and doesn't interfere with currently behavior as it is currently
> allowed, just warned against.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5573) NPE in legacy DefaultWagonManager
[ https://jira.codehaus.org/browse/MNG-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340775#comment-340775 ] Jason van Zyl commented on MNG-5573: The maven-idea-plugin is deprecated. There is no reason to use it, importing POMs directly into Intellij works very well. > NPE in legacy DefaultWagonManager > - > > Key: MNG-5573 > URL: https://jira.codehaus.org/browse/MNG-5573 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.1.1 > Environment: Environment agnostic. >Reporter: Richard Opalka > > When executing the following command: > mvn idea:idea -DdownloadSources=true" -e > I'm getting the following NPE. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea (default-cli) on project > wildfly-cli: Execution default-cli of goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea failed. > NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-idea-plugin:2.2:idea (default-cli) on > project wildfly-cli: Execution default-cli of goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea failed. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-cli of goal org.apache.maven.plugins:maven-idea-plugin:2.2:idea > failed. > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > Caused by: java.lang.NullPointerException > at > org.apache.maven.repository.legacy.DefaultWagonManager.connectWagon(DefaultWagonManager.java:240) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:337) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getArtifact(DefaultWagonManager.java:109) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getArtifact(DefaultWagonManager.java:161) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:155) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.resolveClassifiedArtifact(IdeaModuleMojo.java:966) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.resolveClassifier(IdeaModuleMojo.java:929) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteDependencies(IdeaModuleMojo.java:569) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule(IdeaModuleMojo.java:409) > at > org.apache.maven.plugin.idea.IdeaMojo.rewriteModule(IdeaMojo.java:220) > at org.apache.maven.plugin.idea.IdeaMojo.execute(IdeaMojo.java:200) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > ... 20 more -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5573) NPE in legacy DefaultWagonManager
[ https://jira.codehaus.org/browse/MNG-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-5573. -- Resolution: Won't Fix > NPE in legacy DefaultWagonManager > - > > Key: MNG-5573 > URL: https://jira.codehaus.org/browse/MNG-5573 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.1.1 > Environment: Environment agnostic. >Reporter: Richard Opalka > > When executing the following command: > mvn idea:idea -DdownloadSources=true" -e > I'm getting the following NPE. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea (default-cli) on project > wildfly-cli: Execution default-cli of goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea failed. > NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-idea-plugin:2.2:idea (default-cli) on > project wildfly-cli: Execution default-cli of goal > org.apache.maven.plugins:maven-idea-plugin:2.2:idea failed. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-cli of goal org.apache.maven.plugins:maven-idea-plugin:2.2:idea > failed. > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > Caused by: java.lang.NullPointerException > at > org.apache.maven.repository.legacy.DefaultWagonManager.connectWagon(DefaultWagonManager.java:240) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:337) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getArtifact(DefaultWagonManager.java:109) > at > org.apache.maven.repository.legacy.DefaultWagonManager.getArtifact(DefaultWagonManager.java:161) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:155) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.resolveClassifiedArtifact(IdeaModuleMojo.java:966) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.resolveClassifier(IdeaModuleMojo.java:929) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteDependencies(IdeaModuleMojo.java:569) > at > org.apache.maven.plugin.idea.IdeaModuleMojo.rewriteModule(IdeaModuleMojo.java:409) > at > org.apache.maven.plugin.idea.IdeaMojo.rewriteModule(IdeaMojo.java:220) > at org.apache.maven.plugin.idea.IdeaMojo.execute(IdeaMojo.java:200) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > ... 20 more -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5479) ExecutionEvent.Type.SessionEnded omited when runtime exception thrown
[
https://jira.codehaus.org/browse/MNG-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340774#comment-340774
]
Jason van Zyl edited comment on MNG-5479 at 2/6/14 9:06 PM:
Milos, your way is simpler. Just applied your patch.
was (Author: jason):
Milos, you way is simpler. Just applied your patch.
> ExecutionEvent.Type.SessionEnded omited when runtime exception thrown
> -
>
> Key: MNG-5479
> URL: https://jira.codehaus.org/browse/MNG-5479
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Embedding, IDEs
>Affects Versions: 3.0.4, 3.0.5
>Reporter: Milos Kleint
>Assignee: Jason van Zyl
> Fix For: 3.2
>
> Attachments: maven.patch
>
>
> in LifecycleStarter.java the ExecutionEvent.Type.SessionStarted is always
> fired, but ExecutionEvent.Type.SessionEnded appears only be fired when in
> some cases, omitted in case of RuntimeException thrown. IMHO the event should
> be fired in finally {} block. See attached patch.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5479) ExecutionEvent.Type.SessionEnded omited when runtime exception thrown
[
https://jira.codehaus.org/browse/MNG-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340774#comment-340774
]
Jason van Zyl commented on MNG-5479:
Milos, you way is simpler. Just applied your patch.
> ExecutionEvent.Type.SessionEnded omited when runtime exception thrown
> -
>
> Key: MNG-5479
> URL: https://jira.codehaus.org/browse/MNG-5479
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Embedding, IDEs
>Affects Versions: 3.0.4, 3.0.5
>Reporter: Milos Kleint
>Assignee: Jason van Zyl
> Fix For: 3.2
>
> Attachments: maven.patch
>
>
> in LifecycleStarter.java the ExecutionEvent.Type.SessionStarted is always
> fired, but ExecutionEvent.Type.SessionEnded appears only be fired when in
> some cases, omitted in case of RuntimeException thrown. IMHO the event should
> be fired in finally {} block. See attached patch.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5273) Transitive dependencies with scope provided ending up in the final artifact
[
https://jira.codehaus.org/browse/MNG-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-5273:
---
Assignee: Jason van Zyl
> Transitive dependencies with scope provided ending up in the final artifact
> ---
>
> Key: MNG-5273
> URL: https://jira.codehaus.org/browse/MNG-5273
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.0.3, 3.0.4
> Environment: Windows 7, Sun OS 5.1
>Reporter: Ian Phipps
>Assignee: Jason van Zyl
>
> Marking jaxws-rt as a provided dependency:
> {noformat}
> com.sun.xml.ws
> jaxws-rt
> 2.1.4
> provided
> {noformat}
> Correctly resolves jaxb-impl as a provided dependency (dependency:tree output
> from 3.0.3 and 3.0.4):
> {noformat}[INFO] +- com.sun.xml.ws:jaxws-rt:jar:2.1.4:provided
> [INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.1.7:provided
> [INFO] | +- com.sun.xml.stream.buffer:streambuffer:jar:0.7:provided
> [INFO] | +- com.sun.xml.stream:sjsxp:jar:1.0.1:provided
> [INFO] | +- org.jvnet.staxex:stax-ex:jar:1.2:provided
> [INFO] | +- com.sun.org.apache.xml.internal:resolver:jar:20050927:provided
> [INFO] | \- org.jvnet:mimepull:jar:1.2:provided {noformat}
> But for some reason, in Maven 3 (tried 3.0.3 and 3.0.4), using a packaging
> type of "war", jaxb-impl-2.1.7 ends up in the final artifact.
> It is correctly omitted from the final artifact in maven 2.x.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5255) Dependency with 'provided' scope has its transitive dependency included in final artifact
[ https://jira.codehaus.org/browse/MNG-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5255: --- Assignee: Jason van Zyl > Dependency with 'provided' scope has its transitive dependency included in > final artifact > - > > Key: MNG-5255 > URL: https://jira.codehaus.org/browse/MNG-5255 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0.4 > Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800) > Maven home: D:\bin\apache-maven-3.0.4 > Java version: 1.6.0_27, vendor: Sun Microsystems Inc. > Java home: D:\bin\java\jdk1.6.0_27\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" >Reporter: Bart Skondin >Assignee: Jason van Zyl > Attachments: provided-scope-not-working.zip > > > Expected: A dependency declared with a scope of 'provided', along with any > transitive dependencies, should not be included in the final artifact. > Actual: I have a dependency, jsp-api, declared with 'provided' scope. This > dependency has a dependency of its own, servlet-api. The servlet-api.jar is > being included in the web-inf/lib folder of the resultant war file. > Background: We recently upgraded from Maven 2.2.1 to Maven 3.0.4. The problem > was not witnessed until after the upgrade. > Steps to Reproduce: Run mvn install, then have a look at the web-inf/lib > folder. Notice that the servlet-api.jar has been included. > Additional Info: It seems that I can only reproduce this behavior when > declaring a specific dependency in my pom, spring-ldap. Here is the > dependency tree for the given pared-down project (attached): > --- maven-dependency-plugin:2.1:tree (default-cli) @ > provided-scope-not-working --- > com.bug.example:provided-scope-not-working:war:0.0.1-SNAPSHOT > +- javax.servlet:jsp-api:jar:2.0:provided > | \- javax.servlet:servlet-api:jar:2.4:provided > \- org.springframework.ldap:spring-ldap:jar:1.2.1:compile >+- commons-logging:commons-logging:jar:1.0.4:compile >+- commons-lang:commons-lang:jar:2.1:compile >+- org.springframework:spring-beans:jar:2.0.6:compile >| +- (commons-logging:commons-logging:jar:1.1:compile - omitted for > conflict with 1.0.4) >| \- (org.springframework:spring-core:jar:2.0.6:compile - omitted for > duplicate) >\- org.springframework:spring-core:jar:2.0.6:compile > \- (commons-logging:commons-logging:jar:1.1:compile - omitted for > conflict with 1.0.4) -- This message was sent by Atlassian JIRA (v6.1.6#6162)
