[jira] [Commented] (SUREFIRE-1303) The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[Maciej Tondyra (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15682811#comment-15682811
 ] 

Maciej Tondyra commented on SUREFIRE-1303:
--

So, I added clean and today this error happen again.
I'm still looking solutions

> The forked VM terminated without properly saying goodbye. VM crash or 
> System.exit called?
> -
>
> Key: SUREFIRE-1303
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1303
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Maciej Tondyra
>
> I have some error. I do not know what do. Can you help me? If add some other 
> log please let me know.
> [JENKINS] Recording test results
> hudson.AbortException: Test reports were found but none of them are new. Did 
> tests run? 
> For example, 
> c:\jenkins\workspace\automatic-tests\target\surefire-reports\TEST-TestSuite.xml
>  is 9 hr 49 min old
>   at hudson.tasks.junit.TestResult.parse(TestResult.java:216)
>   at 
> hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:148)
>   at 
> hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:634)
>   at 
> hudson.maven.Maven3Builder$MavenExecutionListener.mojoFailed(Maven3Builder.java:667)
>   at 
> hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:311)
>   at 
> org.apache.maven.eventspy.internal.EventSpyDispatcher.onEvent(EventSpyDispatcher.java:104)
>   at 
> org.apache.maven.eventspy.internal.EventSpyExecutionListener.mojoFailed(EventSpyExecutionListener.java:138)
>   at 
> org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:90)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:219)
>   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:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>   at 
> org.jvnet.hudson.maven3.launcher.Maven32Launcher.main(Maven32Launcher.java:132)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
>   at jenkins.maven3.agent.Maven32Main.launch(Maven32Main.java:186)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at hudson.maven.Maven3Builder.call(Maven3Builder.java:136)
>   at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)
>   at hudson.remoting.UserRequest.perform(UserRequest.java:121)
>   at hudson.remoting.UserRequest.perform(UserRequest.java:49)
>   at hudson.remoting.Request$2.run(Request.java:326)
>   at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Started calculate disk usage of build
> Finished Calculation of disk usage of build in 0 seconds
> Started calculate disk usage of workspace
> Finished Calculation of disk usage of workspace in  56 second
> [INFO] 
> 
> [INFO] BUILD FAILURE
> 

[jira] [Commented] (SUREFIRE-1305) surefire fails on parallel tests when newline character is in test description

[Tibor Digana (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15682426#comment-15682426
 ] 

Tibor Digana commented on SUREFIRE-1305:


[~piotr.turski]
I guess the custom runner does not satisfy the interface of {{Description}}. We 
have to extract method and class from it which is important to run method 
and/or class in parallel.
Try to attach Surefire source, run it in debug mode and debug classes 
{{ConcurrentRunListener}} and {{JUnitCoreRunListener}}. There is no {{TestSet}} 
for {{Description}}. Is the runner mutating the description?

You should debug the method {{fillTestCountMap}} in class 
{{JUnitCoreRunListener}}. Either the class name does not come to the map 
{{classMethodCounts}} or the description of class was mutated before 
{{ConcurrentRunListener#testStarting()}}.
The JUnit description must be parsed successfully in 
{{JUnit4RunListener#testStarted( Description description )}}.

> surefire fails on parallel tests when newline character is in test description
> --
>
> Key: SUREFIRE-1305
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1305
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Piotr Turski
>Assignee: Tibor Digana
>
> zohhak runner may create test description with newline character in it. it 
> runs without any problem with surefire and non-parallel build and with 
> parallel build when there is no newline char in the description. furthermore 
> it runs fine with plain junit in parallel mode
> * original issue was reported here: 
> https://github.com/piotrturski/zohhak/issues/14
> * project that reproduces the issue: 
> https://github.com/christophpickl/zohhak_parallel_bug
> * working parallel junit tests without surefire: 
> https://github.com/piotrturski/zohhak/commit/806aafc8e09fd843753d2940991f3ca0edd5120d



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (SUREFIRE-1305) surefire fails on parallel tests when newline character is in test description

[Piotr Turski (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681920#comment-15681920
 ] 

Piotr Turski edited comment on SUREFIRE-1305 at 11/20/16 10:11 PM:
---

still a bug but a bit different output. i took the project that reproduces the 
issue, added:
{code:xml}
   

apache.snapshots
http://repository.apache.org/snapshots/


{code}
and changed version to
{code}
 2.19.2-SNAPSHOT
{code}
and after running tests:
{noformat}
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building playground 1.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
playground ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/x/zohhak_parallel_bug/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ playground 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
playground ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
//zohhak_parallel_bug/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ 
playground ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.19.2-SNAPSHOT:test (default-test) @ 
playground ---
[INFO] 
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running testMethod
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
testMethod
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 2.240s
[INFO] Finished at: Sun Nov 20 23:01:58 CET 2016
[INFO] Final Memory: 11M/303M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.2-SNAPSHOT:test 
(default-test) on project playground: Execution default-test of goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.2-SNAPSHOT:test failed: 
There was an error in the forked process
[ERROR] org.apache.maven.surefire.testset.TestSetFailedException: Test 
mechanism :: null
[ERROR] at 
org.apache.maven.surefire.common.junit4.JUnit4RunListener.rethrowAnyTestMechanismFailures(JUnit4RunListener.java:210)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:138)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:157)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:300)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:251)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:130)
[ERROR] Caused by: java.lang.NullPointerException
[ERROR] at 
org.apache.maven.surefire.junitcore.ConcurrentRunListener.testStarting(ConcurrentRunListener.java:134)
[ERROR] at 
org.apache.maven.surefire.common.junit4.JUnit4RunListener.testStarted(JUnit4RunListener.java:93)
[ERROR] at 
org.junit.runner.notification.SynchronizedRunListener.testStarted(SynchronizedRunListener.java:49)
[ERROR] at 
org.junit.runner.notification.RunNotifier$3.notifyListener(RunNotifier.java:121)
[ERROR] at 
org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
[ERROR] at 
org.junit.runner.notification.RunNotifier.fireTestStarted(RunNotifier.java:118)
[ERROR] at 
org.apache.maven.surefire.common.junit4.Notifier.fireTestStarted(Notifier.java:100)
[ERROR] at 
org.junit.internal.runners.model.EachTestNotifier.fireTestStarted(EachTestNotifier.java:42)
[ERROR] at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:323)
[ERROR] at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
[ERROR] at 

[jira] [Commented] (SUREFIRE-1305) surefire fails on parallel tests when newline character is in test description

[Piotr Turski (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681920#comment-15681920
 ] 

Piotr Turski commented on SUREFIRE-1305:


still a bug. i took the project that reproduces the issue, added:
{code:xml}
   

apache.snapshots
http://repository.apache.org/snapshots/


{code}
and changed version to
{code}
 2.19.2-SNAPSHOT
{code}
and after running tests:
{noformat}
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building playground 1.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
playground ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/x/zohhak_parallel_bug/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ playground 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
playground ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
//zohhak_parallel_bug/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ 
playground ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.19.2-SNAPSHOT:test (default-test) @ 
playground ---
[INFO] 
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running testMethod
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
testMethod
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 2.240s
[INFO] Finished at: Sun Nov 20 23:01:58 CET 2016
[INFO] Final Memory: 11M/303M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.2-SNAPSHOT:test 
(default-test) on project playground: Execution default-test of goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.2-SNAPSHOT:test failed: 
There was an error in the forked process
[ERROR] org.apache.maven.surefire.testset.TestSetFailedException: Test 
mechanism :: null
[ERROR] at 
org.apache.maven.surefire.common.junit4.JUnit4RunListener.rethrowAnyTestMechanismFailures(JUnit4RunListener.java:210)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:138)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
[ERROR] at 
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:157)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:300)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:251)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:130)
[ERROR] Caused by: java.lang.NullPointerException
[ERROR] at 
org.apache.maven.surefire.junitcore.ConcurrentRunListener.testStarting(ConcurrentRunListener.java:134)
[ERROR] at 
org.apache.maven.surefire.common.junit4.JUnit4RunListener.testStarted(JUnit4RunListener.java:93)
[ERROR] at 
org.junit.runner.notification.SynchronizedRunListener.testStarted(SynchronizedRunListener.java:49)
[ERROR] at 
org.junit.runner.notification.RunNotifier$3.notifyListener(RunNotifier.java:121)
[ERROR] at 
org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
[ERROR] at 
org.junit.runner.notification.RunNotifier.fireTestStarted(RunNotifier.java:118)
[ERROR] at 
org.apache.maven.surefire.common.junit4.Notifier.fireTestStarted(Notifier.java:100)
[ERROR] at 
org.junit.internal.runners.model.EachTestNotifier.fireTestStarted(EachTestNotifier.java:42)
[ERROR] at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:323)
[ERROR] at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
[ERROR] at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
[ERROR] at 

[jira] [Commented] (MINSTALL-131) Rename package to org.apache.maven.plugins

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINSTALL-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681843#comment-15681843
 ] 

Hudson commented on MINSTALL-131:
-

SUCCESS: Integrated in Jenkins build maven-plugins #7733 (See 
[https://builds.apache.org/job/maven-plugins/7733/])
[MINSTALL-131] Rename package to org.apache.maven.plugins

With the migration to Maven 3, the main package should be 
"org.apache.maven.plugins" instead of the current "org.apache.maven.plugin". 
(gboue: [http://svn.apache.org/viewvc/?view=rev=1770586])
* (edit) maven-install-plugin/src/it/attach-jar-checksum/verify.bsh
* (edit) maven-install-plugin/src/it/generate-pom-auto-1/verify.bsh
* (edit) maven-install-plugin/src/it/jar-sources-javadoc/verify.bsh
* (edit) 
maven-install-plugin/src/it/local-repo-override-with-checksum-generatePom/verify.bsh
* (edit) 
maven-install-plugin/src/it/local-repo-override-with-checksum/verify.bsh
* (edit) maven-install-plugin/src/it/pom-checksum/verify.bsh
* (delete) maven-install-plugin/src/main/java/org/apache/maven/plugin
* (add) maven-install-plugin/src/main/java/org/apache/maven/plugins
* (add) maven-install-plugin/src/main/java/org/apache/maven/plugins/install
* (edit) 
maven-install-plugin/src/main/java/org/apache/maven/plugins/install/AbstractInstallMojo.java
* (edit) 
maven-install-plugin/src/main/java/org/apache/maven/plugins/install/InstallFileMojo.java
* (edit) 
maven-install-plugin/src/main/java/org/apache/maven/plugins/install/InstallMojo.java
* (delete) maven-install-plugin/src/test/java/org/apache/maven/plugin
* (add) maven-install-plugin/src/test/java/org/apache/maven/plugins
* (add) maven-install-plugin/src/test/java/org/apache/maven/plugins/install
* (add) 
maven-install-plugin/src/test/java/org/apache/maven/plugins/install/InstallFileMojoTest.java
* (add) 
maven-install-plugin/src/test/java/org/apache/maven/plugins/install/InstallMojoTest.java
* (add) 
maven-install-plugin/src/test/java/org/apache/maven/plugins/install/Utils.java
* (add) 
maven-install-plugin/src/test/java/org/apache/maven/plugins/install/stubs
* (edit) 
maven-install-plugin/src/test/java/org/apache/maven/plugins/install/stubs/AttachedArtifactStub0.java
* (edit) 
maven-install-plugin/src/test/java/org/apache/maven/plugins/install/stubs/AttachedArtifactStub1.java
* (edit) 
maven-install-plugin/src/test/java/org/apache/maven/plugins/install/stubs/InstallArtifactStub.java
* (edit) 
maven-install-plugin/src/test/resources/unit/basic-install-checksum/plugin-config.xml
* (edit) 
maven-install-plugin/src/test/resources/unit/basic-install-test-packaging-pom/plugin-config.xml
* (edit) 
maven-install-plugin/src/test/resources/unit/basic-install-test-with-attached-artifacts/plugin-config.xml
* (edit) 
maven-install-plugin/src/test/resources/unit/basic-install-test/plugin-config.xml
* (edit) 
maven-install-plugin/src/test/resources/unit/configured-install-test/plugin-config.xml


> Rename package to org.apache.maven.plugins
> --
>
> Key: MINSTALL-131
> URL: https://issues.apache.org/jira/browse/MINSTALL-131
> Project: Maven Install Plugin
>  Issue Type: Task
>Affects Versions: 2.5.2
>Reporter: Guillaume Boué
>Assignee: Guillaume Boué
>Priority: Minor
> Fix For: 3.0.0
>
>
> As per [Plugin migration to Maven3 
> dependencies|https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies],
>  the package should be renamed to "org.apache.maven.plugins".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MINSTALL-131) Rename package to org.apache.maven.plugins

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MINSTALL-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Boué closed MINSTALL-131.
---
Resolution: Fixed

> Rename package to org.apache.maven.plugins
> --
>
> Key: MINSTALL-131
> URL: https://issues.apache.org/jira/browse/MINSTALL-131
> Project: Maven Install Plugin
>  Issue Type: Task
>Affects Versions: 2.5.2
>Reporter: Guillaume Boué
>Assignee: Guillaume Boué
>Priority: Minor
> Fix For: 3.0.0
>
>
> As per [Plugin migration to Maven3 
> dependencies|https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies],
>  the package should be renamed to "org.apache.maven.plugins".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MINSTALL-131) Rename package to org.apache.maven.plugins

[JIRA]

[ 
https://issues.apache.org/jira/browse/MINSTALL-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681824#comment-15681824
 ] 

Guillaume Boué commented on MINSTALL-131:
-

Fixed in [r1770586|http://svn.apache.org/viewvc?rev=1770586=rev].

> Rename package to org.apache.maven.plugins
> --
>
> Key: MINSTALL-131
> URL: https://issues.apache.org/jira/browse/MINSTALL-131
> Project: Maven Install Plugin
>  Issue Type: Task
>Affects Versions: 2.5.2
>Reporter: Guillaume Boué
>Assignee: Guillaume Boué
>Priority: Minor
> Fix For: 3.0.0
>
>
> As per [Plugin migration to Maven3 
> dependencies|https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies],
>  the package should be renamed to "org.apache.maven.plugins".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MINSTALL-131) Rename package to org.apache.maven.plugins

[JIRA]

Guillaume Boué created MINSTALL-131:
---

 Summary: Rename package to org.apache.maven.plugins
 Key: MINSTALL-131
 URL: https://issues.apache.org/jira/browse/MINSTALL-131
 Project: Maven Install Plugin
  Issue Type: Task
Affects Versions: 2.5.2
Reporter: Guillaume Boué
Assignee: Guillaume Boué
Priority: Minor
 Fix For: 3.0.0


As per [Plugin migration to Maven3 
dependencies|https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies],
 the package should be renamed to "org.apache.maven.plugins".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-6084) Support JSR250 annotations

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681706#comment-15681706
 ] 

ASF GitHub Bot commented on MNG-6084:
-

Github user mfriedenhagen commented on a diff in the pull request:


https://github.com/apache/maven-integration-testing/pull/15#discussion_r88809229
  
--- Diff: 
core-it-suite/src/test/java/org/apache/maven/it/MavenITmng6084Jsr250PluginTest.java
 ---
@@ -0,0 +1,84 @@
+package org.apache.maven.it;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import org.apache.maven.it.util.ResourceExtractor;
+
+import java.io.File;
+
+/**
+ * This is a test set for https://issues.apache.org/jira/browse/MNG-6084;>MNG-6084.
+ *
+ * @author Jason van Zyl
--- End diff --

Is Jason really the author :-)


> Support JSR250 annotations
> --
>
> Key: MNG-6084
> URL: https://issues.apache.org/jira/browse/MNG-6084
> Project: Maven
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Dan Tran
>
> JSR330 ( @Named, @Singeton, etc) currently supported for plugin development.  
> Would like to see JSR250 as well(@PostConstruct, etc)
> Detail discussion is at  
> http://maven.40175.n5.nabble.com/Maven-Plugin-and-JSR330-td5879508.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MPLUGIN-315) improve mojo description: show parameter name as

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPLUGIN-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681672#comment-15681672
 ] 

Hudson commented on MPLUGIN-315:


SUCCESS: Integrated in Jenkins build maven-plugin-tools #273 (See 
[https://builds.apache.org/job/maven-plugin-tools/273/])
[MPLUGIN-315] improve mojo description: show parameter name as  
(rfscholte: [http://svn.apache.org/viewvc/?view=rev=1770579])
* (edit) 
maven-plugin-tools-generators/src/main/java/org/apache/maven/tools/plugin/generator/PluginXdocGenerator.java
* (edit) maven-plugin-tools-generators/src/main/resources/pluginxdoc.properties
* (edit) 
maven-plugin-tools-generators/src/main/resources/pluginxdoc_fr.properties


> improve mojo description: show parameter name as 
> 
>
> Key: MPLUGIN-315
> URL: https://issues.apache.org/jira/browse/MPLUGIN-315
> Project: Maven Plugin Tools
>  Issue Type: Improvement
>  Components: Plugin Plugin
>Affects Versions: 3.5
>Reporter: Hervé Boutemy
>Assignee: Robert Scholte
> Fix For: 3.5.1
>
>
> since parameters are intended to be put in pom.xml, generating {{}} 
> will improve expressiveness of the documentation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (SUREFIRE-1305) surefire fails on parallel tests when newline character is in test description

[Tibor Digana (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana reassigned SUREFIRE-1305:
--

Assignee: Tibor Digana

> surefire fails on parallel tests when newline character is in test description
> --
>
> Key: SUREFIRE-1305
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1305
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Piotr Turski
>Assignee: Tibor Digana
>
> zohhak runner may create test description with newline character in it. it 
> runs without any problem with surefire and non-parallel build and with 
> parallel build when there is no newline char in the description. furthermore 
> it runs fine with plain junit in parallel mode
> * original issue was reported here: 
> https://github.com/piotrturski/zohhak/issues/14
> * project that reproduces the issue: 
> https://github.com/christophpickl/zohhak_parallel_bug
> * working parallel junit tests without surefire: 
> https://github.com/piotrturski/zohhak/commit/806aafc8e09fd843753d2940991f3ca0edd5120d



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SUREFIRE-1305) surefire fails on parallel tests when newline character is in test description

[Tibor Digana (JIRA)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681670#comment-15681670
 ] 

Tibor Digana commented on SUREFIRE-1305:


[~piotr.turski]
Can you check it out with Version 2.19.2-SNAPSHOT?
Method {{#rethrowAnyTestMechanismFailures()}} changed and I think it should not 
throw NPE.

> surefire fails on parallel tests when newline character is in test description
> --
>
> Key: SUREFIRE-1305
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1305
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Piotr Turski
>
> zohhak runner may create test description with newline character in it. it 
> runs without any problem with surefire and non-parallel build and with 
> parallel build when there is no newline char in the description. furthermore 
> it runs fine with plain junit in parallel mode
> * original issue was reported here: 
> https://github.com/piotrturski/zohhak/issues/14
> * project that reproduces the issue: 
> https://github.com/christophpickl/zohhak_parallel_bug
> * working parallel junit tests without surefire: 
> https://github.com/piotrturski/zohhak/commit/806aafc8e09fd843753d2940991f3ca0edd5120d



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MPLUGIN-315) improve mojo description: show parameter name as

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPLUGIN-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681669#comment-15681669
 ] 

Hudson commented on MPLUGIN-315:


SUCCESS: Integrated in Jenkins build maven-plugin-tools Jigsaw #6 (See 
[https://builds.apache.org/job/maven-plugin-tools%20Jigsaw/6/])
[MPLUGIN-315] improve mojo description: show parameter name as  
(rfscholte: [http://svn.apache.org/viewvc/?view=rev=1770579])
* (edit) 
maven-plugin-tools-generators/src/main/java/org/apache/maven/tools/plugin/generator/PluginXdocGenerator.java
* (edit) maven-plugin-tools-generators/src/main/resources/pluginxdoc.properties
* (edit) 
maven-plugin-tools-generators/src/main/resources/pluginxdoc_fr.properties


> improve mojo description: show parameter name as 
> 
>
> Key: MPLUGIN-315
> URL: https://issues.apache.org/jira/browse/MPLUGIN-315
> Project: Maven Plugin Tools
>  Issue Type: Improvement
>  Components: Plugin Plugin
>Affects Versions: 3.5
>Reporter: Hervé Boutemy
>Assignee: Robert Scholte
> Fix For: 3.5.1
>
>
> since parameters are intended to be put in pom.xml, generating {{}} 
> will improve expressiveness of the documentation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MPLUGIN-315) improve mojo description: show parameter name as

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MPLUGIN-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte resolved MPLUGIN-315.

Resolution: Fixed
  Assignee: Robert Scholte

Fixed in [r1770579|http://svn.apache.org/viewvc?rev=1770579=rev]. 
[~hboutemy], summary looks good to me, details might have a bit too much 
white... thoughts?

> improve mojo description: show parameter name as 
> 
>
> Key: MPLUGIN-315
> URL: https://issues.apache.org/jira/browse/MPLUGIN-315
> Project: Maven Plugin Tools
>  Issue Type: Improvement
>  Components: Plugin Plugin
>Affects Versions: 3.5
>Reporter: Hervé Boutemy
>Assignee: Robert Scholte
> Fix For: 3.6
>
>
> since parameters are intended to be put in pom.xml, generating {{}} 
> will improve expressiveness of the documentation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-6084) Support JSR250 annotations

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681554#comment-15681554
 ] 

ASF GitHub Bot commented on MNG-6084:
-

Github user dantran commented on the issue:

https://github.com/apache/maven/pull/98
  
PR for maven-integration-testing  
https://github.com/apache/maven-integration-testing/pull/15


> Support JSR250 annotations
> --
>
> Key: MNG-6084
> URL: https://issues.apache.org/jira/browse/MNG-6084
> Project: Maven
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Dan Tran
>
> JSR330 ( @Named, @Singeton, etc) currently supported for plugin development.  
> Would like to see JSR250 as well(@PostConstruct, etc)
> Detail discussion is at  
> http://maven.40175.n5.nabble.com/Maven-Plugin-and-JSR330-td5879508.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-6084) Support JSR250 annotations

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681551#comment-15681551
 ] 

ASF GitHub Bot commented on MNG-6084:
-

GitHub user dantran opened a pull request:

https://github.com/apache/maven-integration-testing/pull/15

[MNG-6084] Add test for JSR250 support



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dantran/maven-integration-testing master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-integration-testing/pull/15.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15


commit 14fe9317814cb922e464b506e4cbf0bb9e0dcc34
Author: dantran 
Date:   2016-09-12T06:24:24Z

[MNG-6084] Add test for JSR250 support




> Support JSR250 annotations
> --
>
> Key: MNG-6084
> URL: https://issues.apache.org/jira/browse/MNG-6084
> Project: Maven
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Dan Tran
>
> JSR330 ( @Named, @Singeton, etc) currently supported for plugin development.  
> Would like to see JSR250 as well(@PostConstruct, etc)
> Detail discussion is at  
> http://maven.40175.n5.nabble.com/Maven-Plugin-and-JSR330-td5879508.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-6084) Support JSR250 annotations

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681543#comment-15681543
 ] 

ASF GitHub Bot commented on MNG-6084:
-

GitHub user dantran opened a pull request:

https://github.com/apache/maven/pull/98

[MNG-6084] Support JSR 250 @PreDestory and @PostContruct



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dantran/maven master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven/pull/98.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #98


commit 582ca6591ee9d2ed1de5ea58d10cba19cb8baf1d
Author: dantran 
Date:   2016-09-12T04:07:39Z

[MNG-6084] Support JSR 250 @PreDestory and @PostContruct




> Support JSR250 annotations
> --
>
> Key: MNG-6084
> URL: https://issues.apache.org/jira/browse/MNG-6084
> Project: Maven
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Dan Tran
>
> JSR330 ( @Named, @Singeton, etc) currently supported for plugin development.  
> Would like to see JSR250 as well(@PostConstruct, etc)
> Detail discussion is at  
> http://maven.40175.n5.nabble.com/Maven-Plugin-and-JSR330-td5879508.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-6084) Support JSR250 annotations

[Dan Tran (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681523#comment-15681523
 ] 

Dan Tran commented on MNG-6084:
---

JSR 250 integration tests are now working.  the commits are squashed at both 
maven and maven integration repo

> Support JSR250 annotations
> --
>
> Key: MNG-6084
> URL: https://issues.apache.org/jira/browse/MNG-6084
> Project: Maven
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 3.3.9
>Reporter: Dan Tran
>
> JSR330 ( @Named, @Singeton, etc) currently supported for plugin development.  
> Would like to see JSR250 as well(@PostConstruct, etc)
> Detail discussion is at  
> http://maven.40175.n5.nabble.com/Maven-Plugin-and-JSR330-td5879508.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MCHECKSTYLE-332) maven plugin not using cache property

[richard (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681518#comment-15681518
 ] 

richard commented on MCHECKSTYLE-332:
-

When is 2.18 due out? It looks like 2.17 was back in 2015-10-15.

> maven plugin not using cache property
> -
>
> Key: MCHECKSTYLE-332
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-332
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>  Components: checkstyle:checkstyle
>Affects Versions: 2.17
> Environment: Windows 7, 64 bit, JDK 8
>Reporter: richard
>Assignee: Guillaume Boué
> Fix For: 2.18
>
>
> When enabling cache in the pom for checkstyle via `cacheFile`, no cache file 
> is ever created after the run and multiple runs are not using any cache as 
> there is no speed up.
> POM: 
> https://github.com/checkstyle/checkstyle/blob/481406f2d5c07b8766757eb45bcc15fd1fa51bed/pom.xml#L453-L492
> I am specifying the cache after line 472 with the following:
> bq. ${project.build.directory}/cachefile-sevntu
> When I specify the cache directly into the configuration file, the cache file 
> is created, so this looks like an issue directly related to the maven plugin.
> I shouldn't need to specify it into the configuration since a property is 
> available in the POM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MCHECKSTYLE-329) Checkstyle plugin does not show the number of errors if the severity is configured to be 'warning'.

[JIRA]

[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681401#comment-15681401
 ] 

Guillaume Boué commented on MCHECKSTYLE-329:


I don't think there is an issue here. The number of violations is visible in 
the error message. With your configuration, on a sample project, the build 
fails with:

{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (default-cli) on 
project ...: You have 2 Checkstyle violations.
{noformat}

which gives the number of violations.

This number can be different than the number of Checkstyle errors shown in the 
logs at the end of the Checkstyle invocation, which looks like {{[INFO] There 
are 2 errors reported by Checkstyle 6.11.2 with ...}}. This log line shows how 
many checkstyle errors have been reported by Checkstyle, but there can be more 
violations if there are also checkstyle warnings and 
{{warning}} is set.

Put another way, with {{}}, you're 
telling Checkstyle to emit warnings instead of errors, so that log line will 
not appear.

> Checkstyle plugin does not show the number of errors if the severity is 
> configured to be 'warning'.
> ---
>
> Key: MCHECKSTYLE-329
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-329
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>Affects Versions: 2.17
>Reporter: Tran Hoang Chuong
>Priority: Minor
>
> I have configured the maven checkstyle module as follow:
> {noformat}
> 
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 2.17
> 
>   false
>   warning
>   
>   
>   
>   
>   
>   
>value="protected"/>
>value="true"/>
>value="Override, 
> Test, Before, BeforeClass, After, AfterClass"/>
>name="allowThrowsTagsForSubclasses" value="true"/>
>   
>   
>   
>   
>   
>value="true"/>
>   
>   
>   
>value="INTERFACE_DEF"/>
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
> 
> 
> {noformat}
> Executing mvn checkstyle:check does not give me the number of violations.
> However, it does give me the number if I comment out these 
> lines:{{warning}}
> {{}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MCHECKSTYLE-332) maven plugin not using cache property

[JIRA]

 [ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Boué closed MCHECKSTYLE-332.
--
   Resolution: Fixed
 Assignee: Guillaume Boué
Fix Version/s: 2.18

> maven plugin not using cache property
> -
>
> Key: MCHECKSTYLE-332
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-332
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>  Components: checkstyle:checkstyle
>Affects Versions: 2.17
> Environment: Windows 7, 64 bit, JDK 8
>Reporter: richard
>Assignee: Guillaume Boué
> Fix For: 2.18
>
>
> When enabling cache in the pom for checkstyle via `cacheFile`, no cache file 
> is ever created after the run and multiple runs are not using any cache as 
> there is no speed up.
> POM: 
> https://github.com/checkstyle/checkstyle/blob/481406f2d5c07b8766757eb45bcc15fd1fa51bed/pom.xml#L453-L492
> I am specifying the cache after line 472 with the following:
> bq. ${project.build.directory}/cachefile-sevntu
> When I specify the cache directly into the configuration file, the cache file 
> is created, so this looks like an issue directly related to the maven plugin.
> I shouldn't need to specify it into the configuration since a property is 
> available in the POM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MCHECKSTYLE-332) maven plugin not using cache property

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681307#comment-15681307
 ] 

Hudson commented on MCHECKSTYLE-332:


SUCCESS: Integrated in Jenkins build maven-plugins #7722 (See 
[https://builds.apache.org/job/maven-plugins/7722/])
[MCHECKSTYLE-332] maven plugin not using cache property

Starting with Checkstyle 6.16, the cache configuration was moved from the 
TreeWalker module to the Checker module, as per 
https://github.com/checkstyle/checkstyle/issues/569. To detect this change, we 
can rely on the presence of the public API method "setCacheFile(String)" in the 
Checker class. (gboue: [http://svn.apache.org/viewvc/?view=rev=1770564])
* (add) maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-checker
* (add) 
maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-checker/invoker.properties
* (add) maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-checker/pom.xml
* (add) maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-checker/src
* (add) maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-checker/src/main
* (add) 
maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-checker/src/main/java
* (add) 
maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-checker/src/main/java/org
* (add) 
maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-checker/src/main/java/org/MyClass.java
* (add) 
maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-checker/verify.groovy
* (add) maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-treewalker
* (add) 
maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-treewalker/invoker.properties
* (add) maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-treewalker/pom.xml
* (add) maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-treewalker/src
* (add) maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-treewalker/src/main
* (add) 
maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-treewalker/src/main/java
* (add) 
maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-treewalker/src/main/java/org
* (add) 
maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-treewalker/src/main/java/org/MyClass.java
* (add) 
maven-checkstyle-plugin/src/it/MCHECKSTYLE-332_cache-treewalker/verify.groovy
* (edit) 
maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle/exec/DefaultCheckstyleExecutor.java


> maven plugin not using cache property
> -
>
> Key: MCHECKSTYLE-332
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-332
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>  Components: checkstyle:checkstyle
>Affects Versions: 2.17
> Environment: Windows 7, 64 bit, JDK 8
>Reporter: richard
>
> When enabling cache in the pom for checkstyle via `cacheFile`, no cache file 
> is ever created after the run and multiple runs are not using any cache as 
> there is no speed up.
> POM: 
> https://github.com/checkstyle/checkstyle/blob/481406f2d5c07b8766757eb45bcc15fd1fa51bed/pom.xml#L453-L492
> I am specifying the cache after line 472 with the following:
> bq. ${project.build.directory}/cachefile-sevntu
> When I specify the cache directly into the configuration file, the cache file 
> is created, so this looks like an issue directly related to the maven plugin.
> I shouldn't need to specify it into the configuration since a property is 
> available in the POM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-6109) PluginDescriptor doesn't read since value of parameter

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681298#comment-15681298
 ] 

Hudson commented on MNG-6109:
-

FAILURE: Integrated in Jenkins build maven-plugin-tools Jigsaw #4 (See 
[https://builds.apache.org/job/maven-plugin-tools%20Jigsaw/4/])
[MPLUGIN-319] @since values ignored in report
Only use plugin.xml for M3.4.0 and above due to MNG-6109 (rfscholte: 
[http://svn.apache.org/viewvc/?view=rev=1770562])
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/invoker.properties
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/pom.xml
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java/org
* (add) 
maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java/org/MyMojo.java
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/verify.groovy
* (edit) maven-plugin-plugin/src/it/plugin-info-jdk/pom.xml
* (edit) 
maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/PluginReport.java


> PluginDescriptor doesn't read since value of parameter
> --
>
> Key: MNG-6109
> URL: https://issues.apache.org/jira/browse/MNG-6109
> Project: Maven
>  Issue Type: Bug
>  Components: Plugin API
>Affects Versions: 3.3.9
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: 3.4.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MPLUGIN-319) @since values ignored in report

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPLUGIN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681297#comment-15681297
 ] 

Hudson commented on MPLUGIN-319:


FAILURE: Integrated in Jenkins build maven-plugin-tools Jigsaw #4 (See 
[https://builds.apache.org/job/maven-plugin-tools%20Jigsaw/4/])
[MPLUGIN-319] @since values ignored in report
match IT folder with issue (rfscholte: 
[http://svn.apache.org/viewvc/?view=rev=1770563])
* (add) maven-plugin-plugin/src/it/mplugin-319_report-since
* (delete) maven-plugin-plugin/src/it/mplugin-329_report-since
[MPLUGIN-319] @since values ignored in report
Only use plugin.xml for M3.4.0 and above due to MNG-6109 (rfscholte: 
[http://svn.apache.org/viewvc/?view=rev=1770562])
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/invoker.properties
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/pom.xml
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java/org
* (add) 
maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java/org/MyMojo.java
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/verify.groovy
* (edit) maven-plugin-plugin/src/it/plugin-info-jdk/pom.xml
* (edit) 
maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/PluginReport.java


> @since values ignored in report
> ---
>
> Key: MPLUGIN-319
> URL: https://issues.apache.org/jira/browse/MPLUGIN-319
> Project: Maven Plugin Tools
>  Issue Type: Improvement
>  Components: Plugin Plugin
>Affects Versions: 3.5
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: 3.6
>
>
> MPLUGIN-310 triggered a bug in Maven (MNG-6109)
> This means that all version of Maven before 3.4.0 should not use the 
> {{plugin.xml}}, otherwise some important information will be missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MCHECKSTYLE-332) maven plugin not using cache property

[JIRA]

[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681295#comment-15681295
 ] 

Guillaume Boué commented on MCHECKSTYLE-332:


Fixed in [r1770564|http://svn.apache.org/viewvc?rev=1770564=rev].

> maven plugin not using cache property
> -
>
> Key: MCHECKSTYLE-332
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-332
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>  Components: checkstyle:checkstyle
>Affects Versions: 2.17
> Environment: Windows 7, 64 bit, JDK 8
>Reporter: richard
>
> When enabling cache in the pom for checkstyle via `cacheFile`, no cache file 
> is ever created after the run and multiple runs are not using any cache as 
> there is no speed up.
> POM: 
> https://github.com/checkstyle/checkstyle/blob/481406f2d5c07b8766757eb45bcc15fd1fa51bed/pom.xml#L453-L492
> I am specifying the cache after line 472 with the following:
> bq. ${project.build.directory}/cachefile-sevntu
> When I specify the cache directly into the configuration file, the cache file 
> is created, so this looks like an issue directly related to the maven plugin.
> I shouldn't need to specify it into the configuration since a property is 
> available in the POM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-6109) PluginDescriptor doesn't read since value of parameter

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681291#comment-15681291
 ] 

Hudson commented on MNG-6109:
-

SUCCESS: Integrated in Jenkins build maven-plugin-tools #272 (See 
[https://builds.apache.org/job/maven-plugin-tools/272/])
[MPLUGIN-319] @since values ignored in report
Only use plugin.xml for M3.4.0 and above due to MNG-6109 (rfscholte: 
[http://svn.apache.org/viewvc/?view=rev=1770562])
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/invoker.properties
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/pom.xml
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java/org
* (add) 
maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java/org/MyMojo.java
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/verify.groovy
* (edit) maven-plugin-plugin/src/it/plugin-info-jdk/pom.xml
* (edit) 
maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/PluginReport.java


> PluginDescriptor doesn't read since value of parameter
> --
>
> Key: MNG-6109
> URL: https://issues.apache.org/jira/browse/MNG-6109
> Project: Maven
>  Issue Type: Bug
>  Components: Plugin API
>Affects Versions: 3.3.9
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: 3.4.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MPLUGIN-319) @since values ignored in report

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPLUGIN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681290#comment-15681290
 ] 

Hudson commented on MPLUGIN-319:


SUCCESS: Integrated in Jenkins build maven-plugin-tools #272 (See 
[https://builds.apache.org/job/maven-plugin-tools/272/])
[MPLUGIN-319] @since values ignored in report
match IT folder with issue (rfscholte: 
[http://svn.apache.org/viewvc/?view=rev=1770563])
* (add) maven-plugin-plugin/src/it/mplugin-319_report-since
* (delete) maven-plugin-plugin/src/it/mplugin-329_report-since
[MPLUGIN-319] @since values ignored in report
Only use plugin.xml for M3.4.0 and above due to MNG-6109 (rfscholte: 
[http://svn.apache.org/viewvc/?view=rev=1770562])
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/invoker.properties
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/pom.xml
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java/org
* (add) 
maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java/org/MyMojo.java
* (add) maven-plugin-plugin/src/it/mplugin-329_report-since/verify.groovy
* (edit) maven-plugin-plugin/src/it/plugin-info-jdk/pom.xml
* (edit) 
maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/PluginReport.java


> @since values ignored in report
> ---
>
> Key: MPLUGIN-319
> URL: https://issues.apache.org/jira/browse/MPLUGIN-319
> Project: Maven Plugin Tools
>  Issue Type: Improvement
>  Components: Plugin Plugin
>Affects Versions: 3.5
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: 3.6
>
>
> MPLUGIN-310 triggered a bug in Maven (MNG-6109)
> This means that all version of Maven before 3.4.0 should not use the 
> {{plugin.xml}}, otherwise some important information will be missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (MPLUGIN-319) @since values ignored in report

[Robert Scholte (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MPLUGIN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MPLUGIN-319.
--
Resolution: Fixed

Fixed in [r1770562|http://svn.apache.org/viewvc?rev=1770562=rev]

> @since values ignored in report
> ---
>
> Key: MPLUGIN-319
> URL: https://issues.apache.org/jira/browse/MPLUGIN-319
> Project: Maven Plugin Tools
>  Issue Type: Improvement
>  Components: Plugin Plugin
>Affects Versions: 3.5
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: 3.6
>
>
> MPLUGIN-310 triggered a bug in Maven (MNG-6109)
> This means that all version of Maven before 3.4.0 should not use the 
> {{plugin.xml}}, otherwise some important information will be missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MCHECKSTYLE-332) maven plugin not using cache property

[richard (JIRA)]

[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681250#comment-15681250
 ] 

richard commented on MCHECKSTYLE-332:
-

It should be noted that in Checkstyle 8, we will be completely removing that 
property in TreeWalker.
https://github.com/checkstyle/checkstyle/issues/2883

> maven plugin not using cache property
> -
>
> Key: MCHECKSTYLE-332
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-332
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>  Components: checkstyle:checkstyle
>Affects Versions: 2.17
> Environment: Windows 7, 64 bit, JDK 8
>Reporter: richard
>
> When enabling cache in the pom for checkstyle via `cacheFile`, no cache file 
> is ever created after the run and multiple runs are not using any cache as 
> there is no speed up.
> POM: 
> https://github.com/checkstyle/checkstyle/blob/481406f2d5c07b8766757eb45bcc15fd1fa51bed/pom.xml#L453-L492
> I am specifying the cache after line 472 with the following:
> bq. ${project.build.directory}/cachefile-sevntu
> When I specify the cache directly into the configuration file, the cache file 
> is created, so this looks like an issue directly related to the maven plugin.
> I shouldn't need to specify it into the configuration since a property is 
> available in the POM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MPLUGIN-319) @since values ignored in report

[Robert Scholte (JIRA)]

Robert Scholte created MPLUGIN-319:
--

 Summary: @since values ignored in report
 Key: MPLUGIN-319
 URL: https://issues.apache.org/jira/browse/MPLUGIN-319
 Project: Maven Plugin Tools
  Issue Type: Improvement
  Components: Plugin Plugin
Affects Versions: 3.5
Reporter: Robert Scholte
Assignee: Robert Scholte
 Fix For: 3.6


MPLUGIN-310 triggered a bug in Maven (MNG-6109)
This means that all version of Maven before 3.4.0 should not use the 
{{plugin.xml}}, otherwise some important information will be missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MCHECKSTYLE-332) maven plugin not using cache property

[JIRA]

[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15681152#comment-15681152
 ] 

Guillaume Boué commented on MCHECKSTYLE-332:


I see, there was a change in Checkstyle 6.16, and the {{cacheFile}} property 
was moved to the {{Checker}} module. The plugin uses by default Checkstyle 
6.11.2 where the property is in the {{TreeWalker}} module 
([#569|https://github.com/checkstyle/checkstyle/issues/569]). This explains why 
the configuration is not taken into account. I'll look into that.

> maven plugin not using cache property
> -
>
> Key: MCHECKSTYLE-332
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-332
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>  Components: checkstyle:checkstyle
>Affects Versions: 2.17
> Environment: Windows 7, 64 bit, JDK 8
>Reporter: richard
>
> When enabling cache in the pom for checkstyle via `cacheFile`, no cache file 
> is ever created after the run and multiple runs are not using any cache as 
> there is no speed up.
> POM: 
> https://github.com/checkstyle/checkstyle/blob/481406f2d5c07b8766757eb45bcc15fd1fa51bed/pom.xml#L453-L492
> I am specifying the cache after line 472 with the following:
> bq. ${project.build.directory}/cachefile-sevntu
> When I specify the cache directly into the configuration file, the cache file 
> is created, so this looks like an issue directly related to the maven plugin.
> I shouldn't need to specify it into the configuration since a property is 
> available in the POM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)