Re: [pool] Reusing Config part 2
Hi all, sorry to be late but my timezone is not 100% compliant with yours :P Just give me the time to read the whole topics so I can contribute as well. Have a nice day, Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Mon, Oct 25, 2010 at 9:04 PM, Gary Gregory wrote: >> -Original Message- >> From: Phil Steitz [mailto:phil.ste...@gmail.com] >> Sent: Monday, October 25, 2010 08:50 >> To: Commons Developers List >> Subject: Re: [pool] Reusing Config part 2 >> >> On 10/25/10 11:26 AM, Gary Gregory wrote: >> > Thank you for working through this Simone. >> > >> > I would like to discuss something I took for granted in my experimental >> patch for [POOL-173]. I can see that you took and a more conservative (and >> safer ;) approach in your version. I am glad to see this because we can now >> more easily discuss it because it is obvious in the code now, where we have >> the following config hierarchy: >> > >> > AbstractGenericObjectPoolConfig >> > GenericKeyedObjectPoolConfig >> > GenericObjectPoolConfig >> > >> > IMO, there should be one Config class (call it GenericObjectPoolConfig for >> example.) This hierarchy reflects that the actual two generic pool classes >> are >> out of sync. >> > >> > For example, why should softMinEvictableIdleTimeMillis exist in >> GenericObjectPool but not in GenericKeyedObjectPoolConfig? >> > >> > When I think about a keyed pool vs. not, I think about a map of pools vs. a >> single pool. It does not make sense that they the have the different >> configurations as reflected by the current hierarchy. >> > >> > Thoughts? >> >> Good point, Gary. The softMin property could and probably should be >> extended to GKOP. The latter does have one property though - >> maxTotal - that only makes sense for a keyed pool. > > OK, that gives validity to one subclass and it feels good to have the other > for symmetry even though it would be initially empty. > > Created tix for GKOP softMin: https://issues.apache.org/jira/browse/POOL-176 > >> >> Unfortunately, another problem that we really have here is that >> several of the config parameters mean different things for keyed vs >> non-keyed pools. For example, maxActive in a keyed pool really >> means max active *per key*. This is why maxTotal has to exist. >> Same holds for maxIdle (but there is no "maxTotalIdle"). I have >> thought about suggesting that we rename these parameters to >> maxActivePerKey and maxIdlePerKey, resp. Then we could dispense >> with maxTotal (and keep maxIdle meaning for the union). We might >> want to think about doing that (though enforcing maxIdle so defined >> will add a little overhead). The nice thing about having the >> hierarchy is that that is an easy change at this point (while we are >> breaking stuff ;). >> >> Phil > > Hm... if they do mean different things, it would be most helpful if that was > reflected in the names. I like your "PerKey" names. I also like prefixes > because names then sort together nicely in tools. getKeyedMaxActive()? > > It only makes sense to reuse the names if the semantics match up. So can we > go through the exercise of naming things properly? > > We could then clearly see what is in common between the two pools. > > Gary > >> > >> > Gary Gregory >> > Senior Software Engineer >> > Rocket Software >> > 3340 Peachtree Road, Suite 820 • Atlanta, GA 30326 • USA >> > Tel: +1.404.760.1560 >> > Email: ggreg...@seagullsoftware.com >> > Web: seagull.rocketsoftware.com >> > >> >> -Original Message- >> >> From: Simone Tripodi [mailto:simone.trip...@gmail.com] >> >> Sent: Monday, October 25, 2010 05:36 >> >> To: Commons Developers List >> >> Subject: Re: [pool] Reusing Config >> >> >> >> Hi all mates, >> >> I updated the jira issue uploading my patch; it contains the >> >> configuration extraction and some code modification. >> >> IMHO we shouldn't replicate the same data in both configuration AND >> >> factory/pool, when creating the factory/pool it is enough storing the >> >> configuration reference, just use it. >> >> I intentionally missed the interfaces layer, since they can be added >> >> directly in the JMX support in the required form. >> >> Please take a look at the patch and provide feedbacks, if you agree I >> >> could start committing the modifications and proceed on JMX support. >> >> Have a nice day, >> >> Simo >> >> >> >> http://people.apache.org/~simonetripodi/ >> >> http://www.99soft.org/ >> >> >> >> >> >> >> >> On Fri, Oct 22, 2010 at 5:23 AM, Gary Gregory >> >> wrote: >> -Original Message- >> From: Steven Siebert [mailto:smsi...@gmail.com] >> Sent: Thursday, October 21, 2010 18:08 >> To: Commons Developers List >> Subject: Re: [pool] Reusing Config >> >> Gary, >> >> Great work so far. I'm checking out the diffs now, I'm gonna hack out >> some >> simple UML "diffs", if only to wrap my head around it all. I'll upload >> the >> file to the issue once com
Re: svn commit: r1027007 - in /commons/proper/math/trunk/src: main/java/org/apache/commons/math/exception/ main/java/org/apache/commons/math/optimization/ main/java/org/apache/commons/math/optimizatio
> > URL: http://svn.apache.org/viewvc?rev=1027007&view=rev > > Log: > > MATH-428 > > Refactoring of "DirectSearchOptimizer" to separate the optimization and > > simplex management aspects. Old classes are deprecated. > > > > [...] > > For now, none of these changes have been committed in the 2.X branch. Do > you intend to add them later on ? I've just tried to copy the files and got 45 errors... I'd guess that some of them cannot be solved without compatibility breaking changes. Hence, the answer would be "no". Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GUMP@vmgump]: Project commons-email (in module apache-commons) 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 gene...@gump.apache.org. Project commons-email has an issue affecting its community integration. This issue affects 2 projects, and has been outstanding for 38 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-email : Commons Email Package - fulcrum-template : Services Framework Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-email/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole jar output [commons-email-1.3-SNAPSHOT.jar] identifier set to project name -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/apache-commons/email/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/email/pom.xml -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-email/gump_work/build_apache-commons_commons-email.html Work Name: build_apache-commons_commons-email (Type: Build) Work ended in a state of : Failed Elapsed: 44 secs Command Line: mvn --batch-mode -Dmaven.jar.mail=/srv/gump/packages/javamail-1.4/mail.jar --settings /srv/gump/public/workspace/apache-commons/email/gump_mvn_settings.xml package [Working Directory: /srv/gump/public/workspace/apache-commons/email] - --- T E S T S --- Running org.apache.commons.mail.EmailTest log4j:WARN No appenders could be found for logger (org.subethamail.smtp.server.CommandHandler). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. Tests run: 40, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.712 sec Running org.apache.commons.mail.EmailAttachmentTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.326 sec Running org.apache.commons.mail.ImageHtmlEmailTest Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.285 sec Running org.apache.commons.mail.HtmlEmailTest Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.174 sec Running org.apache.commons.mail.DefaultAuthenticatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec Running org.apache.commons.mail.SimpleEmailTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec Running org.apache.commons.mail.MultiPartEmailTest Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 sec Running org.apache.commons.mail.EmailLiveTest Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.102 sec <<< FAILURE! Running org.apache.commons.mail.SendWithAttachmentsTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.067 sec Running org.apache.commons.mail.InvalidInternetAddressTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec Running org.apache.commons.mail.InvalidAddressTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec Results : Tests in error: testImageHtmlEmailLocal(org.apache.commons.mail.EmailLiveTest) Tests run: 101, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /srv/gump/public/workspace/apache-commons/email/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 42 seconds [INFO] Finished at: Tue Oct 26 13:13:37 UTC 2010 [INFO] Final Memory: 49M/117M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-email/rss.xml - Atom: http://vmgump.apache.org/gump/public/apache-commons/commons-email/atom.xml == Gump Tracking Only === Produced by Gump version 2.3. Gump Run 22000626102010, vmgump.apache.org:vmgump:22000626102010 Gump E-mail Identifier (unique within run) #11. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[GUMP@vmgump]: Project commons-scxml-test (in module apache-commons) 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 gene...@gump.apache.org. Project commons-scxml-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 40 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-scxml-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven2 settings: [/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml] -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/scxml/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/scxml/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/gump_work/build_apache-commons_commons-scxml-test.html Work Name: build_apache-commons_commons-scxml-test (Type: Build) Work ended in a state of : Failed Elapsed: 30 secs Command Line: mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/scxml] - --- T E S T S --- Running org.apache.commons.scxml.invoke.InvokeTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.66 sec Running org.apache.commons.scxml.test.TestingTestSuite Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running org.apache.commons.scxml.env.EnvTestSuite Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.165 sec Running org.apache.commons.scxml.SCXMLTestSuite Tests run: 71, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.608 sec <<< FAILURE! Running org.apache.commons.scxml.issues.IssuesTestSuite Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.364 sec Running org.apache.commons.scxml.model.ModelTestSuite Tests run: 78, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.427 sec <<< FAILURE! Running org.apache.commons.scxml.env.faces.EnvFacesTestSuite Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.commons.scxml.semantics.SemanticsTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.scxml.env.jsp.EnvJspTestSuite Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec Running org.apache.commons.scxml.env.jexl.EnvJexlTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec Running org.apache.commons.scxml.env.servlet.EnvServletTestSuite Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.scxml.io.IOTestSuite Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.571 sec Results : Failed tests: testNamespacePrefixedXPathsEL(org.apache.commons.scxml.NamespacePrefixedXPathsTest) testDatamodelSimultaneousJsp(org.apache.commons.scxml.model.DatamodelTest) Tests run: 228, Failures: 2, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /srv/gump/public/workspace/apache-commons/scxml/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 29 seconds [INFO] Finished at: Tue Oct 26 14:45:30 UTC 2010 [INFO] Final Memory: 41M/99M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/rss.xml - Atom: http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/atom.xml == Gump Tracking Only === Produced by Gump version 2.3. Gump Run 22000626102010, vmgump.apache.org:vmgump:22000626102010 Gump E-mail Identifier (unique within run) #16. -- Apache Gump http://gump.apache.org/ [Instan
[g...@vmgump]: Project commons-proxy-test (in module apache-commons) 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 gene...@gump.apache.org. Project commons-proxy-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 40 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-proxy-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven2 settings: [/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml] -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/proxy/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/gump_work/build_apache-commons_commons-proxy-test.html Work Name: build_apache-commons_commons-proxy-test (Type: Build) Work ended in a state of : Failed Elapsed: 19 secs Command Line: mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/proxy] - Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.proxy.factory.util.TestMethodSignature Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.provider.TestConstantProvider Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.044 sec Running org.apache.commons.proxy.interceptor.filter.TestPatternFilter Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.proxy.interceptor.TestSerializingInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.032 sec Running org.apache.commons.proxy.interceptor.TestInterceptorChain Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running org.apache.commons.proxy.invoker.TestNullInvoker Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.05 sec Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec Running org.apache.commons.proxy.exception.TestDelegateProviderException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.proxy.invoker.TestChainInvoker Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 sec Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.201 sec Running org.apache.commons.proxy.exception.TestProxyFactoryException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.proxy.interceptor.filter.TestReturnTypeFilter Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.provider.TestBeanProvider Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec Results : Tests in error: testInvalidHandlerName(org.apache.commons.proxy.invoker.TestXmlRpcInvoker) Tests run: 179, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 18 seconds [INFO] Finished at: Tue Oct 26 15:45:44 UTC 2010 [INFO] Final Memory: 39M/93M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/rss.xml - Atom: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/ato
Re: [io] missing java.io.PrintWriter.close() in org.apache.commons.io.testtools.FileBasedTestCase.checkWrite()
On Tue, Oct 26, 2010 at 6:13 AM, Julien Aymé wrote:
> Hi Huxing,
>
> since the PrintStream/PrintWriter are built around an existing (open)
> OutputStream/Writer: the parameter passed to the method,
> it is the responsibility of the caller to close the OutputStream/Writer.
>
> Thus, there is no need to close the PrintStream/PrintWriter (they
> would close the underlying OutputStream/Writer, which is not what
> would be expected when the method is called).
Thanks Julien for responding to this.
I would also add that my main question would be (sorry haven't had
time to look at where this is used within IO's tests) "does this
invalidate or cause IO's tests to fail?"
Niall
> Regards,
> Julien
>
> 2010/10/25 Zhang, Huxing :
>> Dear Apache Commons IO developers,
>> I found there might be a close method missing in the source code of test
>> cases, which may be an issue.
>> No patch seems to be applied till revision 1026932.
>> How do you guys think?
>>
>> The original code here is:
>> In
>> io/trunk/src/test/java/org/apache/commons/io/testtools/FileBasedTestCase.java
>> Line 203-223 (revision 1026932)
>>
>> protected void checkWrite(OutputStream output) throws Exception {
>>try {
>>new java.io.PrintStream(output).write(0);
>>} catch (Throwable t) {
>>throw new AssertionFailedError(
>>"The copy() method closed the stream "
>>+ "when it shouldn't have. "
>>+ t.getMessage());
>>}
>>}
>>
>>protected void checkWrite(Writer output) throws Exception {
>>try {
>>new java.io.PrintWriter(output).write('a');
>>} catch (Throwable t) {
>>throw new AssertionFailedError(
>>"The copy() method closed the stream "
>>+ "when it shouldn't have. "
>>+ t.getMessage());
>>}
>>}
>>
>> The java.io.PrintWriter is initialized without being closed after use. So
>> does the java.io.PrintStream instance.
>>
>> Thanks &Best regards,
>> Huxing
>>
>>
>
> -
> 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: r1027007 - in /commons/proper/math/trunk/src: main/java/org/apache/commons/math/exception/ main/java/org/apache/commons/math/optimization/ main/java/org/apache/commons/math/optimizatio
Le 26/10/2010 13:46, Gilles Sadowski a écrit : >>> URL: http://svn.apache.org/viewvc?rev=1027007&view=rev >>> Log: >>> MATH-428 >>> Refactoring of "DirectSearchOptimizer" to separate the optimization and >>> simplex management aspects. Old classes are deprecated. >>> >>> [...] >> >> For now, none of these changes have been committed in the 2.X branch. Do >> you intend to add them later on ? > > I've just tried to copy the files and got 45 errors... > I'd guess that some of them cannot be solved without compatibility breaking > changes. Hence, the answer would be "no". Then the @since should not say features have been introduced in 2.2 and the things to be removed in 3.0 should really be removed. Now that we have a separate playground fro 3.0 (trunk) and 2.2 (branch), I propose we really do some cleaning of the deprecated stuff we have lying around. Luc > > > Gilles > > - > 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: r1027007 - in /commons/proper/math/trunk/src: main/java/org/apache/commons/math/exception/ main/java/org/apache/commons/math/optimization/ main/java/org/apache/commons/math/optimizatio
On Tue, Oct 26, 2010 at 08:05:23PM +0200, Luc Maisonobe wrote: > Le 26/10/2010 13:46, Gilles Sadowski a écrit : > >>> URL: http://svn.apache.org/viewvc?rev=1027007&view=rev > >>> Log: > >>> MATH-428 > >>> Refactoring of "DirectSearchOptimizer" to separate the optimization and > >>> simplex management aspects. Old classes are deprecated. > >>> > >>> [...] > >> > >> For now, none of these changes have been committed in the 2.X branch. Do > >> you intend to add them later on ? > > > > I've just tried to copy the files and got 45 errors... > > I'd guess that some of them cannot be solved without compatibility breaking > > changes. Hence, the answer would be "no". > > Then the @since should not say features have been introduced in 2.2 and > the things to be removed in 3.0 should really be removed. I think that those things with '@since 2.2' where written before the MATH_2_X branch was created. I'm indicating '@deprecated in 2.2' even in the trunk hoping that it would be useful for tracking changes. But if you prefer, I'll just delete the deprecated stuff. > Now that we have a separate playground fro 3.0 (trunk) and 2.2 (branch), > I propose we really do some cleaning of the deprecated stuff we have > lying around. That's what I'm doing; I have lot of changes pending in package "linear", so please don't do any cleanup there before I commit. Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
RE: [ANNOUNCEMENT] Apache Commons Exec 1.1 Released
Many Thanks to Siegfried and Konrad for the hard work they have contributed to fixing past bugs and implementing new features for common-exec If you could provide a link I will download and run the testcases. Vielen Danke, Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Sun, 24 Oct 2010 09:05:12 +0200 > From: siegfried.goes...@it20one.at > To: dev@commons.apache.org; u...@commons.apache.org > Subject: [ANNOUNCEMENT] Apache Commons Exec 1.1 Released > > The commons-exec-team is pleased to announce the commons-exec-1.1.jar > release! > > A library to reliably execute external processes from within the JVM > > Changes in this version include: > > New features: > > o Adding 'Argument' class and quote the arguments after expansion. > o Added TutorialTest as a playground for new user and removed > similar code from DefaultExecutorTest. > o Added 'DefaultExecuteResultHandler' > > Fixed Bugs: > > o OpenVMS now uses symbols instead of logicals for environment variables. > o String substitution handles now java.io.File instances in order to > create a cross-platform file name. > o The 'forever.bat' accidentally overwrite the 'forever.txt' instead > of appending. > o Process.waitFor should clear interrupt status when throwing > InterruptedException Issue: EXEC-46. Thanks to Zimmermann Nir. > o Because the ExecuteWatchdog is the only way to destroy asynchronous > processes, it should be possible to set it to an infinite timeout, > for processes which should not timeout, but manually destroyed > under some circumstances. Issue: EXEC-44. > > Changes: > > o DefaultExecutor() now sets the working directory with the current > working directory. > o Added 'DefaultExecutorTest#testStdInHandling' to show how > commons-exec can feed the 'stdin' of a child process. > o Improved the documentation. Issue: EXEC-42. Thanks to Konrad Windzus. > o Added a new section to the tutorial to show working with asynchronous > processes. Thanks to Pablo Hoertner. > > Have fun! > > -commons-exec-team > > > - > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org > For additional commands, e-mail: user-h...@commons.apache.org >
