You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Niall Pemberton <ni...@gmail.com> on 2008/01/08 03:44:45 UTC
[VOTE] Release commons-parent 7
Hi,
In removing the remote-resources-plugin I ommitted to add back local
resource configuration for the NOTICE.tx and LICENSE.txt files.
Because of this I would like to do another release of commons-parent.
Apologies for this.
The changes since the the last release of version 6 in summary:
Changes to the pom.xml:
- Configure NOTICE.txt and LICENSE.txt resources
- Change the order of the mail archives
- specify the Cobertura plugin version
There are no changes to the site.xml
A full diff of the pom.xml can be found at this address:
http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=609839&r2=608470&diff_format=h
The version number in the pom will be updated automatically during the
release process.
[ ] +1
[ ] =0
[ ] -1
Vote is open for 72 hours
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Niall Pemberton <ni...@gmail.com>.
This vote has failed with only two votes. Also theres a few other
changes to go into the pom from the discussion(s) .
Niall
On Jan 8, 2008 2:44 AM, Niall Pemberton <ni...@gmail.com> wrote:
> Hi,
>
> In removing the remote-resources-plugin I ommitted to add back local
> resource configuration for the NOTICE.tx and LICENSE.txt files.
> Because of this I would like to do another release of commons-parent.
> Apologies for this.
>
> The changes since the the last release of version 6 in summary:
>
> Changes to the pom.xml:
> - Configure NOTICE.txt and LICENSE.txt resources
> - Change the order of the mail archives
> - specify the Cobertura plugin version
>
> There are no changes to the site.xml
>
> A full diff of the pom.xml can be found at this address:
> http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=609839&r2=608470&diff_format=h
>
> The version number in the pom will be updated automatically during the
> release process.
>
> [ ] +1
> [ ] =0
> [ ] -1
>
> Vote is open for 72 hours
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Dennis Lundberg <de...@apache.org>.
Niall Pemberton wrote:
> On Jan 8, 2008 7:55 PM, Dennis Lundberg <de...@apache.org> wrote:
>> Niall Pemberton wrote:
>>> On Jan 8, 2008 7:12 PM, Niall Pemberton <ni...@gmail.com> wrote:
>>>> On Jan 8, 2008 6:49 PM, Dennis Lundberg <de...@apache.org> wrote:
>>>>> Niall Pemberton wrote:
>>>>>> On Jan 8, 2008 4:19 PM, Jochen Wiedmann <jo...@gmail.com> wrote:
>>>>>>> On Jan 8, 2008 12:11 PM, Niall Pemberton <ni...@gmail.com> wrote:
>>>>>>>
>>>>>>>>> Sorry, if I am coming up with this question so late. Nevertheless:
>>>>>>>>> Does the current parent pom deal with adding NOTICE.txt and
>>>>>>>>> LICENSE.txt to the javadoc jar files?
>>>>>>>> No - but AIUI it doesn't need to since it only contains the generated
>>>>>>>> javadoc and not anything we develop.
>>>>>>> I'll be more than happy if we'll be able to get rid of that policy.
>>>>>>> Nevertheless it is what I was forced to do for releases of
>>>>>>> commons-fileupload and commons-io in the past. And, AFAIK, it is
>>>>>>> automatically enforced by the maven-remote-resources-plugin.
>>>>>> Actually remote resourcs doesn't.
>>>>> Actually it does. maven-remote-resources-plugin places the remotely
>>>>> fetched resources in a special directory. These resources are then
>>>>> included into the created jar file by maven-javadoc-plugin and
>>>>> maven-source-plugin.
>>>> Well I tried it and it didn't.
>>> Apologies - I just tried specifying the latest javadoc plugin version
>>> (2.3) and it worked. I'm just wondering why the javadoc jar plugin
>>> doesn't also do the "local" resources as well?
>> You normally don't want the javadoc-plugin to include your normal
>> resources, the ones that end up in target/classes during the build. You
>> can however tell the javadoc-plugin to use special javadoc resources if
>> you want to:
>>
>> http://maven.apache.org/plugins/maven-javadoc-plugin/examples/javadoc-resources.html
>
> I tried adding that to the javadoc plugin configuration
> <javadocDirectory>target/classes/META-INF</javadocDirectory>
>
> but it didn't work and looking at the copyJavadocResources() method in
> AbstractJavadocMojo (http://tinyurl.com/2ewwyz) it appears to pass an
> includes parameter of "**/doc-files" to Plexus's FileUtils
> getDirectoryNames() method (http://tinyurl.com/2cnokz) - so my reading
> is these files would need to be in a "doc-files" directory - is this
> correct or am I doing something wrong?
Reading the page I supplied a little more carefully I think that you a
right. It can't do what I thought it could, so you can't use that to
include license and notice files.
> Niall
>
>>> Niall
>>>
>>>> Niall
>>>>
>>>>>> Niall
>>>>>>
>>>>>>> Jochen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Niall Pemberton <ni...@gmail.com>.
On Jan 8, 2008 7:55 PM, Dennis Lundberg <de...@apache.org> wrote:
> Niall Pemberton wrote:
> > On Jan 8, 2008 7:12 PM, Niall Pemberton <ni...@gmail.com> wrote:
> >> On Jan 8, 2008 6:49 PM, Dennis Lundberg <de...@apache.org> wrote:
> >>> Niall Pemberton wrote:
> >>>> On Jan 8, 2008 4:19 PM, Jochen Wiedmann <jo...@gmail.com> wrote:
> >>>>> On Jan 8, 2008 12:11 PM, Niall Pemberton <ni...@gmail.com> wrote:
> >>>>>
> >>>>>>> Sorry, if I am coming up with this question so late. Nevertheless:
> >>>>>>> Does the current parent pom deal with adding NOTICE.txt and
> >>>>>>> LICENSE.txt to the javadoc jar files?
> >>>>>> No - but AIUI it doesn't need to since it only contains the generated
> >>>>>> javadoc and not anything we develop.
> >>>>> I'll be more than happy if we'll be able to get rid of that policy.
> >>>>> Nevertheless it is what I was forced to do for releases of
> >>>>> commons-fileupload and commons-io in the past. And, AFAIK, it is
> >>>>> automatically enforced by the maven-remote-resources-plugin.
> >>>> Actually remote resourcs doesn't.
> >>> Actually it does. maven-remote-resources-plugin places the remotely
> >>> fetched resources in a special directory. These resources are then
> >>> included into the created jar file by maven-javadoc-plugin and
> >>> maven-source-plugin.
> >> Well I tried it and it didn't.
> >
> > Apologies - I just tried specifying the latest javadoc plugin version
> > (2.3) and it worked. I'm just wondering why the javadoc jar plugin
> > doesn't also do the "local" resources as well?
>
> You normally don't want the javadoc-plugin to include your normal
> resources, the ones that end up in target/classes during the build. You
> can however tell the javadoc-plugin to use special javadoc resources if
> you want to:
>
> http://maven.apache.org/plugins/maven-javadoc-plugin/examples/javadoc-resources.html
I tried adding that to the javadoc plugin configuration
<javadocDirectory>target/classes/META-INF</javadocDirectory>
but it didn't work and looking at the copyJavadocResources() method in
AbstractJavadocMojo (http://tinyurl.com/2ewwyz) it appears to pass an
includes parameter of "**/doc-files" to Plexus's FileUtils
getDirectoryNames() method (http://tinyurl.com/2cnokz) - so my reading
is these files would need to be in a "doc-files" directory - is this
correct or am I doing something wrong?
Niall
> > Niall
> >
> >> Niall
> >>
> >>>> Niall
> >>>>
> >>>>> Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Dennis Lundberg <de...@apache.org>.
Niall Pemberton wrote:
> On Jan 8, 2008 7:12 PM, Niall Pemberton <ni...@gmail.com> wrote:
>> On Jan 8, 2008 6:49 PM, Dennis Lundberg <de...@apache.org> wrote:
>>> Niall Pemberton wrote:
>>>> On Jan 8, 2008 4:19 PM, Jochen Wiedmann <jo...@gmail.com> wrote:
>>>>> On Jan 8, 2008 12:11 PM, Niall Pemberton <ni...@gmail.com> wrote:
>>>>>
>>>>>>> Sorry, if I am coming up with this question so late. Nevertheless:
>>>>>>> Does the current parent pom deal with adding NOTICE.txt and
>>>>>>> LICENSE.txt to the javadoc jar files?
>>>>>> No - but AIUI it doesn't need to since it only contains the generated
>>>>>> javadoc and not anything we develop.
>>>>> I'll be more than happy if we'll be able to get rid of that policy.
>>>>> Nevertheless it is what I was forced to do for releases of
>>>>> commons-fileupload and commons-io in the past. And, AFAIK, it is
>>>>> automatically enforced by the maven-remote-resources-plugin.
>>>> Actually remote resourcs doesn't.
>>> Actually it does. maven-remote-resources-plugin places the remotely
>>> fetched resources in a special directory. These resources are then
>>> included into the created jar file by maven-javadoc-plugin and
>>> maven-source-plugin.
>> Well I tried it and it didn't.
>
> Apologies - I just tried specifying the latest javadoc plugin version
> (2.3) and it worked. I'm just wondering why the javadoc jar plugin
> doesn't also do the "local" resources as well?
You normally don't want the javadoc-plugin to include your normal
resources, the ones that end up in target/classes during the build. You
can however tell the javadoc-plugin to use special javadoc resources if
you want to:
http://maven.apache.org/plugins/maven-javadoc-plugin/examples/javadoc-resources.html
> Niall
>
>> Niall
>>
>>>> Niall
>>>>
>>>>> Jochen
>>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Niall Pemberton <ni...@gmail.com>.
On Jan 8, 2008 7:12 PM, Niall Pemberton <ni...@gmail.com> wrote:
> On Jan 8, 2008 6:49 PM, Dennis Lundberg <de...@apache.org> wrote:
> > Niall Pemberton wrote:
> > > On Jan 8, 2008 4:19 PM, Jochen Wiedmann <jo...@gmail.com> wrote:
> > >> On Jan 8, 2008 12:11 PM, Niall Pemberton <ni...@gmail.com> wrote:
> > >>
> > >>>> Sorry, if I am coming up with this question so late. Nevertheless:
> > >>>> Does the current parent pom deal with adding NOTICE.txt and
> > >>>> LICENSE.txt to the javadoc jar files?
> > >>> No - but AIUI it doesn't need to since it only contains the generated
> > >>> javadoc and not anything we develop.
> > >> I'll be more than happy if we'll be able to get rid of that policy.
> > >> Nevertheless it is what I was forced to do for releases of
> > >> commons-fileupload and commons-io in the past. And, AFAIK, it is
> > >> automatically enforced by the maven-remote-resources-plugin.
> > >
> > > Actually remote resourcs doesn't.
> >
> > Actually it does. maven-remote-resources-plugin places the remotely
> > fetched resources in a special directory. These resources are then
> > included into the created jar file by maven-javadoc-plugin and
> > maven-source-plugin.
>
> Well I tried it and it didn't.
Apologies - I just tried specifying the latest javadoc plugin version
(2.3) and it worked. I'm just wondering why the javadoc jar plugin
doesn't also do the "local" resources as well?
Niall
> Niall
>
> > > Niall
> > >
> > >> Jochen
> > >>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Niall Pemberton <ni...@gmail.com>.
On Jan 8, 2008 6:49 PM, Dennis Lundberg <de...@apache.org> wrote:
> Niall Pemberton wrote:
> > On Jan 8, 2008 4:19 PM, Jochen Wiedmann <jo...@gmail.com> wrote:
> >> On Jan 8, 2008 12:11 PM, Niall Pemberton <ni...@gmail.com> wrote:
> >>
> >>>> Sorry, if I am coming up with this question so late. Nevertheless:
> >>>> Does the current parent pom deal with adding NOTICE.txt and
> >>>> LICENSE.txt to the javadoc jar files?
> >>> No - but AIUI it doesn't need to since it only contains the generated
> >>> javadoc and not anything we develop.
> >> I'll be more than happy if we'll be able to get rid of that policy.
> >> Nevertheless it is what I was forced to do for releases of
> >> commons-fileupload and commons-io in the past. And, AFAIK, it is
> >> automatically enforced by the maven-remote-resources-plugin.
> >
> > Actually remote resourcs doesn't.
>
> Actually it does. maven-remote-resources-plugin places the remotely
> fetched resources in a special directory. These resources are then
> included into the created jar file by maven-javadoc-plugin and
> maven-source-plugin.
Well I tried it and it didn't.
Niall
> > Niall
> >
> >> Jochen
> >>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Dennis Lundberg <de...@apache.org>.
Niall Pemberton wrote:
> On Jan 8, 2008 4:19 PM, Jochen Wiedmann <jo...@gmail.com> wrote:
>> On Jan 8, 2008 12:11 PM, Niall Pemberton <ni...@gmail.com> wrote:
>>
>>>> Sorry, if I am coming up with this question so late. Nevertheless:
>>>> Does the current parent pom deal with adding NOTICE.txt and
>>>> LICENSE.txt to the javadoc jar files?
>>> No - but AIUI it doesn't need to since it only contains the generated
>>> javadoc and not anything we develop.
>> I'll be more than happy if we'll be able to get rid of that policy.
>> Nevertheless it is what I was forced to do for releases of
>> commons-fileupload and commons-io in the past. And, AFAIK, it is
>> automatically enforced by the maven-remote-resources-plugin.
>
> Actually remote resourcs doesn't.
Actually it does. maven-remote-resources-plugin places the remotely
fetched resources in a special directory. These resources are then
included into the created jar file by maven-javadoc-plugin and
maven-source-plugin.
> Niall
>
>> Jochen
>>
>> --
>> Look, that's why there's rules, understand? So that you think before
>> you break 'em.
>>
>> -- (Terry Pratchett, Thief of Time)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Niall Pemberton <ni...@gmail.com>.
On Jan 8, 2008 4:19 PM, Jochen Wiedmann <jo...@gmail.com> wrote:
> On Jan 8, 2008 12:11 PM, Niall Pemberton <ni...@gmail.com> wrote:
>
> > > Sorry, if I am coming up with this question so late. Nevertheless:
> > > Does the current parent pom deal with adding NOTICE.txt and
> > > LICENSE.txt to the javadoc jar files?
> >
> > No - but AIUI it doesn't need to since it only contains the generated
> > javadoc and not anything we develop.
>
> I'll be more than happy if we'll be able to get rid of that policy.
> Nevertheless it is what I was forced to do for releases of
> commons-fileupload and commons-io in the past. And, AFAIK, it is
> automatically enforced by the maven-remote-resources-plugin.
Actually remote resourcs doesn't.
Niall
> Jochen
>
> --
> Look, that's why there's rules, understand? So that you think before
> you break 'em.
>
> -- (Terry Pratchett, Thief of Time)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Jan 8, 2008 12:11 PM, Niall Pemberton <ni...@gmail.com> wrote:
> > Sorry, if I am coming up with this question so late. Nevertheless:
> > Does the current parent pom deal with adding NOTICE.txt and
> > LICENSE.txt to the javadoc jar files?
>
> No - but AIUI it doesn't need to since it only contains the generated
> javadoc and not anything we develop.
I'll be more than happy if we'll be able to get rid of that policy.
Nevertheless it is what I was forced to do for releases of
commons-fileupload and commons-io in the past. And, AFAIK, it is
automatically enforced by the maven-remote-resources-plugin.
Jochen
--
Look, that's why there's rules, understand? So that you think before
you break 'em.
-- (Terry Pratchett, Thief of Time)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Niall Pemberton <ni...@gmail.com>.
On Jan 8, 2008 4:32 PM, Niall Pemberton <ni...@gmail.com> wrote:
> On Jan 8, 2008 4:11 PM, Henri Yandell <fl...@gmail.com> wrote:
> > On Jan 8, 2008 3:11 AM, Niall Pemberton <ni...@gmail.com> wrote:
> > > On Jan 8, 2008 10:50 AM, Jochen Wiedmann <jo...@gmail.com> wrote:
> > > > On Jan 8, 2008 3:44 AM, Niall Pemberton <ni...@gmail.com> wrote:
> > > >
> > > > > In removing the remote-resources-plugin I ommitted to add back local
> > > > > resource configuration for the NOTICE.tx and LICENSE.txt files.
> > > > > Because of this I would like to do another release of commons-parent.
> > > > > Apologies for this.
> > > >
> > > > +1, because I agree that this must be fixed ASAP.
> > > >
> > > >
> > > > Sorry, if I am coming up with this question so late. Nevertheless:
> > > > Does the current parent pom deal with adding NOTICE.txt and
> > > > LICENSE.txt to the javadoc jar files?
> > >
> > > No - but AIUI it doesn't need to since it only contains the generated
> > > javadoc and not anything we develop.
> >
> > Javadoc is full of copyright - that's why it's the part of spec jars
>
> Yes and we have our copyright notice on every page.
>
> > we can't replicate. Just because it's a secondary artifact doesn't
> > change that - so I bet we should have the files in the javadoc jars.
>
> Well it just seems like rule-making gone mad and I bet if you went
> looking thru' all the m2 generated javadoc jars in the ASF distro dirs
> then none would have it.
I posted this on legal-discuss here:
http://apache.markmail.org/message/cnmhhqpk5o6hlv7e
Niall
> Niall
>
> > Hen
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Niall Pemberton <ni...@gmail.com>.
On Jan 8, 2008 4:11 PM, Henri Yandell <fl...@gmail.com> wrote:
> On Jan 8, 2008 3:11 AM, Niall Pemberton <ni...@gmail.com> wrote:
> > On Jan 8, 2008 10:50 AM, Jochen Wiedmann <jo...@gmail.com> wrote:
> > > On Jan 8, 2008 3:44 AM, Niall Pemberton <ni...@gmail.com> wrote:
> > >
> > > > In removing the remote-resources-plugin I ommitted to add back local
> > > > resource configuration for the NOTICE.tx and LICENSE.txt files.
> > > > Because of this I would like to do another release of commons-parent.
> > > > Apologies for this.
> > >
> > > +1, because I agree that this must be fixed ASAP.
> > >
> > >
> > > Sorry, if I am coming up with this question so late. Nevertheless:
> > > Does the current parent pom deal with adding NOTICE.txt and
> > > LICENSE.txt to the javadoc jar files?
> >
> > No - but AIUI it doesn't need to since it only contains the generated
> > javadoc and not anything we develop.
>
> Javadoc is full of copyright - that's why it's the part of spec jars
Yes and we have our copyright notice on every page.
> we can't replicate. Just because it's a secondary artifact doesn't
> change that - so I bet we should have the files in the javadoc jars.
Well it just seems like rule-making gone mad and I bet if you went
looking thru' all the m2 generated javadoc jars in the ASF distro dirs
then none would have it.
Niall
> Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Henri Yandell <fl...@gmail.com>.
On Jan 8, 2008 3:11 AM, Niall Pemberton <ni...@gmail.com> wrote:
> On Jan 8, 2008 10:50 AM, Jochen Wiedmann <jo...@gmail.com> wrote:
> > On Jan 8, 2008 3:44 AM, Niall Pemberton <ni...@gmail.com> wrote:
> >
> > > In removing the remote-resources-plugin I ommitted to add back local
> > > resource configuration for the NOTICE.tx and LICENSE.txt files.
> > > Because of this I would like to do another release of commons-parent.
> > > Apologies for this.
> >
> > +1, because I agree that this must be fixed ASAP.
> >
> >
> > Sorry, if I am coming up with this question so late. Nevertheless:
> > Does the current parent pom deal with adding NOTICE.txt and
> > LICENSE.txt to the javadoc jar files?
>
> No - but AIUI it doesn't need to since it only contains the generated
> javadoc and not anything we develop.
Javadoc is full of copyright - that's why it's the part of spec jars
we can't replicate. Just because it's a secondary artifact doesn't
change that - so I bet we should have the files in the javadoc jars.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Niall Pemberton <ni...@gmail.com>.
On Jan 8, 2008 10:50 AM, Jochen Wiedmann <jo...@gmail.com> wrote:
> On Jan 8, 2008 3:44 AM, Niall Pemberton <ni...@gmail.com> wrote:
>
> > In removing the remote-resources-plugin I ommitted to add back local
> > resource configuration for the NOTICE.tx and LICENSE.txt files.
> > Because of this I would like to do another release of commons-parent.
> > Apologies for this.
>
> +1, because I agree that this must be fixed ASAP.
>
>
> Sorry, if I am coming up with this question so late. Nevertheless:
> Does the current parent pom deal with adding NOTICE.txt and
> LICENSE.txt to the javadoc jar files?
No - but AIUI it doesn't need to since it only contains the generated
javadoc and not anything we develop.
Niall
> Jochen
>
>
>
> --
> Look, that's why there's rules, understand? So that you think before
> you break 'em.
>
> -- (Terry Pratchett, Thief of Time)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 7
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Jan 8, 2008 3:44 AM, Niall Pemberton <ni...@gmail.com> wrote:
> In removing the remote-resources-plugin I ommitted to add back local
> resource configuration for the NOTICE.tx and LICENSE.txt files.
> Because of this I would like to do another release of commons-parent.
> Apologies for this.
+1, because I agree that this must be fixed ASAP.
Sorry, if I am coming up with this question so late. Nevertheless:
Does the current parent pom deal with adding NOTICE.txt and
LICENSE.txt to the javadoc jar files?
Jochen
--
Look, that's why there's rules, understand? So that you think before
you break 'em.
-- (Terry Pratchett, Thief of Time)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org