[configuration] JDK compatibility

2007-12-12 Thread Oliver Heger
(There was a similar discussion about commons lang recently.) Configuration used to support JDK 1.3. For the next release (either 1.6 or 2.0) I would like to drop this compatibility. The number of feature requests that require a newer JDK version is increasing. This raises a couple of questio

Re: [all] Commons SCXML 0.7 RC2 available

2007-12-12 Thread Oliver Heger
Everything looks good to me. Oliver Rahul Akolkar wrote: I've incorporated Sebb and Niall's feedback on RC1 and produced RC2. Tag: http://svn.apache.org/repos/asf/commons/proper/scxml/tags/SCXML_0_7_RC2/ Artifacts: http://people.apache.org/~rahul/commons/scxml-0.7/rc2/ Staged site: htt

Re: [all] Commons SCXML 0.7 RC2 available

2007-12-12 Thread sebb
On 12/12/2007, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > I've incorporated Sebb and Niall's feedback on RC1 and produced RC2. > > Tag: > > http://svn.apache.org/repos/asf/commons/proper/scxml/tags/SCXML_0_7_RC2/ A few files still refer to jakarta for stuff that has moved to commons TLP: build.p

[all] Commons SCXML 0.7 RC2 available

2007-12-12 Thread Rahul Akolkar
I've incorporated Sebb and Niall's feedback on RC1 and produced RC2. Tag: http://svn.apache.org/repos/asf/commons/proper/scxml/tags/SCXML_0_7_RC2/ Artifacts: http://people.apache.org/~rahul/commons/scxml-0.7/rc2/ Staged site: http://people.apache.org/~rahul/commons/scxml-0.7/rc2/site/ Not

Re: [pool] 1.3-1.4 compatibility

2007-12-12 Thread sebb
On 12/12/2007, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > On 12/12/07, sebb <[EMAIL PROTECTED]> wrote: > > > > > By the way, build.xml creates the build/ directory tree, but this is > > not excluded from SVN, unlike dist/ and target/. Not sure how to > > create an SVN property patch... > > > > >

Re: [pool] 1.3-1.4 compatibility

2007-12-12 Thread Rahul Akolkar
On 12/12/07, sebb <[EMAIL PROTECTED]> wrote: > > By the way, build.xml creates the build/ directory tree, but this is > not excluded from SVN, unlike dist/ and target/. Not sure how to > create an SVN property patch... > Like any other patch. Or just commit (given the nature of this change). -R

Re: [pool] 1.3-1.4 compatibility

2007-12-12 Thread sebb
On 12/12/2007, sebb <[EMAIL PROTECTED]> wrote: > On 12/12/2007, Phil Steitz <[EMAIL PROTECTED]> wrote: > > Quick update on this. > > > > I created 1_4_RELEASE_BRANCH so we should be reviewing / patching the > > code there for the release. > > > > Clirr flagged only the change in default values for

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

2007-12-12 Thread commons-jelly-tags-jaxme development
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

Re: [VOTE] Relase Version 2 of Commons Skin (2nd attempt)

2007-12-12 Thread Dennis Lundberg
+1 Makes you want to go to Amsterdam ;-) Niall Pemberton wrote: I have managed to work round the problems I had the other night trying to release commons-skin-2 and have staged a release in the snapshot repo here: http://people.apache.org/repo/m2-snapshot-repository/org/apache/commons/comm

Re: [pool] 1.3-1.4 compatibility

2007-12-12 Thread sebb
On 12/12/2007, Phil Steitz <[EMAIL PROTECTED]> wrote: > Quick update on this. > > I created 1_4_RELEASE_BRANCH so we should be reviewing / patching the > code there for the release. > > Clirr flagged only the change in default values for > DEFAULT_TEST_ON_BORROW mentioned above. Among the changes

Re: [pool] 1.3-1.4 compatibility

2007-12-12 Thread Phil Steitz
Quick update on this. I created 1_4_RELEASE_BRANCH so we should be reviewing / patching the code there for the release. Clirr flagged only the change in default values for DEFAULT_TEST_ON_BORROW mentioned above. Among the changes described in [1] that have been implemented, I think we need to ro