RE: [VFS]HttpConnectionManager
Hi! -Original Message- From: Ralph Goers [mailto:ralph.go...@dslextreme.com] Sent: Monday, February 23, 2009 8:29 AM Thanks Mario. VFS-164 wasn't really clear. Was the problem the limit to 2 connections per host that MultiThreadedHttpConnectionManager has by default? Sorry, I can't remember :-( Yes, I think it hang, and I am not sure if the maxConnectionsPerHost existed at this time, or probably I just overlooked it *grmpf*. I've added maxConnectionsPerHost and maxTotalConnections to HttpFileSystemConfigBuilder and also allowed them to be specified as system properties. You would make a lot of people happy (I think) if you implement this in a commons way, so that every FileSystemOption can also be specified using system properties. Or did you already? :-) Something like -Dvfsopt.ftp.passiveMode=true You can use the DelegatingFileSystemOptionsBuilder to help you here. FileSystemOptions fso = new FileSystemOptions(); DelegatingFileSystemOptionsBuilder delegate = new DelegatingFileSystemOptionsBuilder(VFS.getManager()); delegate.setConfigString(fso, sftp, identities, c:/tmp/test.ident); delegate.setConfigString(fso, http, proxyPort, 8080); delegate.setConfigClass(fso, sftp, userinfo, TrustEveryoneUserInfo.class); by iterating over the System properties, taking each vfsopt.* and split it so taht you can pass it to setConfigString. This can do the trick. Ciao, Mario - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VFS]HttpConnectionManager
On Feb 23, 2009, at 12:18 AM, Mario Ivankovits wrote: I've added maxConnectionsPerHost and maxTotalConnections to HttpFileSystemConfigBuilder and also allowed them to be specified as system properties. You would make a lot of people happy (I think) if you implement this in a commons way, so that every FileSystemOption can also be specified using system properties. Or did you already? :-) Something like -Dvfsopt.ftp.passiveMode=true You can use the DelegatingFileSystemOptionsBuilder to help you here. FileSystemOptions fso = new FileSystemOptions(); DelegatingFileSystemOptionsBuilder delegate = new DelegatingFileSystemOptionsBuilder(VFS.getManager()); delegate.setConfigString(fso, sftp, identities, c:/tmp/ test.ident); delegate.setConfigString(fso, http, proxyPort, 8080); delegate.setConfigClass(fso, sftp, userinfo, TrustEveryoneUserInfo.class); by iterating over the System properties, taking each vfsopt.* and split it so taht you can pass it to setConfigString. This can do the trick. Thanks. No, I hadn't done that but I will definitely give it a try! Ralph - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[g...@vmgump]: Project commons-vfs (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-vfs has an issue affecting its community integration. This issue affects 29 projects, and has been outstanding for 117 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - ant-contrib : Useful little Ant tasks - ant-contrib-test : Useful little Ant tasks - antbook-diary-core : Examples to go with Java Development with Ant - antbook-sections : Examples to go with Java Development with Ant - cddlm : Configuration and Deployment of Grid Applications and System... - commons-vfs : Apache Commons - commons-vfs-sandbox : Apache Commons - excalibur-fortress-bean : Repository of reusable components. - excalibur-fortress-container-impl : Repository of reusable components. - excalibur-fortress-container-test : Repository of reusable components. - excalibur-fortress-examples : Repository of reusable components. - excalibur-fortress-migration : Repository of reusable components. - excalibur-fortress-platform : Repository of reusable components. - excalibur-fortress-testcase : Repository of reusable components. - excalibur-monitor : Repository of reusable components. - excalibur-sourceresolve : Repository of reusable components. - excalibur-xmlutil : Repository of reusable components. - invicta : Open-source build management tool. - ivy : Ivy Core - ivy-tests : Ivy is a tool for managing (recording, tracking, resolving a... - logging-log4cxx-ant : Apache log4cxx - logging-log4cxx-ant-no_wchar_t : Apache log4cxx - logging-log4cxx-ant-static : Apache log4cxx - smartfrog : Smartfrog: Application Deployment from HP Laboratories - smartfrog-components : Smartfrog: Application Deployment from HP Laboratories - smartfrog-tasks : Smartfrog: Application Deployment from HP Laboratories - smartfrog-tasks-test : Smartfrog: Application Deployment from HP Laboratories - smartfrog-test : Smartfrog: Application Deployment from HP Laboratories - smartfrog-testharness : Smartfrog: Application Deployment from HP Laboratories Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-vfs/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-vfs-2.0-SNAPSHOT.jar] identifier set to project name -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/apache-commons/vfs/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/vfs/pom.xml -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-vfs/gump_work/build_apache-commons_commons-vfs.html Work Name: build_apache-commons_commons-vfs (Type: Build) Work ended in a state of : Failed Elapsed: 2 mins 31 secs Command Line: mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/vfs/gump_mvn_settings.xml package [Working Directory: /srv/gump/public/workspace/apache-commons/vfs] CLASSPATH: /usr/lib/jvm/java-6-sun/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/junit/dist/junit-23022009.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-23022009.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-23022009.jar:/srv/gump/public/workspace/apache-commons/collections/build/commons-collections-23022009.jar:/srv/gump/public/workspace/httpcomponent s/2.0.2/commons-httpclient-2.0.2.jar:/srv/gump/public/workspace/apache-commons/net/dist/commons-net-23022009.jar:/srv/gump/packages/jcifs/jcifs-0.8.1.jar:/srv/gump/packages/jsch/jsch-0.1.38.jar - skipping testManualCache because TarFileSystem does not have capability CREATE skipping testOnResolveCache because TarFileSystem does not have capability CREATE skipping testOnCallCache because TarFileSystem does not have capability CREATE skipping testRandomRead
Re: [VOTE] CLI 1.2 release (RC2)
Henri, On Thu, 2009-02-19 at 21:05 -0800, Henri Yandell wrote: IllegalStateException thrown (as it's not a direct argument) when there's not enough width to possibly output things and remain in the width. I'll give it a short period for any discussion and spin off another release candidate. Just to let you know that using Subversion 1.x branch tip, gives me a Commons CLI 1.2 jar that continues to work fine with Groovy and Gant for me -- i.e. none of the recent changes have perturbed anything for me. -- Russel. Dr Russel Winder Partner Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 41 Buckmaster Road, f: +44 8700 516 084 London SW11 1EN, UK. m: +44 7770 465 077 signature.asc Description: This is a digitally signed message part
[continuum] BUILD FAILURE: Commons - Commons Exec -
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=147203projectId=178 Build statistics: State: Failed Previous State: Ok Started at: Mon 23 Feb 2009 07:32:23 -0800 Finished at: Mon 23 Feb 2009 07:33:48 -0800 Total time: 1m 25s Build Trigger: Schedule Build Number: 77 Exit code: 1 Building machine hostname: vmbuild.apache.org Operating system : Linux(unknown) Java Home version : java version 1.6.0_05 Java(TM) SE Runtime Environment (build 1.6.0_05-b13) Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing) Builder version : Maven version: 2.0.9 Java version: 1.6.0_05 OS name: linux version: 2.6.20-16-server arch: i386 Family: unix SCM Changes: Changed: sebb @ Mon 23 Feb 2009 05:37:43 -0800 Comment: Update Javadoc. Fix local variable name typo. Files changed: /commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/environment/EnvironmentUtils.java ( 747013 ) Changed: sebb @ Mon 23 Feb 2009 05:38:34 -0800 Comment: Check that case is preserved for values, and that values are replaced Files changed: /commons/proper/exec/trunk/src/test/java/org/apache/commons/exec/environment/EnvironmentUtilTest.java ( 747014 ) Changed: sebb @ Mon 23 Feb 2009 05:47:04 -0800 Comment: Case-insensitive variables apply to all OSes Files changed: /commons/proper/exec/trunk/src/test/java/org/apache/commons/exec/environment/EnvironmentUtilTest.java ( 747018 ) Changed: sebb @ Mon 23 Feb 2009 06:24:45 -0800 Comment: No point creating Map if we're not going to use it. Files changed: /commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/util/MapUtils.java ( 747028 ) Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy Arguments: --batch-mode -DaltDeploymentRepository=vmbuild.repo::default::file://localhost/home/continuum/data/commons -Pci Build Fresh: false Always Build: false Default Build Definition: true Schedule: COMMONS_SCHEDULE Profile Name: JDK 6 Description: Test Summary: Tests: 68 Failures: 1 Total time: 65.504 Test Failures: EnvironmentUtilTest testCaseInsensitiveVariableLookup : junit.framework.AssertionFailedError junit.framework.AssertionFailedError: expected:bAr but was:null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:282) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:71) at org.apache.commons.exec.environment.EnvironmentUtilTest.testCaseInsensitiveVariableLookup(EnvironmentUtilTest.java:102) - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [general] Tracking Contributors in the POM
On 2009-02-21, Henri Yandell flame...@gmail.com wrote: On Fri, Feb 20, 2009 at 8:27 AM, Stefan Bodewig bode...@apache.org wrote: On 2009-02-20, Torsten Curdt tcu...@apache.org wrote: If somebody provides a patch in JIRA and we commit it, do we automatically add the submitter as a contributor to the POM (in Ant-land we'd do so, well, not inside the POM, of course)? Not sure there is a policy. Thought so. Yep. Personally I add people when it's a new feature or notable enhancement, but not for bugfixes. Loosely speaking. I've usually added contributors only if it's more than just 1-2 patches. Of course I name them in the commit. This means my own gut feelings are in line with existing practice, good 8-) The JIRA contribution report (sales pitch! :) ) can help here. That sales pitch worked. Can I see it in action anywhere? Those statements really downplay the importance of very few individuals to the original code. I feel a bit uncomfortable hiding their names behind contributors of Ant. We should just sign everything The Commons :) Well, maybe. POMs encourage listing of individuals and in my experience this can be a good thing - attracting new contributors. Once you are a recognized part of The Commons, seeing your name becomes less important. I'll let this issue (listing the original contributors of ant's code to compress) sit for now. Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[continuum] BUILD SUCCESSFUL: Commons - Commons Exec -
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=147250projectId=178 Build statistics: State: Ok Previous State: Failed Started at: Mon 23 Feb 2009 09:32:28 -0800 Finished at: Mon 23 Feb 2009 09:33:32 -0800 Total time: 1m 3s Build Trigger: Schedule Build Number: 78 Exit code: 0 Building machine hostname: vmbuild.apache.org Operating system : Linux(unknown) Java Home version : java version 1.6.0_05 Java(TM) SE Runtime Environment (build 1.6.0_05-b13) Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing) Builder version : Maven version: 2.0.9 Java version: 1.6.0_05 OS name: linux version: 2.6.20-16-server arch: i386 Family: unix SCM Changes: Changed: sebb @ Mon 23 Feb 2009 07:32:40 -0800 Comment: Make private static field final for better thread safety Files changed: /commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/environment/EnvironmentUtils.java ( 747049 ) Changed: sebb @ Mon 23 Feb 2009 07:33:45 -0800 Comment: Make private field final for better thread safety Files changed: /commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/launcher/CommandLauncherProxy.java ( 747051 ) Changed: sebb @ Mon 23 Feb 2009 07:50:05 -0800 Comment: Other accesses to watch and process are synchronized Make private field final Files changed: /commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/ExecuteWatchdog.java ( 747054 ) Changed: sebb @ Mon 23 Feb 2009 08:03:17 -0800 Comment: Make private variables final where possible Files changed: /commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/CommandLine.java ( 747056 ) /commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/DefaultExecutor.java ( 747056 ) /commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/ExecuteException.java ( 747056 ) /commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/LogOutputStream.java ( 747056 ) /commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/PumpStreamHandler.java ( 747056 ) /commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/StreamPumper.java ( 747056 ) /commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/Watchdog.java ( 747056 ) Changed: sebb @ Mon 23 Feb 2009 08:09:54 -0800 Comment: Duh - only run case-insensitive key lookup on Windows Files changed: /commons/proper/exec/trunk/src/test/java/org/apache/commons/exec/environment/EnvironmentUtilTest.java ( 747060 ) Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy Arguments: --batch-mode -DaltDeploymentRepository=vmbuild.repo::default::file://localhost/home/continuum/data/commons -Pci Build Fresh: false Always Build: false Default Build Definition: true Schedule: COMMONS_SCHEDULE Profile Name: JDK 6 Description: Test Summary: Tests: 68 Failures: 0 Total time: 42.468002 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: svn commit: r747161 - /commons/proper/exec/trunk/src/changes/changes.xml
On 23/02/2009, sgoes...@apache.org sgoes...@apache.org wrote: Author: sgoeschl Date: Mon Feb 23 22:09:44 2009 New Revision: 747161 URL: http://svn.apache.org/viewvc?rev=747161view=rev Log: Fixed broken changes.xml - typo ... Modified: commons/proper/exec/trunk/src/changes/changes.xml Modified: commons/proper/exec/trunk/src/changes/changes.xml URL: http://svn.apache.org/viewvc/commons/proper/exec/trunk/src/changes/changes.xml?rev=747161r1=747160r2=747161view=diff == --- commons/proper/exec/trunk/src/changes/changes.xml (original) +++ commons/proper/exec/trunk/src/changes/changes.xml Mon Feb 23 22:09:44 2009 @@ -24,7 +24,7 @@ /properties body release version=1.0.0 date=As in SVN description=Sandbox release Is the description - Sandbox release - correct? - action dev=sgoeschl type=fix due-to=Sebastien Bazleyissue=EXEC-37 + action dev=sgoeschl type=fix due-to=Sebastien Bazley issue=EXEC-37 Removed useless synchronized statement in OpenVmsProcessingEnvironment.createProcEnvironment /action - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: svn commit: r747161 - /commons/proper/exec/trunk/src/changes/changes.xml
No sebb wrote: On 23/02/2009, sgoes...@apache.org sgoes...@apache.org wrote: Author: sgoeschl Date: Mon Feb 23 22:09:44 2009 New Revision: 747161 URL: http://svn.apache.org/viewvc?rev=747161view=rev Log: Fixed broken changes.xml - typo ... Modified: commons/proper/exec/trunk/src/changes/changes.xml Modified: commons/proper/exec/trunk/src/changes/changes.xml URL: http://svn.apache.org/viewvc/commons/proper/exec/trunk/src/changes/changes.xml?rev=747161r1=747160r2=747161view=diff == --- commons/proper/exec/trunk/src/changes/changes.xml (original) +++ commons/proper/exec/trunk/src/changes/changes.xml Mon Feb 23 22:09:44 2009 @@ -24,7 +24,7 @@ /properties body release version=1.0.0 date=As in SVN description=Sandbox release Is the description - Sandbox release - correct? - action dev=sgoeschl type=fix due-to=Sebastien Bazleyissue=EXEC-37 + action dev=sgoeschl type=fix due-to=Sebastien Bazley issue=EXEC-37 Removed useless synchronized statement in OpenVmsProcessingEnvironment.createProcEnvironment /action - 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: r747195 - /commons/proper/exec/tags/EXEC_1_0_0/
On 23/02/2009, sgoes...@apache.org sgoes...@apache.org wrote: Author: sgoeschl Date: Mon Feb 23 23:21:25 2009 New Revision: 747195 URL: http://svn.apache.org/viewvc?rev=747195view=rev Log: Preparing next release candidate ... Removed: commons/proper/exec/tags/EXEC_1_0_0/ May I suggest using RCn for release candidate tags? - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [general] Tracking Contributors in the POM
On Mon, Feb 23, 2009 at 8:27 AM, Stefan Bodewig bode...@apache.org wrote: On 2009-02-21, Henri Yandell flame...@gmail.com wrote: The JIRA contribution report (sales pitch! :) ) can help here. That sales pitch worked. Can I see it in action anywhere? Go to a project page on the Apache JIRA, click on Contribution Report and choose your version. For example: http://issues.apache.org/jira/secure/ConfigureReport.jspa?versionId=12312139issueStatus=allselectedProjectId=12310470reportKey=com.sourcelabs.jira.plugin.report.contributions%3AcontributionreportNext=Next It shows us that Julien Aymé did a lot of work towards that release. Hen - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [general] Tracking Contributors in the POM
On 2009-02-24, Henri Yandell flame...@gmail.com wrote: On Mon, Feb 23, 2009 at 8:27 AM, Stefan Bodewig bode...@apache.org wrote: On 2009-02-21, Henri Yandell flame...@gmail.com wrote: The JIRA contribution report (sales pitch! :) ) can help here. That sales pitch worked. Can I see it in action anywhere? Go to a project page on the Apache JIRA, click on Contribution Report and choose your version. Ah, now I see it. Thanks Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [g...@vmgump]: Project commons-vfs (in module apache-commons) failed
Nothing in commons vfs changed. What broke it? On Feb 23, 2009, at 2:24 AM, Gump wrote: 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-vfs has an issue affecting its community integration. This issue affects 29 projects, and has been outstanding for 117 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - ant-contrib : Useful little Ant tasks - ant-contrib-test : Useful little Ant tasks - antbook-diary-core : Examples to go with Java Development with Ant - antbook-sections : Examples to go with Java Development with Ant - cddlm : Configuration and Deployment of Grid Applications and System... - commons-vfs : Apache Commons - commons-vfs-sandbox : Apache Commons - excalibur-fortress-bean : Repository of reusable components. - excalibur-fortress-container-impl : Repository of reusable components. - excalibur-fortress-container-test : Repository of reusable components. - excalibur-fortress-examples : Repository of reusable components. - excalibur-fortress-migration : Repository of reusable components. - excalibur-fortress-platform : Repository of reusable components. - excalibur-fortress-testcase : Repository of reusable components. - excalibur-monitor : Repository of reusable components. - excalibur-sourceresolve : Repository of reusable components. - excalibur-xmlutil : Repository of reusable components. - invicta : Open-source build management tool. - ivy : Ivy Core - ivy-tests : Ivy is a tool for managing (recording, tracking, resolving a... - logging-log4cxx-ant : Apache log4cxx - logging-log4cxx-ant-no_wchar_t : Apache log4cxx - logging-log4cxx-ant-static : Apache log4cxx - smartfrog : Smartfrog: Application Deployment from HP Laboratories - smartfrog-components : Smartfrog: Application Deployment from HP Laboratories - smartfrog-tasks : Smartfrog: Application Deployment from HP Laboratories - smartfrog-tasks-test : Smartfrog: Application Deployment from HP Laboratories - smartfrog-test : Smartfrog: Application Deployment from HP Laboratories - smartfrog-testharness : Smartfrog: Application Deployment from HP Laboratories Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-vfs/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-vfs-2.0-SNAPSHOT.jar] identifier set to project name -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/ workspace/apache-commons/vfs/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/vfs/ pom.xml -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-vfs/gump_work/build_apache-commons_commons-vfs.html Work Name: build_apache-commons_commons-vfs (Type: Build) Work ended in a state of : Failed Elapsed: 2 mins 31 secs Command Line: mvn --batch-mode --settings /srv/gump/public/workspace/ apache-commons/vfs/gump_mvn_settings.xml package [Working Directory: /srv/gump/public/workspace/apache-commons/vfs] CLASSPATH: /usr/lib/jvm/java-6-sun/lib/tools.jar:/srv/gump/public/ workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/ dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant- apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant- apache-xalan2.jar:/srv/gump/public/workspace/ant/dist/lib/ant- trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/ gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/ workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/ dist/lib/ant.jar:/srv/gump/public/workspace/junit/dist/ junit-23022009.jar:/srv/gump/public/workspace/xml-commons/java/ external/build/xml-apis-ext.jar:/srv/gump/public/workspace/apache- commons/logging/target/commons-logging-23022009.jar:/srv/gump/public/ workspace/apache-commons/logging/target/commons-logging- api-23022009.jar:/srv/gump/public/workspace/apache-commons/ collections/build/commons-collections-23022009.jar:/srv/gump/public/ workspace/httpcomponent s/2.0.2/commons-httpclient-2.0.2.jar:/srv/gump/public/workspace/ apache-commons/net/dist/commons-net-23022009.jar:/srv/gump/packages/ jcifs/jcifs-0.8.1.jar:/srv/gump/packages/jsch/jsch-0.1.38.jar - skipping testManualCache because TarFileSystem does not have capability CREATE skipping testOnResolveCache because TarFileSystem does not have
[MATH] Current stage of the commons-math.linear package
Hello All, I am interested in the develoment of the linear algebra subpackage of the commons-math project. Can someone give me infomation on the current state of the package and the TODO lists, plannings for the near future? Thanks in advance!