The new package, org.apache.commons.lang3.text.translate, felt weird
as I started to write about it. It makes it sound like it handles
languages.
I'm going to change it to:
org.apache.commons.lang3.text.transform
Hen
-
To unsub
--- On Sun, 3/28/10, Phil Steitz wrote:
> Adrian Crum wrote:
> > --- On Sun, 3/28/10, Luc Maisonobe
> wrote:
> >> Adrian Crum a écrit :
> >>> --- On Sat, 3/27/10, Phil Steitz
> >> wrote:
> Adrian Crum wrote:
> > --- On Sat, 3/27/10, Rahul Akolkar
>
> wrote:
> >> Adrian Crum
>
On Mon, Apr 5, 2010 at 1:54 PM, sebb wrote:
> I think it might be useful to add a note regarding consistency between
> changes.xml, RELEASE-NOTES and JIRA.
>
> For example, if JIRA FOO-1234 is fixed in release 1.2, then IMO it
> should have a JIRA "fix" release of 1.2, and appear in the
> changes
Would love to see this.
I'll go and put the historic Lang ones together if you let me know how
you'd like it to look.
Hen
On Mon, Apr 5, 2010 at 9:16 AM, Gary Gregory
wrote:
> Seeing the discussion about [daemon] and not releasing made me think of
> another use for a test jar file.
>
> What I
Hi,
I am ready to help you with analysis & ideas to improve your
work(Sorry I don't have time to code but helping you in logic will be
fine with me).
I will try my best to help you in every way possible.Keep up the good work.
I also do research in AI (Neural networks,machine learning ,etc)..If
y
Hi all,
I am a master student from China, and having using Apache Commons SCXML for
years,now i have a idea to do something for Commons SCXML, i hold it as a
GSoC project and finished its project proposal,submit it on GSoC website
already. I named it "An Eclipse-based Visual State Chart XML editor/
On 05/04/2010, Phil Steitz wrote:
> I have made my first attempt at updating the documentation here:
> http://commons.apache.org/releases/index.html
>
> Given that the previous docs were so out of date as to be pretty
> much worthless, I thought it best to push things along with CTR -
> actual
Luc Maisonobe wrote:
> Phil Steitz a écrit :
>> I have made my first attempt at updating the documentation here:
>> http://commons.apache.org/releases/index.html
>
> Thanks for this documentation, Phil.
>
> I have one question and one comment.
>
> In the "Create the release candidate" section, y
Phil Steitz a écrit :
> I have made my first attempt at updating the documentation here:
> http://commons.apache.org/releases/index.html
Thanks for this documentation, Phil.
I have one question and one comment.
In the "Create the release candidate" section, you write: "Note that the
release cand
On 05/04/2010, Gary Gregory wrote:
> > -Original Message-
> > From: sebb [mailto:seb...@gmail.com]
> > Sent: Monday, April 05, 2010 11:17
> > To: Commons Developers List
> > Subject: Re: [codec][lang] Provide a test jar plus [daemon]
> >
>
> > On 05/04/2010, Gary Gregory wrote:
> >
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: Monday, April 05, 2010 11:17
> To: Commons Developers List
> Subject: Re: [codec][lang] Provide a test jar plus [daemon]
>
> On 05/04/2010, Gary Gregory wrote:
> > I do not think Clirr is enough as exemplified by the chan
Even if the package names are different and thus binary compatibility
is not preserved, the @since tags are still important to delineate new
functionality before 3.0. It can help people with migrating.
On Mon, Apr 5, 2010 at 12:26 PM, Gary Gregory
wrote:
>> -Original Message-
>> From: seb
On 05/04/2010, Gary Gregory wrote:
> I do not think Clirr is enough as exemplified by the change of behavior in
> Base64 encoding with CRLFs between version 1.3 and 1.4 (see CODEC-94.)
Agreed - Clirr is necessary, but not sufficient.
> There is no substitute for running unit tests.
Agreed; ho
I do not think Clirr is enough as exemplified by the change of behavior in
Base64 encoding with CRLFs between version 1.3 and 1.4 (see CODEC-94.)
There is no substitute for running unit tests.
As we change code in a component, unit tests are created or changed. It is
possible to create compatib
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: Saturday, March 27, 2010 16:19
> To: Commons Developers List
> Subject: Re: [lang] v3.0 @since
>
> On 27/03/2010, Gary Gregory wrote:
> > Since multiple @since tags are allowed and are treated like multiple @author
> tags
Is it not sufficient to simply run clirr reports before a release?
-Matt
On Apr 5, 2010, at 11:16 AM, Gary Gregory wrote:
Seeing the discussion about [daemon] and not releasing made me
think of another use for a test jar file.
What I would like to know when evaluating an RC for releasing a
Folks!
The only discussion seems to be about "how to retire the project", not
"if to retire the project". This means to me we all agree to at least
temporarily retire it and there is no more discussion about how to do
it.
As the Apache commons way of retiring seems to be to move it to the
dormant
Seeing the discussion about [daemon] and not releasing made me think of another
use for a test jar file.
What I would like to know when evaluating an RC for releasing a maintenance of
a commons component (from x.y.n to x.y.n+1) is that there is 100% binary
compatibility.
As part of the build I
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-io-test has an issue affecting its community integration.
This iss
I have made my first attempt at updating the documentation here:
http://commons.apache.org/releases/index.html
Given that the previous docs were so out of date as to be pretty
much worthless, I thought it best to push things along with CTR -
actually "PTR" (p = publish). I am sure there are some
20 matches
Mail list logo
