You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Matt Benson <gu...@yahoo.com> on 2008/07/29 00:54:52 UTC

[all] release preparation

Is a `mvn site` from  a src distribution supposed to
generate download_[component].cgi?  If not, are we
intended to make sure we preserve the existing file or
re-create it when deploying the site?  This is
confusing to me.

Thanks,
Matt


      

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [all] release preparation

Posted by Rahul Akolkar <ra...@gmail.com>.
On Tue, Jul 29, 2008 at 2:38 PM, Matt Benson <gu...@yahoo.com> wrote:
>
> --- Niall Pemberton <ni...@gmail.com> wrote:
>
>> On Tue, Jul 29, 2008 at 5:33 PM, Matt Benson
>> <gu...@yahoo.com> wrote:
>> >
>> > --- Niall Pemberton <ni...@gmail.com>
>> wrote:
>> >
>> >> On Tue, Jul 29, 2008 at 3:47 PM, Matt Benson
>> >> <gu...@yahoo.com> wrote:
>> >> >
>> >> > --- Rahul Akolkar <ra...@gmail.com>
>> wrote:
>> >> >
>> >> >> On Mon, Jul 28, 2008 at 6:54 PM, Matt Benson
>> >> >> <gu...@yahoo.com> wrote:
>> >> >> > Is a `mvn site` from  a src distribution
>> >> supposed
>> >> >> to
>> >> >> > generate download_[component].cgi?
>> >> >> <snip/>
>> >> >>
>> >> >> No.
>> >> >>
>> >> >>
>> >> >> >  If not, are we
>> >> >> > intended to make sure we preserve the
>> existing
>> >> >> file or
>> >> >> > re-create it when deploying the site?
>> >> >> <snap/>
>> >> >>
>> >> >> Don't need to do anything special for it (its
>> >> >> preserved by default).
>> >> >>
>> >> >> Process:
>> >> >>  * Update <commons.release.version> in pom
>> >> >>  * "mvn commons:download-page" to gen the .xml
>> >> >> download page
>> >> >>  * "mvn site-deploy" (or similar)
>> >> >>
>> >> >> As an aside (though perhaps its related), I
>> saw a
>> >> >> couple of updates to
>> >> >> SVN tags go by -- it'd be best if we can avoid
>> >> >> these.
>> >> >>
>> >> >
>> >> > As these were updates directly related to
>> creating
>> >> > RC5, I have no idea how to appease you in this
>> >> regard.
>> >> >  :(
>> >>
>> >> Theres really two ways of doing this.
>> >>
>> >> 1) Do all the updates in the trunk and then tag
>> >> 2) Create a branch for the release, update there
>> and
>> >> then tag
>> >>
>> >> IMO best to choose 1) if the whole focus is only
>> on
>> >> the current
>> >> release and 2) if other people are want to
>> continue
>> >> to do development
>> >> and not have to hold off on commits while the
>> >> release is being done.
>> >>
>> >
>> > So in the pursuit of (1) you would recommend doing
>> all
>> > necessary changes, then rolling them immediately
>> back
>> > after the tag has been copied?
>>
>> No need to roll back, just roll forward once you
>> have a successful
>> release. For me this has just been rolling on the
>> version number to
>> the next SNAPSHOT.
>>
>> Having said that, I usually tag from my local copy
>> which just has the
>> version number change (all other changes, e.g. site
>> committed to
>> trunk) - not sure if Rahul considers that equivalent
>> to / as bad as
>> updating a Tag.
>>
>> For example the last Chain release candidates:
>>   http://markmail.org/message/nk4v42ptxcuoemir
>>   http://markmail.org/message/2awdi7hntpqhmghw
>>   http://markmail.org/message/chkvopsanzwrlstq
>>
>
> Apparently I'm not svn-savvy enough... what cmd
> accomplishes this?
>
<snip/>

svn cp (WC --> WC [1]) + mods + svn ci

Graphical clients have corresponding gestures for the first bit, such
as "right drag" [2] in TortoiseSVN.

-Rahul

[1] http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.copy.html
[2] http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug.html#tsvn-dug-right-drag



> Thanks,
> Matt
>
>> Niall
>>
>> > -Matt
>> >
>> >> Niall
>> >>
>> >> > -Matt
>> >> >
>> >> >> -Rahul
>> >> >>
>> >> >>
>> >> >> >  This is
>> >> >> > confusing to me.
>> >> >> >
>> >> >> > Thanks,
>> >> >> > Matt
>> >> >> >
>> >> >> >
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [all] release preparation

Posted by Rahul Akolkar <ra...@gmail.com>.
On Tue, Jul 29, 2008 at 1:28 PM, Niall Pemberton
<ni...@gmail.com> wrote:
> On Tue, Jul 29, 2008 at 5:33 PM, Matt Benson <gu...@yahoo.com> wrote:
>>
>> --- Niall Pemberton <ni...@gmail.com> wrote:
>>
>>> On Tue, Jul 29, 2008 at 3:47 PM, Matt Benson
>>> <gu...@yahoo.com> wrote:
>>> >
>>> > --- Rahul Akolkar <ra...@gmail.com> wrote:
>>> >
>>> >> On Mon, Jul 28, 2008 at 6:54 PM, Matt Benson
>>> >> <gu...@yahoo.com> wrote:
>>> >> > Is a `mvn site` from  a src distribution
>>> supposed
>>> >> to
>>> >> > generate download_[component].cgi?
>>> >> <snip/>
>>> >>
>>> >> No.
>>> >>
>>> >>
>>> >> >  If not, are we
>>> >> > intended to make sure we preserve the existing
>>> >> file or
>>> >> > re-create it when deploying the site?
>>> >> <snap/>
>>> >>
>>> >> Don't need to do anything special for it (its
>>> >> preserved by default).
>>> >>
>>> >> Process:
>>> >>  * Update <commons.release.version> in pom
>>> >>  * "mvn commons:download-page" to gen the .xml
>>> >> download page
>>> >>  * "mvn site-deploy" (or similar)
>>> >>
>>> >> As an aside (though perhaps its related), I saw a
>>> >> couple of updates to
>>> >> SVN tags go by -- it'd be best if we can avoid
>>> >> these.
>>> >>
>>> >
>>> > As these were updates directly related to creating
>>> > RC5, I have no idea how to appease you in this
>>> regard.
>>> >  :(
>>>
>>> Theres really two ways of doing this.
>>>
>>> 1) Do all the updates in the trunk and then tag
>>> 2) Create a branch for the release, update there and
>>> then tag
>>>
>>> IMO best to choose 1) if the whole focus is only on
>>> the current
>>> release and 2) if other people are want to continue
>>> to do development
>>> and not have to hold off on commits while the
>>> release is being done.
>>>
>>
>> So in the pursuit of (1) you would recommend doing all
>> necessary changes, then rolling them immediately back
>> after the tag has been copied?
>
> No need to roll back, just roll forward once you have a successful
> release. For me this has just been rolling on the version number to
> the next SNAPSHOT.
>
> Having said that, I usually tag from my local copy which just has the
> version number change (all other changes, e.g. site committed to
> trunk) - not sure if Rahul considers that equivalent to / as bad as
> updating a Tag.
>
<snip/>

The examples below are better since the changes are atomic -- in one
SVN rev (and minimal as well -- other prep changes to trunk/branch as
you suggest).

-Rahul



> For example the last Chain release candidates:
>  http://markmail.org/message/nk4v42ptxcuoemir
>  http://markmail.org/message/2awdi7hntpqhmghw
>  http://markmail.org/message/chkvopsanzwrlstq
>
> Niall
>
>> -Matt
>>
>>> Niall
>>>
>>> > -Matt
>>> >
>>> >> -Rahul
>>> >>
>>> >>
>>> >> >  This is
>>> >> > confusing to me.
>>> >> >
>>> >> > Thanks,
>>> >> > Matt
>>> >> >
>>> >> >

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [all] release preparation

Posted by Matt Benson <gu...@yahoo.com>.
--- Niall Pemberton <ni...@gmail.com> wrote:

> On Tue, Jul 29, 2008 at 5:33 PM, Matt Benson
> <gu...@yahoo.com> wrote:
> >
> > --- Niall Pemberton <ni...@gmail.com>
> wrote:
> >
> >> On Tue, Jul 29, 2008 at 3:47 PM, Matt Benson
> >> <gu...@yahoo.com> wrote:
> >> >
> >> > --- Rahul Akolkar <ra...@gmail.com>
> wrote:
> >> >
> >> >> On Mon, Jul 28, 2008 at 6:54 PM, Matt Benson
> >> >> <gu...@yahoo.com> wrote:
> >> >> > Is a `mvn site` from  a src distribution
> >> supposed
> >> >> to
> >> >> > generate download_[component].cgi?
> >> >> <snip/>
> >> >>
> >> >> No.
> >> >>
> >> >>
> >> >> >  If not, are we
> >> >> > intended to make sure we preserve the
> existing
> >> >> file or
> >> >> > re-create it when deploying the site?
> >> >> <snap/>
> >> >>
> >> >> Don't need to do anything special for it (its
> >> >> preserved by default).
> >> >>
> >> >> Process:
> >> >>  * Update <commons.release.version> in pom
> >> >>  * "mvn commons:download-page" to gen the .xml
> >> >> download page
> >> >>  * "mvn site-deploy" (or similar)
> >> >>
> >> >> As an aside (though perhaps its related), I
> saw a
> >> >> couple of updates to
> >> >> SVN tags go by -- it'd be best if we can avoid
> >> >> these.
> >> >>
> >> >
> >> > As these were updates directly related to
> creating
> >> > RC5, I have no idea how to appease you in this
> >> regard.
> >> >  :(
> >>
> >> Theres really two ways of doing this.
> >>
> >> 1) Do all the updates in the trunk and then tag
> >> 2) Create a branch for the release, update there
> and
> >> then tag
> >>
> >> IMO best to choose 1) if the whole focus is only
> on
> >> the current
> >> release and 2) if other people are want to
> continue
> >> to do development
> >> and not have to hold off on commits while the
> >> release is being done.
> >>
> >
> > So in the pursuit of (1) you would recommend doing
> all
> > necessary changes, then rolling them immediately
> back
> > after the tag has been copied?
> 
> No need to roll back, just roll forward once you
> have a successful
> release. For me this has just been rolling on the
> version number to
> the next SNAPSHOT.
> 
> Having said that, I usually tag from my local copy
> which just has the
> version number change (all other changes, e.g. site
> committed to
> trunk) - not sure if Rahul considers that equivalent
> to / as bad as
> updating a Tag.
> 
> For example the last Chain release candidates:
>   http://markmail.org/message/nk4v42ptxcuoemir
>   http://markmail.org/message/2awdi7hntpqhmghw
>   http://markmail.org/message/chkvopsanzwrlstq
> 

Apparently I'm not svn-savvy enough... what cmd
accomplishes this?

Thanks,
Matt

> Niall
> 
> > -Matt
> >
> >> Niall
> >>
> >> > -Matt
> >> >
> >> >> -Rahul
> >> >>
> >> >>
> >> >> >  This is
> >> >> > confusing to me.
> >> >> >
> >> >> > Thanks,
> >> >> > Matt
> >> >> >
> >> >> >
> 
>
---------------------------------------------------------------------
> 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: [all] release preparation

Posted by Niall Pemberton <ni...@gmail.com>.
On Tue, Jul 29, 2008 at 5:33 PM, Matt Benson <gu...@yahoo.com> wrote:
>
> --- Niall Pemberton <ni...@gmail.com> wrote:
>
>> On Tue, Jul 29, 2008 at 3:47 PM, Matt Benson
>> <gu...@yahoo.com> wrote:
>> >
>> > --- Rahul Akolkar <ra...@gmail.com> wrote:
>> >
>> >> On Mon, Jul 28, 2008 at 6:54 PM, Matt Benson
>> >> <gu...@yahoo.com> wrote:
>> >> > Is a `mvn site` from  a src distribution
>> supposed
>> >> to
>> >> > generate download_[component].cgi?
>> >> <snip/>
>> >>
>> >> No.
>> >>
>> >>
>> >> >  If not, are we
>> >> > intended to make sure we preserve the existing
>> >> file or
>> >> > re-create it when deploying the site?
>> >> <snap/>
>> >>
>> >> Don't need to do anything special for it (its
>> >> preserved by default).
>> >>
>> >> Process:
>> >>  * Update <commons.release.version> in pom
>> >>  * "mvn commons:download-page" to gen the .xml
>> >> download page
>> >>  * "mvn site-deploy" (or similar)
>> >>
>> >> As an aside (though perhaps its related), I saw a
>> >> couple of updates to
>> >> SVN tags go by -- it'd be best if we can avoid
>> >> these.
>> >>
>> >
>> > As these were updates directly related to creating
>> > RC5, I have no idea how to appease you in this
>> regard.
>> >  :(
>>
>> Theres really two ways of doing this.
>>
>> 1) Do all the updates in the trunk and then tag
>> 2) Create a branch for the release, update there and
>> then tag
>>
>> IMO best to choose 1) if the whole focus is only on
>> the current
>> release and 2) if other people are want to continue
>> to do development
>> and not have to hold off on commits while the
>> release is being done.
>>
>
> So in the pursuit of (1) you would recommend doing all
> necessary changes, then rolling them immediately back
> after the tag has been copied?

No need to roll back, just roll forward once you have a successful
release. For me this has just been rolling on the version number to
the next SNAPSHOT.

Having said that, I usually tag from my local copy which just has the
version number change (all other changes, e.g. site committed to
trunk) - not sure if Rahul considers that equivalent to / as bad as
updating a Tag.

For example the last Chain release candidates:
  http://markmail.org/message/nk4v42ptxcuoemir
  http://markmail.org/message/2awdi7hntpqhmghw
  http://markmail.org/message/chkvopsanzwrlstq

Niall

> -Matt
>
>> Niall
>>
>> > -Matt
>> >
>> >> -Rahul
>> >>
>> >>
>> >> >  This is
>> >> > confusing to me.
>> >> >
>> >> > Thanks,
>> >> > Matt
>> >> >
>> >> >

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [all] release preparation

Posted by Matt Benson <gu...@yahoo.com>.
--- Niall Pemberton <ni...@gmail.com> wrote:

> On Tue, Jul 29, 2008 at 3:47 PM, Matt Benson
> <gu...@yahoo.com> wrote:
> >
> > --- Rahul Akolkar <ra...@gmail.com> wrote:
> >
> >> On Mon, Jul 28, 2008 at 6:54 PM, Matt Benson
> >> <gu...@yahoo.com> wrote:
> >> > Is a `mvn site` from  a src distribution
> supposed
> >> to
> >> > generate download_[component].cgi?
> >> <snip/>
> >>
> >> No.
> >>
> >>
> >> >  If not, are we
> >> > intended to make sure we preserve the existing
> >> file or
> >> > re-create it when deploying the site?
> >> <snap/>
> >>
> >> Don't need to do anything special for it (its
> >> preserved by default).
> >>
> >> Process:
> >>  * Update <commons.release.version> in pom
> >>  * "mvn commons:download-page" to gen the .xml
> >> download page
> >>  * "mvn site-deploy" (or similar)
> >>
> >> As an aside (though perhaps its related), I saw a
> >> couple of updates to
> >> SVN tags go by -- it'd be best if we can avoid
> >> these.
> >>
> >
> > As these were updates directly related to creating
> > RC5, I have no idea how to appease you in this
> regard.
> >  :(
> 
> Theres really two ways of doing this.
> 
> 1) Do all the updates in the trunk and then tag
> 2) Create a branch for the release, update there and
> then tag
> 
> IMO best to choose 1) if the whole focus is only on
> the current
> release and 2) if other people are want to continue
> to do development
> and not have to hold off on commits while the
> release is being done.
> 

So in the pursuit of (1) you would recommend doing all
necessary changes, then rolling them immediately back
after the tag has been copied?

-Matt

> Niall
> 
> > -Matt
> >
> >> -Rahul
> >>
> >>
> >> >  This is
> >> > confusing to me.
> >> >
> >> > Thanks,
> >> > Matt
> >> >
> >> >
> >>
> >>
> >
>
---------------------------------------------------------------------
> >> 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
> >
> >
> 
>
---------------------------------------------------------------------
> 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: [all] release preparation

Posted by Rahul Akolkar <ra...@gmail.com>.
On Tue, Jul 29, 2008 at 11:05 AM, Niall Pemberton
<ni...@gmail.com> wrote:
> On Tue, Jul 29, 2008 at 3:47 PM, Matt Benson <gu...@yahoo.com> wrote:
>>
>> --- Rahul Akolkar <ra...@gmail.com> wrote:
>>
>>> On Mon, Jul 28, 2008 at 6:54 PM, Matt Benson
>>> <gu...@yahoo.com> wrote:
>>> > Is a `mvn site` from  a src distribution supposed
>>> to
>>> > generate download_[component].cgi?
>>> <snip/>
>>>
>>> No.
>>>
>>>
>>> >  If not, are we
>>> > intended to make sure we preserve the existing
>>> file or
>>> > re-create it when deploying the site?
>>> <snap/>
>>>
>>> Don't need to do anything special for it (its
>>> preserved by default).
>>>
>>> Process:
>>>  * Update <commons.release.version> in pom
>>>  * "mvn commons:download-page" to gen the .xml
>>> download page
>>>  * "mvn site-deploy" (or similar)
>>>
>>> As an aside (though perhaps its related), I saw a
>>> couple of updates to
>>> SVN tags go by -- it'd be best if we can avoid
>>> these.
>>>
>>
>> As these were updates directly related to creating
>> RC5, I have no idea how to appease you in this regard.
>>  :(
>
> Theres really two ways of doing this.
>
> 1) Do all the updates in the trunk and then tag
> 2) Create a branch for the release, update there and then tag
>
> IMO best to choose 1) if the whole focus is only on the current
> release and 2) if other people are want to continue to do development
> and not have to hold off on commits while the release is being done.
>
<snip/>

Yup, thanks, my thoughts as well.

-Rahul



> Niall
>
>> -Matt
>>
>>> -Rahul
>>>
>>>
>>> >  This is
>>> > confusing to me.
>>> >
>>> > Thanks,
>>> > Matt
>>> >
>>> >
>>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [all] release preparation

Posted by Niall Pemberton <ni...@gmail.com>.
On Tue, Jul 29, 2008 at 3:47 PM, Matt Benson <gu...@yahoo.com> wrote:
>
> --- Rahul Akolkar <ra...@gmail.com> wrote:
>
>> On Mon, Jul 28, 2008 at 6:54 PM, Matt Benson
>> <gu...@yahoo.com> wrote:
>> > Is a `mvn site` from  a src distribution supposed
>> to
>> > generate download_[component].cgi?
>> <snip/>
>>
>> No.
>>
>>
>> >  If not, are we
>> > intended to make sure we preserve the existing
>> file or
>> > re-create it when deploying the site?
>> <snap/>
>>
>> Don't need to do anything special for it (its
>> preserved by default).
>>
>> Process:
>>  * Update <commons.release.version> in pom
>>  * "mvn commons:download-page" to gen the .xml
>> download page
>>  * "mvn site-deploy" (or similar)
>>
>> As an aside (though perhaps its related), I saw a
>> couple of updates to
>> SVN tags go by -- it'd be best if we can avoid
>> these.
>>
>
> As these were updates directly related to creating
> RC5, I have no idea how to appease you in this regard.
>  :(

Theres really two ways of doing this.

1) Do all the updates in the trunk and then tag
2) Create a branch for the release, update there and then tag

IMO best to choose 1) if the whole focus is only on the current
release and 2) if other people are want to continue to do development
and not have to hold off on commits while the release is being done.

Niall

> -Matt
>
>> -Rahul
>>
>>
>> >  This is
>> > confusing to me.
>> >
>> > Thanks,
>> > Matt
>> >
>> >
>>
>>
> ---------------------------------------------------------------------
>> 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
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [all] release preparation

Posted by Matt Benson <gu...@yahoo.com>.
--- Rahul Akolkar <ra...@gmail.com> wrote:

> On Mon, Jul 28, 2008 at 6:54 PM, Matt Benson
> <gu...@yahoo.com> wrote:
> > Is a `mvn site` from  a src distribution supposed
> to
> > generate download_[component].cgi?
> <snip/>
> 
> No.
> 
> 
> >  If not, are we
> > intended to make sure we preserve the existing
> file or
> > re-create it when deploying the site?
> <snap/>
> 
> Don't need to do anything special for it (its
> preserved by default).
> 
> Process:
>  * Update <commons.release.version> in pom
>  * "mvn commons:download-page" to gen the .xml
> download page
>  * "mvn site-deploy" (or similar)
> 
> As an aside (though perhaps its related), I saw a
> couple of updates to
> SVN tags go by -- it'd be best if we can avoid
> these.
> 

As these were updates directly related to creating
RC5, I have no idea how to appease you in this regard.
 :(

-Matt

> -Rahul
> 
> 
> >  This is
> > confusing to me.
> >
> > Thanks,
> > Matt
> >
> >
> 
>
---------------------------------------------------------------------
> 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: [all] release preparation

Posted by Rahul Akolkar <ra...@gmail.com>.
On Mon, Jul 28, 2008 at 6:54 PM, Matt Benson <gu...@yahoo.com> wrote:
> Is a `mvn site` from  a src distribution supposed to
> generate download_[component].cgi?
<snip/>

No.


>  If not, are we
> intended to make sure we preserve the existing file or
> re-create it when deploying the site?
<snap/>

Don't need to do anything special for it (its preserved by default).

Process:
 * Update <commons.release.version> in pom
 * "mvn commons:download-page" to gen the .xml download page
 * "mvn site-deploy" (or similar)

As an aside (though perhaps its related), I saw a couple of updates to
SVN tags go by -- it'd be best if we can avoid these.

-Rahul


>  This is
> confusing to me.
>
> Thanks,
> Matt
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org