Re: [logging] change groupId (Re: [RESULT][VOTE] Release commons-logging 1.1.1 (take 4))

Joerg Hohwiller <[EMAIL PROTECTED]> schrieb: > Could you please change the groupId to "org.apache.commons.logging". > It is an ugly legacy problem that many projects are still ignoring the maven > conventions. > > Here are the good boys that have already been convinced: > http://repo1.maven.o

[DBCP] 1.3 release?

I see that a 1.3 commons-dbcp release has been discussed a couple of times on the list. Can someone help me understand where things stand, currently? OpenEJB is currently dependent upon 1.3-SNAPSHOT. Would be great to get a released version of dbcp. I may be able to lend a hand, if needed

[logging] maven: deploy *-sources.jar as well

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, could you also generate the sources.jar files? http://maven.apache.org/plugins/maven-source-plugin/usage.html then also deploy them to central repo as well. Thanks a lot Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linu

[logging] change groupId (Re: [RESULT][VOTE] Release commons-logging 1.1.1 (take 4))

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, > ...and we have a winner! I am a little late ;) Could you please change the groupId to "org.apache.commons.logging". It is an ugly legacy problem that many projects are still ignoring the maven conventions. Here are the good boys that have

Re: svn commit: r601912 - in /commons/proper/scxml/trunk: build.xml pom.xml project.xml

On 06/12/2007, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > On 12/6/07, sebb <[EMAIL PROTECTED]> wrote: > > On 06/12/2007, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Author: rahul > > > Date: Thu Dec 6 15:25:54 2007 > > > New Revision: 601912 > > > > > > URL: http://svn.apache.org/viewvc?rev

[logging] start JSR to add interface "org.apache.commons.logging.Log" to JDK

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everybody, you might say I am crazy but I am totally serious with this. I mentioned the idea once before but was more like joking. I kept thinking about this one and came to the impression that there are good arguments to do so: We should open a J

Re: svn commit: r601912 - in /commons/proper/scxml/trunk: build.xml pom.xml project.xml

On 12/6/07, sebb <[EMAIL PROTECTED]> wrote: > On 06/12/2007, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Author: rahul > > Date: Thu Dec 6 15:25:54 2007 > > New Revision: 601912 > > > > URL: http://svn.apache.org/viewvc?rev=601912&view=rev > > Log: > > Time to use a recent JUnit release. > >

Re: svn commit: r601912 - in /commons/proper/scxml/trunk: build.xml pom.xml project.xml

On 06/12/2007, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Author: rahul > Date: Thu Dec 6 15:25:54 2007 > New Revision: 601912 > > URL: http://svn.apache.org/viewvc?rev=601912&view=rev > Log: > Time to use a recent JUnit release. > Does JUnit 4.4 not require Java 1.5? The pom says to use 1.4

[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

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 [EMAIL PROTECTED] Project commons-jelly-tags-jaxme has an issue affecting its community integration. This

[RESULT][VOTE] Relase Version 2 of Commons Skin

This vote has passed with the following votes: +1 Ben Speakmon +1 Rahul Akolkar +1 Jörg Schaible +1 Luc Maisonobe +1 Niall Pemberton Thanks, I'll cut the release as soon as I can figure out how to do that with m2 (hints appreciated). Niall On Nov 29, 2007 1:58 PM, Niall Pemberton <[EMAIL PROTEC

[CLI2] Patch for CVS Unit Test in CLI2 Code

Hi developers, i would like to ask what you think about the appended Unit Test patch. I have enhanced the Unit Test for CVS a "little" and would like to know if you would appreciate to see such kind of a Unit Test in this kind of direction? If you appreciate such a Unit test i would like to conti