Re: maven-license-plugin: what does 'license-list' actually produce?
On Wed, May 6, 2020 at 7:10 PM Greg Chabala wrote: > Ah, like what you get from the standard dependency report? E.g. > > https://maven.apache.org/plugins/maven-dependency-plugin/dependencies.html#Licenses Yes! Thx, that's exactly what I was looking for. Alain
Re: maven-license-plugin: what does 'license-list' actually produce?
Ah, like what you get from the standard dependency report? E.g. https://maven.apache.org/plugins/maven-dependency-plugin/dependencies.html#Licenses On Wed, May 6, 2020 at 5:55 PM Alain Désilets wrote: > On Wed, May 6, 2020 at 6:48 PM Greg Chabala > wrote: > > > Ah, I see. I believe it's closer to (A), but I would describe it as 'the > > list of licenses that the plugin knows to exist in the universe'. > > > > Really? Not terribly useful. I can probably accurate version of that info > from wikipedia. > > > > > > I believe (B) would be the license:third-party-report goal: > > > https://www.mojohaus.org/license-maven-plugin/third-party-report-mojo.html > > > Yeah, I ran that. But it basically gives me a long list of third-party > modules with their licenses. What I would like to see is a consolidated > "bag" of all the licenses that my project depends on. Of course, I can > manually generate that bag by consolidating the third-party-report output, > but it would be nice to have an automated way to get that. > > Alain >
Re: maven-license-plugin: what does 'license-list' actually produce?
On Wed, May 6, 2020 at 6:48 PM Greg Chabala wrote: > Ah, I see. I believe it's closer to (A), but I would describe it as 'the > list of licenses that the plugin knows to exist in the universe'. > Really? Not terribly useful. I can probably accurate version of that info from wikipedia. > > I believe (B) would be the license:third-party-report goal: > https://www.mojohaus.org/license-maven-plugin/third-party-report-mojo.html Yeah, I ran that. But it basically gives me a long list of third-party modules with their licenses. What I would like to see is a consolidated "bag" of all the licenses that my project depends on. Of course, I can manually generate that bag by consolidating the third-party-report output, but it would be nice to have an automated way to get that. Alain
Re: maven-license-plugin: what does 'license-list' actually produce?
Ah, I see. I believe it's closer to (A), but I would describe it as 'the list of licenses that the plugin knows to exist in the universe'. I believe (B) would be the license:third-party-report goal: https://www.mojohaus.org/license-maven-plugin/third-party-report-mojo.html On Wed, May 6, 2020 at 5:34 PM Alain Désilets wrote: > On Wed, May 6, 2020, 4:16 PM Greg Chabala wrote: > > > The documentation has an example of the output: > > > > > https://www.mojohaus.org/license-maven-plugin/examples/example-license-list.html > > > Yes I saw that. I just don't know how to interpret that list. Is it > > (A) the list of all licenses under which I coul distribute the projet >Or > (B) the union of all the licenses of a dependancy that the project depends > on > > > > > > > On Wed, May 6, 2020 at 3:03 PM Alain Désilets > > wrote: > > > > > The output of the license-list goal and the plugin documentation say > that > > > this is a list of 'availalble licenses'. > > > > > > I am not sure what 'available' means in this context. I *believe* it > > means > > > those are the various licenses under which I could distribute the > > project. > > > But I am not sure. Can someone confirm that my understanding is > correct? > > > > > > Thx. > > > > > > Alain Désilets > > > > > >
Re: maven-license-plugin: what does 'license-list' actually produce?
On Wed, May 6, 2020, 4:16 PM Greg Chabala wrote: > The documentation has an example of the output: > > https://www.mojohaus.org/license-maven-plugin/examples/example-license-list.html Yes I saw that. I just don't know how to interpret that list. Is it (A) the list of all licenses under which I coul distribute the projet Or (B) the union of all the licenses of a dependancy that the project depends on > > > On Wed, May 6, 2020 at 3:03 PM Alain Désilets > wrote: > > > The output of the license-list goal and the plugin documentation say that > > this is a list of 'availalble licenses'. > > > > I am not sure what 'available' means in this context. I *believe* it > means > > those are the various licenses under which I could distribute the > project. > > But I am not sure. Can someone confirm that my understanding is correct? > > > > Thx. > > > > Alain Désilets > > >
Re: maven-license-plugin: what does 'license-list' actually produce?
The documentation has an example of the output: https://www.mojohaus.org/license-maven-plugin/examples/example-license-list.html On Wed, May 6, 2020 at 3:03 PM Alain Désilets wrote: > The output of the license-list goal and the plugin documentation say that > this is a list of 'availalble licenses'. > > I am not sure what 'available' means in this context. I *believe* it means > those are the various licenses under which I could distribute the project. > But I am not sure. Can someone confirm that my understanding is correct? > > Thx. > > Alain Désilets >
maven-license-plugin: what does 'license-list' actually produce?
The output of the license-list goal and the plugin documentation say that this is a list of 'availalble licenses'. I am not sure what 'available' means in this context. I *believe* it means those are the various licenses under which I could distribute the project. But I am not sure. Can someone confirm that my understanding is correct? Thx. Alain Désilets
Maven License Plugin question
Hi all!
I have problems understanding the purpose of an attribute of
license:update-project-license goal.
About the generateBundle attribute the docs say:
"A flag to copy the main license file in a bundled place. This is usefull
for final application to have a none confusing location to seek for the
application license. If Sets to true, will copy the license file to the
bundleLicensePath to outputDirectory. *Note:* This option is not available
for pom module types."
I understand, that by default this will copy the full license file to
META-INF/${project.artifactId}-LICENSE.txt
which would otherwise be copied to the root of the jar.
What I don't understand is the explanation of the cases in which this is
benificial.
Is the "bundle" in generateBundle the "bundle" from OSGi, so this attribute
something connected with generating OSGi bundles?
I would appreciate if someone could provide an explaining paraphrasis of "
This is usefull for final application to have a none confusing location to
seek for the application license.".
Markward
Re: maven-license-plugin NPE
On 11 April 2013 11:36, Olivier Lamy wrote: > This mojo is maintained here > http://code.google.com/p/maven-license-plugin/ > So use this place for any questions. > While you are over there can you also point out that they are not supposed to call themselves maven-___-plugin as that causes confusion on behalf of users (and is not a naming format that we consider part of the allowed usage) they should use a format that makes it clear that it is a plugin for Apache Maven but by somebody other than the ASF, e.g. -maven-plugin would be fine See http://jira.codehaus.org/browse/MPLUGIN-185 > Maybe you can try this one too > http://mojo.codehaus.org/license-maven-plugin/ > > 2013/4/11 David Hoffer : > > I have a multi-module build I'm running the license:format goal on. It > > works fine for several modules then fails with NPE on the > deployment-parent > > module which is a pom type module (we have several like that), any ideas > > why it would fail on this one? > > > > I tried versions 1.9.0 and 1.10.b1 and get the same error. > > > > [ERROR] Failed to execute goal > > com.mycila.maven-license-plugin:maven-license-plu > > gin:1.10.b1:format (default-cli) on project deployment-parent: Execution > > default > > -cli of goal > > com.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format > > failed. NullPointerException -> [Help 1] > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > > goal c > > om.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format > > (default-cli) > > on project deployment-parent: Execution default-cli of goal > > com.mycila.maven-li > > cense-plugin:maven-license-plugin:1.10.b1:format failed. > > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor > > .java:225) > > 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.buildProje > > ct(LifecycleModuleBuilder.java:84) > > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje > > ct(LifecycleModuleBuilder.java:59) > > at > > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu > > ild(LifecycleStarter.java:183) > > at > > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl > > eStarter.java:161) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > > java:57) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > > sorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:601) > > at > > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun > > cher.java:290) > > at > > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav > > a:230) > > at > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La > > uncher.java:409) > > at > > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java: > > 352) > > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > > default-c > > li of goal > > com.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format f > > ailed. > > at > > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default > > BuildPluginManager.java:110) > > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor > > .java:209) > > ... 19 more > > Caused by: java.lang.NullPointerException > > at > > com.google.code.mojo.license.header.HeaderParser.hasHeader(HeaderPars > > er.java:142) > > at > > com.google.code.mojo.license.header.HeaderParser.(HeaderParser. > > java:63) > > at > > com.google.code.mojo.license.document.Document.parseHeader(Document.j > > ava:125) >
Re: maven-license-plugin NPE
This mojo is maintained here http://code.google.com/p/maven-license-plugin/ So use this place for any questions. Maybe you can try this one too http://mojo.codehaus.org/license-maven-plugin/ 2013/4/11 David Hoffer : > I have a multi-module build I'm running the license:format goal on. It > works fine for several modules then fails with NPE on the deployment-parent > module which is a pom type module (we have several like that), any ideas > why it would fail on this one? > > I tried versions 1.9.0 and 1.10.b1 and get the same error. > > [ERROR] Failed to execute goal > com.mycila.maven-license-plugin:maven-license-plu > gin:1.10.b1:format (default-cli) on project deployment-parent: Execution > default > -cli of goal > com.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format > failed. NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal c > om.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format > (default-cli) > on project deployment-parent: Execution default-cli of goal > com.mycila.maven-li > cense-plugin:maven-license-plugin:1.10.b1:format failed. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor > .java:225) > 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.buildProje > ct(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje > ct(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu > ild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl > eStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun > cher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav > a:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La > uncher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java: > 352) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-c > li of goal > com.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format f > ailed. > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default > BuildPluginManager.java:110) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor > .java:209) > ... 19 more > Caused by: java.lang.NullPointerException > at > com.google.code.mojo.license.header.HeaderParser.hasHeader(HeaderPars > er.java:142) > at > com.google.code.mojo.license.header.HeaderParser.(HeaderParser. > java:63) > at > com.google.code.mojo.license.document.Document.parseHeader(Document.j > ava:125) > at > com.google.code.mojo.license.LicenseFormatMojo$1.onHeaderNotFound(Lic > enseFormatMojo.java:55) > at > com.google.code.mojo.license.AbstractLicenseMojo$1.run(AbstractLicens > eMojo.java:265) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:47 > 1) > at > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:47 > 1) > at > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. > java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor > .java:615) > at java.lang.Thread.run(Thread.java:722) -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-license-plugin NPE
I have a multi-module build I'm running the license:format goal on. It works fine for several modules then fails with NPE on the deployment-parent module which is a pom type module (we have several like that), any ideas why it would fail on this one? I tried versions 1.9.0 and 1.10.b1 and get the same error. [ERROR] Failed to execute goal com.mycila.maven-license-plugin:maven-license-plu gin:1.10.b1:format (default-cli) on project deployment-parent: Execution default -cli of goal com.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format failed. NullPointerException -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal c om.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format (default-cli) on project deployment-parent: Execution default-cli of goal com.mycila.maven-li cense-plugin:maven-license-plugin:1.10.b1:format failed. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor .java:225) 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.buildProje ct(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje ct(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu ild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl eStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun cher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav a:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La uncher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java: 352) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-c li of goal com.mycila.maven-license-plugin:maven-license-plugin:1.10.b1:format f ailed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default BuildPluginManager.java:110) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor .java:209) ... 19 more Caused by: java.lang.NullPointerException at com.google.code.mojo.license.header.HeaderParser.hasHeader(HeaderPars er.java:142) at com.google.code.mojo.license.header.HeaderParser.(HeaderParser. java:63) at com.google.code.mojo.license.document.Document.parseHeader(Document.j ava:125) at com.google.code.mojo.license.LicenseFormatMojo$1.onHeaderNotFound(Lic enseFormatMojo.java:55) at com.google.code.mojo.license.AbstractLicenseMojo$1.run(AbstractLicens eMojo.java:265) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:47 1) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:47 1) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:615) at java.lang.Thread.run(Thread.java:722)
maven-license-plugin
Does anyone know about the maven-license-plugin? http://www.theserverside.com/news/thread.tss?thread_id=48526 http://code.google.com/p/maven-license-plugin/ It looks interesting, but I haven't tried it yet. Is there any movement to move it to codehaus? -Josh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
