[VOTE] Release of DbUtils 1.2 RC2
My second attempt at releasing a commons project; please be gentle. :-) RC2 includes sebb's patches that make numerous instance variables immutable. NOTE: No one has yet explicitly said on-list that they have tested DbUtils 1.2 RC1 or RC2 with a real database. We should not release it until somebody tries it out with a real live Oracle database, as described below. Compatibility warnings: * We upgraded the JVM dependency from JDK 1.3 to JDK 1.4 (DBUTILS-31) * Users who may have extended BeanListHandler.handleRow will find that this method no longer exists (is no longer called) in DbUtils 1.2 (DBUTILS-37) * Users who may have extended KeyedHandler will find that its protected members are now final (to guarantee thread safety). (DBUTILS-51) PLEASE TEST THIS RELEASE WITH A REAL DATABASE! Although this project has reasonable unit tests, it has no integration tests with any actual databases; it is quite possible that the fix for DBUTILS-31 has broken something on Oracle, MS SQL Server, Derby, or your favorite database. To verify DBUTILS-31, use QueryRunner to put a null value in a field, e.g. with QueryRunner.update. Ideally it would be good to verify putting nulls in fields of various types: char, varchar, int, boolean, date, etc. -- Tag: https://svn.apache.org/repos/asf/commons/proper/dbutils/tags/DBUTILS_1_2 Site: http://people.apache.org/builds/commons/dbutils/1.2/RC2/site/index.html Binaries: http://people.apache.org/builds/commons/dbutils/1.2/RC2/staged/commons-dbutils/commons-dbutils/1.2/ [ ] +1 release it [ ] +0 go ahead I don't care [ ] -1 no, do not release it because - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release of DbUtils 1.2 RC1
sebb wrote: I think there are some problems with thread-safety. Yikes! I didn't investigate very carefully the thread-safety claims of these classes (again, not much has changed since 1.1) but I agree with your assessment, now that I open my eyes and think about it. In revision 752369 I incorporated the patches you attached to http://issues.apache.org/jira/browse/DBUTILS-51 However, the KeyedHandler instance variables are protected, rather than private, so making them final would perhaps break some programs. I don't think the class can be thread-safe at present. I don't think there's a lot of risk that users required these values to be mutable; I would assume that most users just called the super constructor, so I applied this patch, too. -Dan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[VOTE] Release Commons CLI 1.2 (RC6)
One more try :) Stating that the Java version is 1.4 on the website will be done post-release (I'm going to split the CLI and CLI2 websites). --- Tag: https://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.2-RC6 Site remains unchanged: http://people.apache.org/~bayard/cli-1.2-rc1 Binaries: http://people.apache.org/builds/commons/cli/1.2/RC6/staged/commons-cli/commons-cli/1.2/ [ ] +1 release it [ ] +0 go ahead I don't care [ ] -1 no, do not release it because - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Commons CLI 1.2 (RC5)
1.4 it is then. I cba to deal with duplicated build logic in my old age :) So a pom change, update to latest junit then regenerate dist. Hen On Tue, Mar 10, 2009 at 11:10 AM, sebb wrote: > Duh - ignore that. > > Just noticed that ParserTestCase is an abstract class... > > I used "mvn ant:ant" to create the build file so I could test with 1.3 > and the generated file did not exclude ParserTestCase. > > When it is excluded, the tests complete OK. > > Perhaps there is a case for renaming that class ;-) > > More seriously, if a release targets 1.3, it should include some way > of building and testing the code using 1.3. > > On 10/03/2009, sebb wrote: >> That would certainly help with testing... >> >> I tried removing the test case with the Java 1.4 class, and the test >> still fails on Java 1.3.1_20 (Win/XP). >> >> The failure is >> >> Cannot instantiate test case: testSimpleShort >> (java.lang.InstantiationException: >> org.apache.commons.cli.ParserTestCase >> at java.lang.reflect.Constructor.newInstance(Native Method) >> at junit.framework.TestSuite.createTest(TestSuite.java:131) >> at junit.framework.TestSuite.addTestMethod(TestSuite.java:114) >> at junit.framework.TestSuite.(TestSuite.java:75) >> >> This appears to be caused by the setUp() method which creates an >> Options() instance and adds 3 options to it. If the code is changed to >> add only 2 options, the failure does not occur, but of course some of >> the tests fail. Odder yet, adding another option allows setUp() to >> work, but still some tests fail. >> >> Looks like Java 1.3.1_20 or JUnit 3.8.1 or the combination is broken. >> >> Is it worth trying to support 1.3 now? >> >> >> On 10/03/2009, Gary Gregory wrote: >> > Why not change the Java req. to Java 1.4 for CLI 1.2? (Hides from flying >> tomatoes.) >> > >> > >> > Gary >> > >> > >> > -Original Message- >> > From: sebb [mailto:seb...@gmail.com] >> > Sent: Tuesday, March 10, 2009 5:45 AM >> > >> > To: Commons Developers List >> > Subject: Re: [VOTE] Release Commons CLI 1.2 (RC5) >> > >> > -1 >> > >> > Will not build on Java 1.3 as java.sql.ParameterMetaData is @since 1.4. >> > >> > So at least the Java source version in the POM needs changing. >> > I've not yet tried testing on Java 1.3 after building on 1.4 >> > >> > Also the site does not appear to mention the minimum Java requirements >> anywhere. >> > >> > BTW, if it is decided to move to Java 1.4 as a minimum, JUnit should >> > be updated to 3.8.2. >> > >> > On 10/03/2009, Gary Gregory wrote: >> > > +1 >> > > >> > > Builds and tests on Sun Java 1.6.0_12 on Windows XP SP3. >> > > >> > > >> > > Gary >> > > >> > > >> > > -Original Message- >> > > From: Henri Yandell [mailto:flame...@gmail.com] >> > > Sent: Monday, March 09, 2009 6:41 PM >> > > To: Commons Developers List >> > > Subject: [VOTE] Release Commons CLI 1.2 (RC5) >> > > >> > > One more shot :) >> > > >> > > >> > > Tag: >> > > >> > > https://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.2-RC5 >> > > >> > > Site remains unchanged: >> > > >> > > http://people.apache.org/~bayard/cli-1.2-rc1 >> > > >> > > Binaries: >> > > >> > > >> http://people.apache.org/builds/commons/cli/1.2/RC5/staged/commons-cli/commons-cli/1.2/ >> > > >> > > [ ] +1 release it >> > > [ ] +0 go ahead I don't care >> > > [ ] -1 no, do not release it because >> > > >> > > - >> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > > For additional commands, e-mail: dev-h...@commons.apache.org >> > > >> > > >> > > - >> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > > For additional commands, e-mail: dev-h...@commons.apache.org >> > > >> > > >> > >> > - >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > For additional commands, e-mail: dev-h...@commons.apache.org >> > >> > >> > - >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > For additional commands, e-mail: dev-h...@commons.apache.org >> > >> > >> > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release of DbUtils 1.2 RC1
I think there are some problems with thread-safety. QueryRunner Javadoc says the class is thread-safe. However it has a protected mutable variable DataSource which can also be set/got via public methods. If one thread sets the variable, another may not see the correct value, so the class is not thread-safe. ArrayHandler has a non-final instance variable "convert" which could be made final. Likewise BasicRowProcessor. This would make the classes immutable, and therefore thread-safe. It's not clear if they are thread-safe without making the variables final. The same applies to most of the handlers - they have instance variables which could be made final. However, the KeyedHandler instance variables are protected, rather than private, so making them final would perhaps break some programs. I don't think the class can be thread-safe at present. I'll raise a JIRA with suggested patches. On 11/03/2009, Dan Fabulich wrote: > sebb wrote: > > > > -0.5 because the unit tests seem wrong. > > > > I've incorporated your feedback in revision 752322. For the record, all of > those tests predate DbUtils 1.1; we haven't touched them in years. > > I think these test changes are pretty minor; not worth an additional RC. > What do you think? > > -Dan > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release of DbUtils 1.2 RC1
Jörg Schaible wrote: However, IBM JDK 6 fails here: --- Test set: org.apache.commons.dbutils.QueryRunnerTest --- Tests run: 8, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.341 sec <<< FAILURE! testFillStatementWithBeanErrorReadMethodPrivate(org.apache.commons.dbutils.QueryRunnerTest) It seems that this JDK does more internal checks. Possibly fixed in trunk revision 752329. (Fumbled fingers and accidentally forgot to add a commit message.) Please try again in trunk; I think it should work. -Dan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release of DbUtils 1.2 RC1
sebb wrote: -0.5 because the unit tests seem wrong. I've incorporated your feedback in revision 752322. For the record, all of those tests predate DbUtils 1.1; we haven't touched them in years. I think these test changes are pretty minor; not worth an additional RC. What do you think? -Dan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [openmodels] planning WAS Re: gauging sandbox interest - openmodels
Not claiming that it is setup properly but jci is a m2 multi project. Still maybe worth having a look. Welcome to a world of pain ...which I found m2 is when you go multi project. That said it seems to be working for the maven folks - so maybe it's just a user error. cheers -- Torsten On Tue, Mar 10, 2009 at 18:01, Matt Benson wrote: > > I have some code to start with (never been anywhere but my box so no IP > problems) but I am currently using Ant + Ivy. This will be an empty project > with n subprojects so I feel I will need a ridiculous amount of handholding > to get this set up properly with m2. Do any of our Maven mavens have the > cycles for this? > > Thanks, > Matt > > --- On Sun, 3/1/09, Henri Yandell wrote: > >> From: Henri Yandell >> Subject: Re: gauging sandbox interest - openmodels >> To: "Commons Developers List" >> Date: Sunday, March 1, 2009, 1:20 PM >> No reason not to give it a try and if >> it's too large it can move out of Commons. >> >> http://issues.apache.org/jira/browse/LANG-449 might be >> of interest to it. >> >> Hen >> >> On Sun, Mar 1, 2009 at 9:15 AM, Matt Benson >> wrote: >> > >> > For awhile I've had an itch that it would be nice to >> have a project whose purpose is to provide small, realistic >> domain models for consumption primarily by tests of >> library-type code (if the domain models are actually >> usable/extensible for real work, so much the better). It >> seems to me that particularly at Commons it could be >> beneficial for tests/examples of various components to >> reference common object models, giving potential users a >> better point of reference to see how various components >> might be used with their own models. Is there any interest >> in having such a project in Commons; do we feel this would >> be too large and not precisely the mission of Commons; are >> there other opinions? >> > >> > Thanks, >> > Matt >> > >> > >> > >> > >> > >> - >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > For additional commands, e-mail: dev-h...@commons.apache.org >> > >> > >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Commons CLI 1.2 (RC5)
+1 from me >> From: Henri Yandell >> Sent: Monday, March 09, 2009 6:41 PM >> To: Commons Developers List >> Subject: [VOTE] Release Commons CLI 1.2 (RC5) >> >> One more shot :) >> >> >> Tag: >> >> https://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.2-RC5 >> >> Site remains unchanged: >> >> http://people.apache.org/~bayard/cli-1.2-rc1 >> >> Binaries: >> >> http://people.apache.org/builds/commons/cli/1.2/RC5/staged/commons-cli/commons-cli/1.2/ >> >> [ ] +1 release it >> [ ] +0 go ahead I don't care >> [ ] -1 no, do not release it because >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
RE: [VOTE] Release Commons CLI 1.2 (RC5)
The case for us supporting Java 1.3 is that someone is actively maintaining an application based on Java 1.3 only and wants to upgrade CLI 1.1 to 1.2. How likely is that? As we all know, Java 1.3.1 is done: "On Windows, Linux, Solaris 9, and Solaris 10 J2SE 1.3.1 has completed the Sun End of Life (EOL) process." [1] I say it is time for CLI 1.x to move on to Java 1.4.2. Gary [1] http://java.sun.com/j2se/1.3/index.jsp Full quote: "On Windows, Linux, Solaris 9, and Solaris 10 J2SE 1.3.1 has completed the Sun End of Life (EOL) process. The EOL transition period was from Oct 25, 2004 until the General Availability (GA) of Java SE 6 on December 11th, 2006. With this notice, customers are strongly encouraged to migrate to the current release, Java SE 6. > Read More. A paid Java Vintage Support Offering is available for those customers who are interested in continuing to obtain support for the release. Please contact your Sun sales representative for details." -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Tuesday, March 10, 2009 11:11 AM To: Commons Developers List Subject: Re: [VOTE] Release Commons CLI 1.2 (RC5) Duh - ignore that. Just noticed that ParserTestCase is an abstract class... I used "mvn ant:ant" to create the build file so I could test with 1.3 and the generated file did not exclude ParserTestCase. When it is excluded, the tests complete OK. Perhaps there is a case for renaming that class ;-) More seriously, if a release targets 1.3, it should include some way of building and testing the code using 1.3. On 10/03/2009, sebb wrote: > That would certainly help with testing... > > I tried removing the test case with the Java 1.4 class, and the test > still fails on Java 1.3.1_20 (Win/XP). > > The failure is > > Cannot instantiate test case: testSimpleShort > (java.lang.InstantiationException: > org.apache.commons.cli.ParserTestCase > at java.lang.reflect.Constructor.newInstance(Native Method) > at junit.framework.TestSuite.createTest(TestSuite.java:131) > at junit.framework.TestSuite.addTestMethod(TestSuite.java:114) > at junit.framework.TestSuite.(TestSuite.java:75) > > This appears to be caused by the setUp() method which creates an > Options() instance and adds 3 options to it. If the code is changed to > add only 2 options, the failure does not occur, but of course some of > the tests fail. Odder yet, adding another option allows setUp() to > work, but still some tests fail. > > Looks like Java 1.3.1_20 or JUnit 3.8.1 or the combination is broken. > > Is it worth trying to support 1.3 now? > > > On 10/03/2009, Gary Gregory wrote: > > Why not change the Java req. to Java 1.4 for CLI 1.2? (Hides from flying > tomatoes.) > > > > > > Gary > > > > > > -Original Message- > > From: sebb [mailto:seb...@gmail.com] > > Sent: Tuesday, March 10, 2009 5:45 AM > > > > To: Commons Developers List > > Subject: Re: [VOTE] Release Commons CLI 1.2 (RC5) > > > > -1 > > > > Will not build on Java 1.3 as java.sql.ParameterMetaData is @since 1.4. > > > > So at least the Java source version in the POM needs changing. > > I've not yet tried testing on Java 1.3 after building on 1.4 > > > > Also the site does not appear to mention the minimum Java requirements > anywhere. > > > > BTW, if it is decided to move to Java 1.4 as a minimum, JUnit should > > be updated to 3.8.2. > > > > On 10/03/2009, Gary Gregory wrote: > > > +1 > > > > > > Builds and tests on Sun Java 1.6.0_12 on Windows XP SP3. > > > > > > > > > Gary > > > > > > > > > -Original Message- > > > From: Henri Yandell [mailto:flame...@gmail.com] > > > Sent: Monday, March 09, 2009 6:41 PM > > > To: Commons Developers List > > > Subject: [VOTE] Release Commons CLI 1.2 (RC5) > > > > > > One more shot :) > > > > > > > > > Tag: > > > > > > https://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.2-RC5 > > > > > > Site remains unchanged: > > > > > > http://people.apache.org/~bayard/cli-1.2-rc1 > > > > > > Binaries: > > > > > > > http://people.apache.org/builds/commons/cli/1.2/RC5/staged/commons-cli/commons-cli/1.2/ > > > > > > [ ] +1 release it > > > [ ] +0 go ahead I don't care > > > [ ] -1 no, do not release it because > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additio
Re: [VOTE] Release Commons CLI 1.2 (RC5)
Duh - ignore that. Just noticed that ParserTestCase is an abstract class... I used "mvn ant:ant" to create the build file so I could test with 1.3 and the generated file did not exclude ParserTestCase. When it is excluded, the tests complete OK. Perhaps there is a case for renaming that class ;-) More seriously, if a release targets 1.3, it should include some way of building and testing the code using 1.3. On 10/03/2009, sebb wrote: > That would certainly help with testing... > > I tried removing the test case with the Java 1.4 class, and the test > still fails on Java 1.3.1_20 (Win/XP). > > The failure is > > Cannot instantiate test case: testSimpleShort > (java.lang.InstantiationException: > org.apache.commons.cli.ParserTestCase > at java.lang.reflect.Constructor.newInstance(Native Method) > at junit.framework.TestSuite.createTest(TestSuite.java:131) > at junit.framework.TestSuite.addTestMethod(TestSuite.java:114) > at junit.framework.TestSuite.(TestSuite.java:75) > > This appears to be caused by the setUp() method which creates an > Options() instance and adds 3 options to it. If the code is changed to > add only 2 options, the failure does not occur, but of course some of > the tests fail. Odder yet, adding another option allows setUp() to > work, but still some tests fail. > > Looks like Java 1.3.1_20 or JUnit 3.8.1 or the combination is broken. > > Is it worth trying to support 1.3 now? > > > On 10/03/2009, Gary Gregory wrote: > > Why not change the Java req. to Java 1.4 for CLI 1.2? (Hides from flying > tomatoes.) > > > > > > Gary > > > > > > -Original Message- > > From: sebb [mailto:seb...@gmail.com] > > Sent: Tuesday, March 10, 2009 5:45 AM > > > > To: Commons Developers List > > Subject: Re: [VOTE] Release Commons CLI 1.2 (RC5) > > > > -1 > > > > Will not build on Java 1.3 as java.sql.ParameterMetaData is @since 1.4. > > > > So at least the Java source version in the POM needs changing. > > I've not yet tried testing on Java 1.3 after building on 1.4 > > > > Also the site does not appear to mention the minimum Java requirements > anywhere. > > > > BTW, if it is decided to move to Java 1.4 as a minimum, JUnit should > > be updated to 3.8.2. > > > > On 10/03/2009, Gary Gregory wrote: > > > +1 > > > > > > Builds and tests on Sun Java 1.6.0_12 on Windows XP SP3. > > > > > > > > > Gary > > > > > > > > > -Original Message- > > > From: Henri Yandell [mailto:flame...@gmail.com] > > > Sent: Monday, March 09, 2009 6:41 PM > > > To: Commons Developers List > > > Subject: [VOTE] Release Commons CLI 1.2 (RC5) > > > > > > One more shot :) > > > > > > > > > Tag: > > > > > > https://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.2-RC5 > > > > > > Site remains unchanged: > > > > > > http://people.apache.org/~bayard/cli-1.2-rc1 > > > > > > Binaries: > > > > > > > http://people.apache.org/builds/commons/cli/1.2/RC5/staged/commons-cli/commons-cli/1.2/ > > > > > > [ ] +1 release it > > > [ ] +0 go ahead I don't care > > > [ ] -1 no, do not release it because > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Commons CLI 1.2 (RC5)
That would certainly help with testing... I tried removing the test case with the Java 1.4 class, and the test still fails on Java 1.3.1_20 (Win/XP). The failure is Cannot instantiate test case: testSimpleShort (java.lang.InstantiationException: org.apache.commons.cli.ParserTestCase at java.lang.reflect.Constructor.newInstance(Native Method) at junit.framework.TestSuite.createTest(TestSuite.java:131) at junit.framework.TestSuite.addTestMethod(TestSuite.java:114) at junit.framework.TestSuite.(TestSuite.java:75) This appears to be caused by the setUp() method which creates an Options() instance and adds 3 options to it. If the code is changed to add only 2 options, the failure does not occur, but of course some of the tests fail. Odder yet, adding another option allows setUp() to work, but still some tests fail. Looks like Java 1.3.1_20 or JUnit 3.8.1 or the combination is broken. Is it worth trying to support 1.3 now? On 10/03/2009, Gary Gregory wrote: > Why not change the Java req. to Java 1.4 for CLI 1.2? (Hides from flying > tomatoes.) > > > Gary > > > -Original Message- > From: sebb [mailto:seb...@gmail.com] > Sent: Tuesday, March 10, 2009 5:45 AM > > To: Commons Developers List > Subject: Re: [VOTE] Release Commons CLI 1.2 (RC5) > > -1 > > Will not build on Java 1.3 as java.sql.ParameterMetaData is @since 1.4. > > So at least the Java source version in the POM needs changing. > I've not yet tried testing on Java 1.3 after building on 1.4 > > Also the site does not appear to mention the minimum Java requirements > anywhere. > > BTW, if it is decided to move to Java 1.4 as a minimum, JUnit should > be updated to 3.8.2. > > On 10/03/2009, Gary Gregory wrote: > > +1 > > > > Builds and tests on Sun Java 1.6.0_12 on Windows XP SP3. > > > > > > Gary > > > > > > -Original Message- > > From: Henri Yandell [mailto:flame...@gmail.com] > > Sent: Monday, March 09, 2009 6:41 PM > > To: Commons Developers List > > Subject: [VOTE] Release Commons CLI 1.2 (RC5) > > > > One more shot :) > > > > > > Tag: > > > > https://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.2-RC5 > > > > Site remains unchanged: > > > > http://people.apache.org/~bayard/cli-1.2-rc1 > > > > Binaries: > > > > > http://people.apache.org/builds/commons/cli/1.2/RC5/staged/commons-cli/commons-cli/1.2/ > > > > [ ] +1 release it > > [ ] +0 go ahead I don't care > > [ ] -1 no, do not release it because > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
RE: [VOTE] Release Commons CLI 1.2 (RC5)
Why not change the Java req. to Java 1.4 for CLI 1.2? (Hides from flying tomatoes.) Gary -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Tuesday, March 10, 2009 5:45 AM To: Commons Developers List Subject: Re: [VOTE] Release Commons CLI 1.2 (RC5) -1 Will not build on Java 1.3 as java.sql.ParameterMetaData is @since 1.4. So at least the Java source version in the POM needs changing. I've not yet tried testing on Java 1.3 after building on 1.4 Also the site does not appear to mention the minimum Java requirements anywhere. BTW, if it is decided to move to Java 1.4 as a minimum, JUnit should be updated to 3.8.2. On 10/03/2009, Gary Gregory wrote: > +1 > > Builds and tests on Sun Java 1.6.0_12 on Windows XP SP3. > > > Gary > > > -Original Message- > From: Henri Yandell [mailto:flame...@gmail.com] > Sent: Monday, March 09, 2009 6:41 PM > To: Commons Developers List > Subject: [VOTE] Release Commons CLI 1.2 (RC5) > > One more shot :) > > > Tag: > > https://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.2-RC5 > > Site remains unchanged: > > http://people.apache.org/~bayard/cli-1.2-rc1 > > Binaries: > > > http://people.apache.org/builds/commons/cli/1.2/RC5/staged/commons-cli/commons-cli/1.2/ > > [ ] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Commons CLI 1.2 (RC5)
Will be a close match with commons-exec ... :-) Siegfried Goeschl Henri Yandell wrote: > Easy enough to fix - that was only introduced due to a real world > test. Wonder if we're going to hit a record RC wise... > > On Tue, Mar 10, 2009 at 5:44 AM, sebb wrote: > >> -1 >> >> Will not build on Java 1.3 as java.sql.ParameterMetaData is @since 1.4. >> >> So at least the Java source version in the POM needs changing. >> I've not yet tried testing on Java 1.3 after building on 1.4 >> >> Also the site does not appear to mention the minimum Java requirements >> anywhere. >> >> BTW, if it is decided to move to Java 1.4 as a minimum, JUnit should >> be updated to 3.8.2. >> >> On 10/03/2009, Gary Gregory wrote: >> >>> +1 >>> >>> Builds and tests on Sun Java 1.6.0_12 on Windows XP SP3. >>> >>> >>> Gary >>> >>> >>> -Original Message- >>> From: Henri Yandell [mailto:flame...@gmail.com] >>> Sent: Monday, March 09, 2009 6:41 PM >>> To: Commons Developers List >>> Subject: [VOTE] Release Commons CLI 1.2 (RC5) >>> >>> One more shot :) >>> >>> >>> Tag: >>> >>> https://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.2-RC5 >>> >>> Site remains unchanged: >>> >>> http://people.apache.org/~bayard/cli-1.2-rc1 >>> >>> Binaries: >>> >>> >>> http://people.apache.org/builds/commons/cli/1.2/RC5/staged/commons-cli/commons-cli/1.2/ >>> >>> [ ] +1 release it >>> [ ] +0 go ahead I don't care >>> [ ] -1 no, do not release it because >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >>> >>> >> - >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[openmodels] planning WAS Re: gauging sandbox interest - openmodels
I have some code to start with (never been anywhere but my box so no IP problems) but I am currently using Ant + Ivy. This will be an empty project with n subprojects so I feel I will need a ridiculous amount of handholding to get this set up properly with m2. Do any of our Maven mavens have the cycles for this? Thanks, Matt --- On Sun, 3/1/09, Henri Yandell wrote: > From: Henri Yandell > Subject: Re: gauging sandbox interest - openmodels > To: "Commons Developers List" > Date: Sunday, March 1, 2009, 1:20 PM > No reason not to give it a try and if > it's too large it can move out of Commons. > > http://issues.apache.org/jira/browse/LANG-449 might be > of interest to it. > > Hen > > On Sun, Mar 1, 2009 at 9:15 AM, Matt Benson > wrote: > > > > For awhile I've had an itch that it would be nice to > have a project whose purpose is to provide small, realistic > domain models for consumption primarily by tests of > library-type code (if the domain models are actually > usable/extensible for real work, so much the better). It > seems to me that particularly at Commons it could be > beneficial for tests/examples of various components to > reference common object models, giving potential users a > better point of reference to see how various components > might be used with their own models. Is there any interest > in having such a project in Commons; do we feel this would > be too large and not precisely the mission of Commons; are > there other opinions? > > > > Thanks, > > Matt > > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
RE: [VOTE] Release Commons CLI 1.2 (RC5)
Are we thinking of using Java 5 for CLI 2.0? G -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Tuesday, March 10, 2009 5:45 AM To: Commons Developers List Subject: Re: [VOTE] Release Commons CLI 1.2 (RC5) -1 Will not build on Java 1.3 as java.sql.ParameterMetaData is @since 1.4. So at least the Java source version in the POM needs changing. I've not yet tried testing on Java 1.3 after building on 1.4 Also the site does not appear to mention the minimum Java requirements anywhere. BTW, if it is decided to move to Java 1.4 as a minimum, JUnit should be updated to 3.8.2. On 10/03/2009, Gary Gregory wrote: > +1 > > Builds and tests on Sun Java 1.6.0_12 on Windows XP SP3. > > > Gary > > > -Original Message- > From: Henri Yandell [mailto:flame...@gmail.com] > Sent: Monday, March 09, 2009 6:41 PM > To: Commons Developers List > Subject: [VOTE] Release Commons CLI 1.2 (RC5) > > One more shot :) > > > Tag: > > https://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.2-RC5 > > Site remains unchanged: > > http://people.apache.org/~bayard/cli-1.2-rc1 > > Binaries: > > > http://people.apache.org/builds/commons/cli/1.2/RC5/staged/commons-cli/commons-cli/1.2/ > > [ ] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Commons CLI 1.2 (RC5)
Easy enough to fix - that was only introduced due to a real world test. Wonder if we're going to hit a record RC wise... On Tue, Mar 10, 2009 at 5:44 AM, sebb wrote: > -1 > > Will not build on Java 1.3 as java.sql.ParameterMetaData is @since 1.4. > > So at least the Java source version in the POM needs changing. > I've not yet tried testing on Java 1.3 after building on 1.4 > > Also the site does not appear to mention the minimum Java requirements > anywhere. > > BTW, if it is decided to move to Java 1.4 as a minimum, JUnit should > be updated to 3.8.2. > > On 10/03/2009, Gary Gregory wrote: >> +1 >> >> Builds and tests on Sun Java 1.6.0_12 on Windows XP SP3. >> >> >> Gary >> >> >> -Original Message- >> From: Henri Yandell [mailto:flame...@gmail.com] >> Sent: Monday, March 09, 2009 6:41 PM >> To: Commons Developers List >> Subject: [VOTE] Release Commons CLI 1.2 (RC5) >> >> One more shot :) >> >> >> Tag: >> >> https://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.2-RC5 >> >> Site remains unchanged: >> >> http://people.apache.org/~bayard/cli-1.2-rc1 >> >> Binaries: >> >> http://people.apache.org/builds/commons/cli/1.2/RC5/staged/commons-cli/commons-cli/1.2/ >> >> [ ] +1 release it >> [ ] +0 go ahead I don't care >> [ ] -1 no, do not release it because >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: svn commit: r752029 - /commons/sandbox/compress/trunk/NOTICE.txt
On 10/03/2009, Stefan Bodewig wrote: > On 2009-03-10, sebb wrote: > > > On 10/03/2009, bode...@apache.org wrote: > > > >> standard NOTICE header, a bit of whitespace > > > The header is specifically NOT required for NOTICE files, which is why > > RAT does not insist on adding one. > > > The nice thing about policies is that they change every so often and > you have to be following so many lists to know when they do. 8-) As far as I know, that has never changed. But I've not been around since the beginning. > I took the boilerplate text from Ant. When the last version of Ant > was released, the header was required. > > Thanks for the catch, I'll remove it. > > Stefan > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: svn commit: r752029 - /commons/sandbox/compress/trunk/NOTICE.txt
On 2009-03-10, sebb wrote: > On 10/03/2009, bode...@apache.org wrote: >> standard NOTICE header, a bit of whitespace > The header is specifically NOT required for NOTICE files, which is why > RAT does not insist on adding one. The nice thing about policies is that they change every so often and you have to be following so many lists to know when they do. 8-) I took the boilerplate text from Ant. When the last version of Ant was released, the header was required. Thanks for the catch, I'll remove it. Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: svn commit: r752029 - /commons/sandbox/compress/trunk/NOTICE.txt
On 10/03/2009, bode...@apache.org wrote: > Author: bodewig > Date: Tue Mar 10 09:34:08 2009 > New Revision: 752029 > > URL: http://svn.apache.org/viewvc?rev=752029&view=rev > Log: > standard NOTICE header, a bit of whitespace The header is specifically NOT required for NOTICE files, which is why RAT does not insist on adding one. A NOTICE file is supposed to be the sort of text that is displayed in an About box, i.e. as short as possible. See http://www.apache.org/legal/src-headers.html#notice > Modified: > commons/sandbox/compress/trunk/NOTICE.txt > > Modified: commons/sandbox/compress/trunk/NOTICE.txt > URL: > http://svn.apache.org/viewvc/commons/sandbox/compress/trunk/NOTICE.txt?rev=752029&r1=752028&r2=752029&view=diff > > == > --- commons/sandbox/compress/trunk/NOTICE.txt (original) > +++ commons/sandbox/compress/trunk/NOTICE.txt Tue Mar 10 09:34:08 2009 > @@ -1,10 +1,21 @@ > + = > + == NOTICE file corresponding to the section 4 d of== > + == the Apache License, Version 2.0, == > + == in this case for the Apache Commons Compress distribution. == > + = > + > Apache Commons Compress > Copyright 2002-2009 The Apache Software Foundation > > This product includes software developed by > The Apache Software Foundation (http://www.apache.org/). > > -Original BZip2 classes contributed by Keiron Liddle , > Aftex Software to the Apache Ant project > +Original BZip2 classes contributed by Keiron Liddle > +, Aftex Software to the Apache Ant project > + > Original Tar classes from contributors of the Apache Ant project > + > Original Zip classes from contributors of the Apache Ant project > -Original CPIO classes contributed by Markus Kuss and the jRPM project > (jrpm.sourceforge.net) > + > +Original CPIO classes contributed by Markus Kuss and the jRPM project > +(jrpm.sourceforge.net) > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Commons CLI 1.2 (RC5)
-1 Will not build on Java 1.3 as java.sql.ParameterMetaData is @since 1.4. So at least the Java source version in the POM needs changing. I've not yet tried testing on Java 1.3 after building on 1.4 Also the site does not appear to mention the minimum Java requirements anywhere. BTW, if it is decided to move to Java 1.4 as a minimum, JUnit should be updated to 3.8.2. On 10/03/2009, Gary Gregory wrote: > +1 > > Builds and tests on Sun Java 1.6.0_12 on Windows XP SP3. > > > Gary > > > -Original Message- > From: Henri Yandell [mailto:flame...@gmail.com] > Sent: Monday, March 09, 2009 6:41 PM > To: Commons Developers List > Subject: [VOTE] Release Commons CLI 1.2 (RC5) > > One more shot :) > > > Tag: > > https://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.2-RC5 > > Site remains unchanged: > > http://people.apache.org/~bayard/cli-1.2-rc1 > > Binaries: > > > http://people.apache.org/builds/commons/cli/1.2/RC5/staged/commons-cli/commons-cli/1.2/ > > [ ] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
