Re: Draft proposal for a JSR-303 Bean Validation incubator podling

2009-11-24 Thread Mohammad Nour El-Din
Sorry I reviewed the proposal few days ago and forgot to vote here. +1 On Tue, Nov 24, 2009 at 9:15 PM, Donald Woods wrote: > Will be good to have a member of the JSR-303 EG in the community! > I've added your name to the proposal. > > > -Donald > > > Gerhard Petracek wrote: >> >> hi donald, >>

test

2009-11-24 Thread Ralph Goers
Sorry for the noise - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Re: [dbcp] 1.3 release packaging

2009-11-24 Thread sebb
On 25/11/2009, Phil Steitz wrote: > sebb wrote: > > On 25/11/2009, Phil Steitz wrote: > >> The 1.3 release of dbcp will support JDK 1.4, 1.5 (JDBC 3) and 1.6 > >> (JDBC 4). The Ant build in trunk will work with all three, > >> commenting out the JDBC 4 code when compiling under 1.4 or 1.5.

Re: [dbcp] 1.3 release packaging

2009-11-24 Thread Phil Steitz
sebb wrote: > On 25/11/2009, Phil Steitz wrote: >> The 1.3 release of dbcp will support JDK 1.4, 1.5 (JDBC 3) and 1.6 >> (JDBC 4). The Ant build in trunk will work with all three, >> commenting out the JDBC 4 code when compiling under 1.4 or 1.5. >> >> It does not appear to be possible to prod

Re: [DBCP] Does it still need Maven1 build files? JDBC3_ANT markers?

2009-11-24 Thread sebb
On 24/11/2009, Phil Steitz wrote: > sebb wrote: > > There is an Ant build script and a Maven2 POM, so does DBCP still need > > the following files? > > > > maven.xml > > project.xml > > release-notes.jsl > > > > Also, unless DBCP is still intended to support JDBC2, the JDBC3 ANT > > marke

Re: [dbcp] 1.3 release packaging

2009-11-24 Thread sebb
On 25/11/2009, Phil Steitz wrote: > The 1.3 release of dbcp will support JDK 1.4, 1.5 (JDBC 3) and 1.6 > (JDBC 4). The Ant build in trunk will work with all three, > commenting out the JDBC 4 code when compiling under 1.4 or 1.5. > > It does not appear to be possible to produce a single binary

Re: [dbcp] 1.3 release problems

2009-11-24 Thread sebb
On 24/11/2009, Phil Steitz wrote: > sebb wrote: > > On 24/11/2009, sebb wrote: > >> On 24/11/2009, Phil Steitz wrote: > >> > Phil Steitz wrote: > >> > > sebb wrote: > >> > >> On 22/11/2009, Phil Steitz wrote: > >> > >>> I am running into some problems preparing for dbcp-1.3. I wou

Re: [dbcp] 1.3 release packaging

2009-11-24 Thread Paul Benedict
JBoss Hibernate 3.5 is sitting in the same position because it has to support both JDBC 3 and JDBC 4. There are obvious incompatibilities. For their purposes, they created a general abstraction and then allowed implementations to plug-in. I would similarly follow suit. Produce separate assemblies

[dbcp] 1.3 release packaging

2009-11-24 Thread Phil Steitz
The 1.3 release of dbcp will support JDK 1.4, 1.5 (JDBC 3) and 1.6 (JDBC 4). The Ant build in trunk will work with all three, commenting out the JDBC 4 code when compiling under 1.4 or 1.5. It does not appear to be possible to produce a single binary jar which will work for both JDBC 3 and 4, so

[Lang 3] #isTrue()

2009-11-24 Thread Paul Benedict
I understand why this method exists: public static void isTrue(boolean expression, String message, Object value) But why do these variants exist? public static void isTrue(boolean expression, String message, double value) public static void isTrue(boolean expression, String message, long value) J

Re: [dbcp] 1.3 release problems

2009-11-24 Thread Phil Steitz
sebb wrote: > On 24/11/2009, sebb wrote: >> On 24/11/2009, Phil Steitz wrote: >> > Phil Steitz wrote: >> > > sebb wrote: >> > >> On 22/11/2009, Phil Steitz wrote: >> > >>> I am running into some problems preparing for dbcp-1.3. I would >> > >>> appreciate comments / patches on any of

Re: [DBCP] Does it still need Maven1 build files? JDBC3_ANT markers?

2009-11-24 Thread Phil Steitz
sebb wrote: > There is an Ant build script and a Maven2 POM, so does DBCP still need > the following files? > > maven.xml > project.xml > release-notes.jsl > > Also, unless DBCP is still intended to support JDBC2, the JDBC3 ANT > markers could be removed. All of these can be removed. I dropped

Re: [JEXL 2.0] o.a.c.jexl or o.a.c.jexl2 ?

2009-11-24 Thread Rahul Akolkar
On Tue, Nov 24, 2009 at 5:29 AM, henrib wrote: > > sebb-2-2 wrote: >> >> Perhaps you could let us know exactly what you are planning to do first? >> > 1 - Revisit the JexlContext concept to only expose {set,get}JexlVariable > methods (instead of having to expose setVars/getVars & Map) to make it >

Re: [dbcp] 1.3 release problems

2009-11-24 Thread sebb
On 24/11/2009, sebb wrote: > On 24/11/2009, sebb wrote: > > On 24/11/2009, Phil Steitz wrote: > > > Phil Steitz wrote: > > > > sebb wrote: > > > >> On 22/11/2009, Phil Steitz wrote: > > > >>> I am running into some problems preparing for dbcp-1.3. I would > > > >>> appreciate c

Re: [DBCP] Noisy test output

2009-11-24 Thread sebb
On 23/11/2009, sebb wrote: > The JUnit tests produce a lot of output, even if the tests are successful. > > Is there really any need to print stack traces in the following method? > > TestSharedPoolDataSource.PoolTest.run() > > I propose to comment them out. > > Similarly, the test case TestMa

[DBCP] Does it still need Maven1 build files? JDBC3_ANT markers?

2009-11-24 Thread sebb
There is an Ant build script and a Maven2 POM, so does DBCP still need the following files? maven.xml project.xml release-notes.jsl Also, unless DBCP is still intended to support JDBC2, the JDBC3 ANT markers could be removed. -

Re: Draft proposal for a JSR-303 Bean Validation incubator podling

2009-11-24 Thread Donald Woods
Will be good to have a member of the JSR-303 EG in the community! I've added your name to the proposal. -Donald Gerhard Petracek wrote: hi donald, as project lead of myfaces extval and member of the bv-eg i'm basically interested (for sure). since i'm quite busy (especially within the next

Re: [dbcp] 1.3 release problems

2009-11-24 Thread sebb
On 24/11/2009, sebb wrote: > On 24/11/2009, Phil Steitz wrote: > > Phil Steitz wrote: > > > sebb wrote: > > >> On 22/11/2009, Phil Steitz wrote: > > >>> I am running into some problems preparing for dbcp-1.3. I would > > >>> appreciate comments / patches on any of the issues below. >

Re: [dbcp] 1.3 release problems

2009-11-24 Thread sebb
On 24/11/2009, Phil Steitz wrote: > Phil Steitz wrote: > > sebb wrote: > >> On 22/11/2009, Phil Steitz wrote: > >>> I am running into some problems preparing for dbcp-1.3. I would > >>> appreciate comments / patches on any of the issues below. > >>> > >>> 1. Findbugs is showing some real

Re: [JEXL 2.0] o.a.c.jexl or o.a.c.jexl2 ?

2009-11-24 Thread Jörg Schaible
sebb wrote at Dienstag, 24. November 2009 11:44: > On 24/11/2009, henrib wrote: >> >> >> >> sebb-2-2 wrote: >> > >> > Perhaps you could let us know exactly what you are planning to do >> > first? >> > >> >> 1 - Revisit the JexlContext concept to only expose {set,get}JexlVariable >> methods

Re: [dbcp] 1.3 release problems

2009-11-24 Thread Phil Steitz
Phil Steitz wrote: > sebb wrote: >> On 22/11/2009, Phil Steitz wrote: >>> I am running into some problems preparing for dbcp-1.3. I would >>> appreciate comments / patches on any of the issues below. >>> >>> 1. Findbugs is showing some real (inconsistent synch) and not so >>> real (e.g. serial

[RESULT][VOTE] Apache Commons to sponsor agimatec-validation incunbation

2009-11-24 Thread Niall Pemberton
Both votes (Sponsorship & using Commons mailing lists) have passed with eight votes (seven binding) from the following people: Niall Pemberton Stephen Colebourne Henri Yandell Siegfried Goeschl Phil Steitz Rahul Akolkar Oliver Heger Tommaso Teofili thanks, the next stage is to take the proposal t

Re: [VOTE] Apache Commons to sponsor agimatec-validation incunbation

2009-11-24 Thread Niall Pemberton
On Mon, Nov 23, 2009 at 8:13 PM, Rahul Akolkar wrote: > On Wed, Nov 18, 2009 at 3:34 PM, Niall Pemberton > wrote: > >> >> [X] +1 Yes lets sponsor it >> [ ]  -1 No because... >> > >> >> In order to make it easier for commons to *observe* the incubation >> effort does anyone object to discussion

Re: Draft proposal for a JSR-303 Bean Validation incubator podling

2009-11-24 Thread Niall Pemberton
On Mon, Nov 23, 2009 at 8:31 PM, Jeremy Bauer wrote: > Hi Donald, > > Excellent!  I am interested in being an initial committer. Great, I've added your name to the proposal: http://wiki.apache.org/incubator/ValidationProposal Niall > -Jeremy > (OpenJPA Committer and PMC Member) > > On Wed, Nov

Re: [dbcp] 1.3 release problems

2009-11-24 Thread Phil Steitz
Jörg Schaible wrote: > Phil Steitz wrote at Sonntag, 22. November 2009 17:43: > >> I am running into some problems preparing for dbcp-1.3. I would >> appreciate comments / patches on any of the issues below. >> >> 1. Findbugs is showing some real (inconsistent synch) and not so >> real (e.g. seri

Re: [JEXL 2.0] o.a.c.jexl or o.a.c.jexl2 ?

2009-11-24 Thread sebb
On 24/11/2009, henrib wrote: > > > > sebb-2-2 wrote: > > > > Perhaps you could let us know exactly what you are planning to do first? > > > > 1 - Revisit the JexlContext concept to only expose {set,get}JexlVariable > methods (instead of having to expose setVars/getVars & Map) to make it > ea

Re: [JEXL 2.0] o.a.c.jexl or o.a.c.jexl2 ?

2009-11-24 Thread henrib
sebb-2-2 wrote: > > Perhaps you could let us know exactly what you are planning to do first? > 1 - Revisit the JexlContext concept to only expose {set,get}JexlVariable methods (instead of having to expose setVars/getVars & Map) to make it easier to implement. The "new" JexlContext would be a

Re: [JEXL 2.0] o.a.c.jexl or o.a.c.jexl2 ?

2009-11-24 Thread sebb
On 24/11/2009, henrib wrote: > > Thanks to all for your valuable feedback. > > The general consensus is that although it may be possible to keep oac.jexl, > it is safer to use > oac.jexl2 as the package name for JEXL2. > I'll refresh the code line accordingly soon. > > I might take the oppor

Re: [JEXL 2.0] o.a.c.jexl or o.a.c.jexl2 ?

2009-11-24 Thread henrib
Thanks to all for your valuable feedback. The general consensus is that although it may be possible to keep oac.jexl, it is safer to use oac.jexl2 as the package name for JEXL2. I'll refresh the code line accordingly soon. I might take the opportunity to move some (deep API) classes around to fo