Re: maven-build-tools notice and license files

2008-01-21 Thread Matthias Wessendorf
hrm... yeah, well. should we add this ? I think yes. Even it is ugly. -M On Jan 20, 2008 11:52 PM, Simon Kitching [EMAIL PROTECTED] wrote: Yep, notice-in-javadoc-jar needs to be fixed too. The apache commons parent pom does it like this: plugin !-- - Copy

Re: maven-build-tools notice and license files

2008-01-21 Thread Matthias Wessendorf
No luck with that can you give it a shot? -M On Jan 21, 2008 8:05 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote: hrm... yeah, well. should we add this ? I think yes. Even it is ugly. -M On Jan 20, 2008 11:52 PM, Simon Kitching [EMAIL PROTECTED] wrote: Yep,

maven-build-tools notice and license files

2008-01-20 Thread simon
Hi, I've noticed some peculiarities with the way that license and notice files are handled in the maven-build-tools/maven2-plugins project and its child modules. (1) For most child modules there are currently two copies of LICENSE and NOTICE checked in to svn. One is in the base directory of the

Re: maven-build-tools notice and license files

2008-01-20 Thread Matthias Wessendorf
ok, go ahead! -M On Jan 20, 2008 6:54 AM, simon [EMAIL PROTECTED] wrote: Hi, I've noticed some peculiarities with the way that license and notice files are handled in the maven-build-tools/maven2-plugins project and its child modules. (1) For most child modules there are currently two

Re: maven-build-tools notice and license files

2008-01-20 Thread simon
Ok, tried - but don't have commit permissions to this project it seems: svn: Commit failed (details follow): svn: MKACTIVITY of '/repos/asf/! svn/act/eefd0a04-73aa-4150-81d5-8d85f511742e': 403 Forbidden (http://svn.apache.org) svn: Your commit message was left in a temporary file: Odd, it looks

Re: maven-build-tools notice and license files

2008-01-20 Thread simon
On Sun, 2008-01-20 at 19:00 +0100, simon wrote: Ok, tried - but don't have commit permissions to this project it seems: Please forget that. I had checked this dir out using an http: url, not https. So of course could not commit. Done now. I have also updated the parent reference to the

Re: maven-build-tools notice and license files

2008-01-20 Thread simon
Matthias, Is the wagon plugin code originally from Oracle, ie needs the same NOTICE as the other plugins? Or is it originally ASF code? The first committer is bommel, the second is you... Thanks, Simon On Sun, 2008-01-20 at 08:54 -0800, Matthias Wessendorf wrote: ok, go ahead! -M On

Re: maven-build-tools notice and license files

2008-01-20 Thread Matthias Wessendorf
On Jan 20, 2008 10:47 AM, simon [EMAIL PROTECTED] wrote: Matthias, Is the wagon plugin code originally from Oracle, ie needs the same NOTICE as the other plugins? Or is it originally ASF code? Börnd did it for MyFaces switch to maven. -M The first committer is bommel, the second is you...

Re: maven-build-tools notice and license files

2008-01-20 Thread simon
On Sun, 2008-01-20 at 10:54 -0800, Matthias Wessendorf wrote: On Jan 20, 2008 10:47 AM, simon [EMAIL PROTECTED] wrote: Matthias, Is the wagon plugin code originally from Oracle, ie needs the same NOTICE as the other plugins? Or is it originally ASF code? Börnd did it for MyFaces

Re: maven-build-tools notice and license files

2008-01-20 Thread Matthias Wessendorf
Börnd did it for MyFaces switch to maven. And he works for Atanion, not Oracle. There were no code grants from he used to work for them. Atanion, so this must be normal ASF code. I'll add the normal NOTICE file then, not the Oracle-specific one. right, as I said, done for the maven-switch

Re: maven-build-tools notice and license files

2008-01-20 Thread Bernd Bohmann
The wagon plugin is ASF code and based on the maven-deploy-plugin. Regards Bernd simon schrieb: Matthias, Is the wagon plugin code originally from Oracle, ie needs the same NOTICE as the other plugins? Or is it originally ASF code? The first committer is bommel, the second is you...

Re: maven-build-tools notice and license files

2008-01-20 Thread Matthias Wessendorf
Simon, as I expected the release causes some issues. The blah-javadoc.jar files don't have the notice and license files included. We (when incubating trinidad) had had this issue in the past, and as a workaround, we used the apache-jar-resources-bundle. -Matthias On Jan 20, 2008 10:08 AM,

Re: maven-build-tools notice and license files

2008-01-20 Thread Simon Kitching
Yep, notice-in-javadoc-jar needs to be fixed too. The apache commons parent pom does it like this: plugin !-- - Copy LICENSE.txt and NOTICE.txt so that they are included - in the -javadoc jar file for the component. --