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
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
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
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
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
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
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
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
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 dhoff...@gmail.com:
I have a multi-module build I'm running the license:format
On 11 April 2013 11:36, Olivier Lamy ol...@apache.org 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
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
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
12 matches
Mail list logo
