Yah, I came to that conclusion too.. I went to open a bug report, and find https://github.com/mojohaus/license-maven-plugin/issues/10
I already did a few months back. :-) This plugin isn't marked as threadsafe, why is it being allowed? :-( On Wed, Nov 11, 2015 at 2:07 PM, Karl Heinz Marbaise <[email protected]> wrote: > Hi, > > > after taking a deeper look: > > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > 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) > > this looks like an thread issue... > > > Kind regards > Karl Heinz Marbaise > On 11/11/15 8:05 PM, Karl Heinz Marbaise wrote: >> >> Hi, >> >> Using Maven 3.3.9... >> >> mvn org.codehaus.mojo:license-maven-plugin:1.8:update-file-header >> >> ..... >> t-mojo/src/main/java/org/codehaus/mojo/license/MyBean3.java >> [INFO] - ignore file (detected %%Ignore-License) >> >> /Users/kama/ws-git-codehaus/license-maven-plugin/src/it/update-project-license-test-mojo/src/main/java/org/codehaus/license/plugin/test/MyBean3.java >> >> [INFO] - ignore file (detected %%Ignore-License) >> /Users/kama/ws-git-codehaus/license-maven-plugin/src/site/apt/header.apt >> [INFO] Scan 308 files header done in 380.314ms. >> [INFO] >> * update header on 65 files. >> * uptodate header on 147 files. >> * add header on 85 files. >> * ignore header on 11 files. >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD SUCCESS >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 1.582 s >> [INFO] Finished at: 2015-11-11T20:01:31+01:00 >> [INFO] Final Memory: 13M/293M >> [INFO] >> ------------------------------------------------------------------------ >> >> Tested also with Maven 3.3.3...no problems... >> >> Also checked with Java 1.7, Java 1.8 no problems... >> >> Hm...Can you post how you have called Maven? >> >> Which os you are running on? >> >> Is the project somewhere available ? Or better add the information to >> the issue you have opened on the license-maven-plugin project.... >> >> Kind regards >> Karl Heinz Marbaise >> >> On 11/11/15 7:45 PM, jieryn wrote: >>> >>> mvn-339 seems to be working for me for most cases except the codehaus >>> license maven plugin. In fact, all the mvn33x line seems to have this >>> issue. mvn325 is most recent version which works for me for this >>> plugin. >>> >>> non binding: +0 >>> >>> [INFO] --- license-maven-plugin:1.8:update-file-header (default-cli) @ >>> jar --- >>> ... >>> [ERROR] Failed to execute goal >>> org.codehaus.mojo:license-maven-plugin:1.8:update-file-header >>> (default-cli) on project service: could not execute goal >>> UpdateFileHeaderMojo for reason : null: NullPointerException -> [Help >>> 1] >>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to >>> execute goal >>> org.codehaus.mojo:license-maven-plugin:1.8:update-file-header >>> (default-cli) on project service: could not execute goal >>> UpdateFileHeaderMojo for reason : null >>> at >>> >>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) >>> >>> 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.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185) >>> >>> at >>> >>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:181) >>> >>> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >>> at >>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) >>> 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) >>> Caused by: org.apache.maven.plugin.MojoExecutionException: could not >>> execute goal UpdateFileHeaderMojo for reason : null >>> at >>> >>> org.codehaus.mojo.license.AbstractLicenseMojo.execute(AbstractLicenseMojo.java:219) >>> >>> at >>> >>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) >>> >>> at >>> >>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) >>> >>> ... 11 more >>> Caused by: java.lang.NullPointerException >>> at >>> >>> org.codehaus.mojo.license.header.FileHeaderProcessor.populateFilter(FileHeaderProcessor.java:129) >>> >>> at >>> >>> org.codehaus.mojo.license.AbstractFileHeaderMojo.processCommentStyle(AbstractFileHeaderMojo.java:796) >>> >>> at >>> >>> org.codehaus.mojo.license.AbstractFileHeaderMojo.doAction(AbstractFileHeaderMojo.java:581) >>> >>> at >>> >>> org.codehaus.mojo.license.AbstractLicenseMojo.execute(AbstractLicenseMojo.java:207) >>> >>> ... 13 more >>> >>> On Wed, Nov 11, 2015 at 1:14 PM, Karl Heinz Marbaise >>> <[email protected]> wrote: >>>> >>>> Hi, >>>> >>>> I have tested my own iterator-plugin, Modello Project (current master), >>>> mojohaus projects (properties-maven-plugin, exec-maven-plugin, >>>> appassembler, >>>> versions-maven-plugin,templating-maven-plugin), >>>> tested with current trunks of the following plugins: >>>> maven-resources-plugin, >>>> maven-ear-plugin, maven-compiler-plugin), other test projects >>>> >>>> without any issue. >>>> >>>> +1 from me... >>>> >>>> Furthermore i have updated the announcement mail with informations >>>> about the >>>> reporters of issues and code contributors..(I have attached it to this >>>> mail)..If someone has supplementals for this please write to me... >>>> >>>> Kind regards >>>> Karl Heinz Marbaise >>>> >>>> On 11/10/15 6:16 PM, Jason van Zyl wrote: >>>>> >>>>> >>>>> Hi, >>>>> >>>>> Time to release Maven 3.3.9! >>>>> >>>>> Here is a link to the issues resolved: >>>>> >>>>> >>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12333074 >>>>> >>>>> >>>>> Staging repo: >>>>> https://repository.apache.org/content/repositories/maven-1233/ >>>>> >>>>> The distributable binaries and sources for testing can be found here: >>>>> >>>>> >>>>> https://repository.apache.org/content/repositories/maven-1233/org/apache/maven/apache-maven/3.3.9/ >>>>> >>>>> >>>>> Specifically the zip, tarball, and source archives can be found here: >>>>> >>>>> >>>>> https://repository.apache.org/content/repositories/maven-1233/org/apache/maven/apache-maven/3.3.9/apache-maven-3.3.9-bin.zip >>>>> >>>>> >>>>> >>>>> https://repository.apache.org/content/repositories/maven-1233/org/apache/maven/apache-maven/3.3.9/apache-maven-3.3.9-bin.tar.gz >>>>> >>>>> >>>>> >>>>> https://repository.apache.org/content/repositories/maven-1233/org/apache/maven/apache-maven/3.3.9/apache-maven-3.3.9-src.zip >>>>> >>>>> >>>>> >>>>> https://repository.apache.org/content/repositories/maven-1233/org/apache/maven/apache-maven/3.3.9/apache-maven-3.3.9-src.tar.gz >>>>> >>>>> >>>>> Source release checksum(s): >>>>> apache-maven-3.3.9-src.zip sha1: >>>>> 2b783992afcba54255f46508d582fe656e2c37dc >>>>> >>>>> Staging site: >>>>> http://people.apache.org/~jvanzyl/maven-3.3.9/ >>>>> >>>>> Vote open for 72 hours. >>>>> >>>>> [ ] +1 >>>>> [ ] +0 >>>>> [ ] -1 >>>>> >>>>> Thanks, >>>>> >>>>> Jason >>>>> >>>>> ---------------------------------------------------------- >>>>> Jason van Zyl >>>>> Founder, Takari and Apache Maven >>>>> http://twitter.com/jvanzyl >>>>> http://twitter.com/takari_io > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
