Le 30/03/2011 03:36, Gary Gregory a écrit :
> Wait! I'm not done or I'm loosing my marbles...
>
> I followed the whole song and dance from:
>
> http://wiki.apache.org/commons/UsingNexus
>
> It's the last time I'll pick that route.
For what its worth, for math 2.2 I used a mix of Phil scripts fo
On Mar 29, 2011, at 7:40 PM, Stephen Williams wrote:
> On 3/29/11 7:33 PM, Ralph Goers wrote:
>> On Mar 29, 2011, at 7:24 PM, Stephen Williams wrote:
>>> ...
>>> So, lesson learned: Don't use Maven! ;-)
>>> No, the other one: make copies of your code through multiple means until it
>>> is compl
+1 :)
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, Mar 30, 2011 at 8:17 AM, Phil Steitz wrote:
> The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/pool/tags/POOL_1_5_6_RC2
>
> The distribution zips/tars are here:
> http://people.apache.org/~pstei
On Mar 30, 2011, at 12:01 AM, Luc Maisonobe wrote:
> Le 30/03/2011 03:36, Gary Gregory a écrit :
>> Wait! I'm not done or I'm loosing my marbles...
>>
>> I followed the whole song and dance from:
>>
>> http://wiki.apache.org/commons/UsingNexus
>>
>> It's the last time I'll pick that route.
>
+1
Two comments:
- At the site top left javadocs for 1.5.6 are not linked
- groupId is commons-pool. Shouldn't it change to org.apache or
something? Guess that one is for later
I have not checked sigs
On Wed, Mar 30, 2011 at 8:17 AM, Phil Steitz wrote:
> The tag is here:
> http://svn.apache.or
On 3/30/11 12:02 AM, Ralph Goers wrote:
On Mar 29, 2011, at 7:40 PM, Stephen Williams wrote:
On 3/29/11 7:33 PM, Ralph Goers wrote:
On Mar 29, 2011, at 7:24 PM, Stephen Williams wrote:
...
So, lesson learned: Don't use Maven! ;-)
No, the other one: make copies of your code through multiple me
Le 30/03/2011 09:07, Ralph Goers a écrit :
>
> On Mar 30, 2011, at 12:01 AM, Luc Maisonobe wrote:
>
>> Le 30/03/2011 03:36, Gary Gregory a écrit :
>>> Wait! I'm not done or I'm loosing my marbles...
>>>
>>> I followed the whole song and dance from:
>>>
>>> http://wiki.apache.org/commons/UsingNexu
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-scxml-test has an issue affecting its community integration.
This
On Wed, Mar 30, 2011 at 02:21:04AM +0100, sebb wrote:
> On 30 March 2011 01:15, Gilles Sadowski wrote:
> > Hi.
> >
> >> We have been talking about moving away from interfaces as the
> >> preferred way to support people plugging in alternative
> >> implementations because they have in several place
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-id has an issue affecting its community integration.
This issue af
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-proxy-test has an issue affecting its community integration.
This
Hi Jorg.
> >
> > From comments that were posted to the other thread, I gather the main
> > trend that, because some interfaces needed an upgrade, the "interface"
> > design tool is becoming "evil". Did I get this right?
> >
> > I guess that you refer to "RandomData" and "RandomDataImpl". This is
On 30 March 2011 06:30, Phil Steitz wrote:
> On 3/29/11 6:30 PM, sebb wrote:
>> On 30 March 2011 01:13, wrote:
>>> Author: psteitz
>>> Date: Wed Mar 30 00:13:51 2011
>>> New Revision: 1086810
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1086810&view=rev
>>> Log:
>>> Upgraded parent pom, downgra
Le 30/03/2011 13:33, Gilles Sadowski a écrit :
> On Wed, Mar 30, 2011 at 02:21:04AM +0100, sebb wrote:
>> On 30 March 2011 01:15, Gilles Sadowski wrote:
>>> Hi.
>>>
We have been talking about moving away from interfaces as the
preferred way to support people plugging in alternative
On 30 March 2011 08:07, Ralph Goers wrote:
>
> On Mar 30, 2011, at 12:01 AM, Luc Maisonobe wrote:
>
>> Le 30/03/2011 03:36, Gary Gregory a écrit :
>>> Wait! I'm not done or I'm loosing my marbles...
>>>
>>> I followed the whole song and dance from:
>>>
>>> http://wiki.apache.org/commons/UsingNexus
On 30 March 2011 08:01, Luc Maisonobe wrote:
> Le 30/03/2011 03:36, Gary Gregory a écrit :
>> Wait! I'm not done or I'm loosing my marbles...
>>
>> I followed the whole song and dance from:
>>
>> http://wiki.apache.org/commons/UsingNexus
>>
>> It's the last time I'll pick that route.
>
> For what
On Tue, Mar 29, 2011 at 8:52 PM, sebb wrote:
> I think that should be avoided unless the API is also being changed in
> an incompatible way, and then only if it really is impossible to
> maintain backwards compatibility.
I think there are excellent reasons to change the API in codec.
Reasons inc
On 3/30/11 5:39 AM, sebb wrote:
> On 30 March 2011 08:01, Luc Maisonobe wrote:
>> Le 30/03/2011 03:36, Gary Gregory a écrit :
>>> Wait! I'm not done or I'm loosing my marbles...
>>>
>>> I followed the whole song and dance from:
>>>
>>> http://wiki.apache.org/commons/UsingNexus
>>>
>>> It's the las
On Mar 30, 2011, at 12:04, Phil Steitz wrote:
> On 3/30/11 5:39 AM, sebb wrote:
>> On 30 March 2011 08:01, Luc Maisonobe wrote:
>>> Le 30/03/2011 03:36, Gary Gregory a �crit :
Wait! I'm not done or I'm loosing my marbles...
I followed the whole song and dance from:
htt
I think that you reason on the basic assumption that CM is close to
stability. Many problems (some bugs but also design consistency) have shown
that it is not. So, my opinion is that users will prefer a product that
continues to improve rather than something that is backward-compatible. I'm
one of
On 30 March 2011 16:19, Jochen Wiedmann wrote:
> On Tue, Mar 29, 2011 at 8:52 PM, sebb wrote:
>
>> I think that should be avoided unless the API is also being changed in
>> an incompatible way, and then only if it really is impossible to
>> maintain backwards compatibility.
>
> I think there are
We are mixing two things in this thread - how much we care about
backward compatibility and how and when to use interfaces.
I think we need to settle both topics. I have stated my view, which
is really just to standard Commons policy, on the backward
compatibility issue. Based on many years expe
On 30 March 2011 17:03, Phil Steitz wrote:
> On 3/30/11 5:39 AM, sebb wrote:
>> On 30 March 2011 08:01, Luc Maisonobe wrote:
>>> Le 30/03/2011 03:36, Gary Gregory a écrit :
Wait! I'm not done or I'm loosing my marbles...
I followed the whole song and dance from:
http://wi
On Mar 30, 2011, at 13:24, sebb wrote:
> On 30 March 2011 17:03, Phil Steitz wrote:
>> On 3/30/11 5:39 AM, sebb wrote:
>>> On 30 March 2011 08:01, Luc Maisonobe wrote:
Le 30/03/2011 03:36, Gary Gregory a écrit :
> Wait! I'm not done or I'm loosing my marbles...
>
> I followed t
On 3/30/11 10:24 AM, sebb wrote:
> On 30 March 2011 17:03, Phil Steitz wrote:
>> On 3/30/11 5:39 AM, sebb wrote:
>>> On 30 March 2011 08:01, Luc Maisonobe wrote:
Le 30/03/2011 03:36, Gary Gregory a écrit :
> Wait! I'm not done or I'm loosing my marbles...
>
> I followed the whole
Hi Gilles,
Gilles Sadowski wrote:
> Hi Jorg.
>
>> >
>> > From comments that were posted to the other thread, I gather the main
>> > trend that, because some interfaces needed an upgrade, the "interface"
>> > design tool is becoming "evil". Did I get this right?
>> >
>> > I guess that you refer
On 30/03/2011 18:43, Phil Steitz wrote:
> I get that, which is why I think some kind of middle ground where we
> provide simple scripts to move stuff around on the ASF hosts might
> be a good compromise. This is essentially what the ibiblio-rysnch
> stuff does. The only manual missing piece is co
On 30 March 2011 19:23, Mark Thomas wrote:
> On 30/03/2011 18:43, Phil Steitz wrote:
>> I get that, which is why I think some kind of middle ground where we
>> provide simple scripts to move stuff around on the ASF hosts might
>> be a good compromise. This is essentially what the ibiblio-rysnch
>
>
> > I cannot seem to have published the Maven bits to Maven places. There is
> no
> > 1.5 here:
> >
> > http://repo1.maven.org/maven2/commons-codec/commons-codec/
>
Still nothing there. :(
Gary
On 3/30/11 11:23 AM, Mark Thomas wrote:
> On 30/03/2011 18:43, Phil Steitz wrote:
>> I get that, which is why I think some kind of middle ground where we
>> provide simple scripts to move stuff around on the ASF hosts might
>> be a good compromise. This is essentially what the ibiblio-rysnch
>> st
+1
Thank you to Phil for RM'ing.
All is well on my system:
Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_24
Java home: C:\Program Files\Java\jdk1.6.0_24\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "amd64" Family: "wi
On 30/03/2011 07:17, Phil Steitz wrote:
> The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/pool/tags/POOL_1_5_6_RC2
>
> The distribution zips/tars are here:
> http://people.apache.org/~psteitz/pool-1.5.6-rc2/
MD5/SHA1s match for source distributions.
OpenPGP signatures valid and
On 3/30/11 1:21 PM, Mark Thomas wrote:
> On 30/03/2011 07:17, Phil Steitz wrote:
>> The tag is here:
>> http://svn.apache.org/repos/asf/commons/proper/pool/tags/POOL_1_5_6_RC2
>>
>> The distribution zips/tars are here:
>> http://people.apache.org/~psteitz/pool-1.5.6-rc2/
> MD5/SHA1s match for sourc
On 30 March 2011 21:37, Phil Steitz wrote:
> On 3/30/11 1:21 PM, Mark Thomas wrote:
>> On 30/03/2011 07:17, Phil Steitz wrote:
>>> The tag is here:
>>> http://svn.apache.org/repos/asf/commons/proper/pool/tags/POOL_1_5_6_RC2
>>>
>>> The distribution zips/tars are here:
>>> http://people.apache.org/
On 30 March 2011 06:30, Phil Steitz wrote:
> On 3/29/11 6:30 PM, sebb wrote:
>> On 30 March 2011 01:13, wrote:
>>> Author: psteitz
>>> Date: Wed Mar 30 00:13:51 2011
>>> New Revision: 1086810
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1086810&view=rev
>>> Log:
>>> Upgraded parent pom, downgra
Commons Codec 1.5 was promoted from Nexus on 29 March 2011 06:21
and is showing up here:
https://repository.apache.org/content/groups/staging/commons-codec/commons-codec/1.5/
However it has yet to show up in Maven Central over 24 hours later.
http://repo1.maven.org/maven2/commons-codec/commons-
Hi all guys,
I recently needed the Discovery in a project of mine and noticed we
haven't had releases since 2008. I would like to update it, improving
a little the design - like, for example, using the generics.
Any objection? Thanks in advance, have a nice day,
Simo
http://people.apache.org/~simo
On Wed, Mar 30, 2011 at 6:03 PM, Phil Steitz wrote:
> There is this cool command called "cp" that works very well. There
> is another one called "tar" and even one called "scp" ;) If the
> problem is that we want to be more paranoid than we are with the
> mirrors for the maven stuff, why can't
On Wed, Mar 30, 2011 at 7:04 PM, sebb wrote:
> But does the API have to change, or could these additional features be
> supported by adding new methods and classes?
Not necessarily. But my point is that codec is in a state where
breaking the API will make work just easier. So why not take the
op
On Tue, Mar 29, 2011 at 5:52 PM, Phil Steitz wrote:
> I disagree with this. The most important artifacts are the
> zips/tars that go to dist/. These *are* the ASF release. Nexus
> makes it *harder* IMO to maintain provenance of these artifacts.
These artifacts are present in Nexus. Pulling th
On 31 March 2011 00:17, Jochen Wiedmann wrote:
> On Wed, Mar 30, 2011 at 7:04 PM, sebb wrote:
>
>> But does the API have to change, or could these additional features be
>> supported by adding new methods and classes?
>
> Not necessarily. But my point is that codec is in a state where
> breaking
On 31 March 2011 00:22, Jochen Wiedmann wrote:
> On Tue, Mar 29, 2011 at 5:52 PM, Phil Steitz wrote:
>
>> I disagree with this. The most important artifacts are the
>> zips/tars that go to dist/. These *are* the ASF release. Nexus
>> makes it *harder* IMO to maintain provenance of these artifa
On 3/30/11 4:22 PM, Jochen Wiedmann wrote:
> On Tue, Mar 29, 2011 at 5:52 PM, Phil Steitz wrote:
>
>> I disagree with this. The most important artifacts are the
>> zips/tars that go to dist/. These *are* the ASF release. Nexus
>> makes it *harder* IMO to maintain provenance of these artifacts.
On Wed, Mar 30, 2011 at 6:30 AM, Phil Steitz wrote:
> On 3/29/11 6:30 PM, sebb wrote:
>> On 30 March 2011 01:13, wrote:
>>> Author: psteitz
>>> Date: Wed Mar 30 00:13:51 2011
>>> New Revision: 1086810
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1086810&view=rev
>>> Log:
>>> Upgraded parent pom
On 31 March 2011 02:00, Niall Pemberton wrote:
> On Wed, Mar 30, 2011 at 6:30 AM, Phil Steitz wrote:
>> On 3/29/11 6:30 PM, sebb wrote:
>>> On 30 March 2011 01:13, wrote:
Author: psteitz
Date: Wed Mar 30 00:13:51 2011
New Revision: 1086810
URL: http://svn.apache.org/vie
On 31 March 2011 01:38, Phil Steitz wrote:
> On 3/30/11 4:22 PM, Jochen Wiedmann wrote:
>> On Tue, Mar 29, 2011 at 5:52 PM, Phil Steitz wrote:
>>
>>> I disagree with this. The most important artifacts are the
>>> zips/tars that go to dist/. These *are* the ASF release. Nexus
>>> makes it *hard
I'm seeing a lot of complaining on these threads but no actual proposal. If the
proposal is to move away from Maven/Nexus for a release for all of commons I'll
vote -1. OTOH, If some release managers want to do the release some other way
I'm not going to force them to use Maven/Nexus.
Ralph
On 3/30/11 6:57 PM, sebb wrote:
> On 31 March 2011 01:38, Phil Steitz wrote:
>> On 3/30/11 4:22 PM, Jochen Wiedmann wrote:
>>> On Tue, Mar 29, 2011 at 5:52 PM, Phil Steitz wrote:
>>>
I disagree with this. The most important artifacts are the
zips/tars that go to dist/. These *are* the
On 3/30/11 7:07 PM, Ralph Goers wrote:
> I'm seeing a lot of complaining on these threads but no actual proposal.
I started the thread with a proposal, which was to standardize on
the process documented on the web site. I know you don't like that
process and I am not going to insist that we force
On 3/29/11 11:17 PM, Phil Steitz wrote:
> The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/pool/tags/POOL_1_5_6_RC2
>
> The distribution zips/tars are here:
> http://people.apache.org/~psteitz/pool-1.5.6-rc2/
>
> Maven artifacts are here:
> http://people.apache.org/~psteitz/pool-1.
50 matches
Mail list logo
