Re: [parent-pom] versions
On 4/1/07, Torsten Curdt [EMAIL PROTECTED] wrote: I've noticed that the plugin versions are not specified in the commons parent pom. From my experience this is a *really* bad idea as maven then picks the most recent from local repository. Which again can easily lead to inconsistent site builds across the team. So if no one objects I will add the latest version information to the plugins. For a reproducible site build. Personally I think we should only have the plugins defined if the release jar itself needs them for stability. Otherwise we just deal with whatever pain Maven is throwing everyone's way and yell at them to fix. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [parent-pom] versions
Henri Yandell wrote: Personally I think we should only have the plugins defined if the release jar itself needs them for stability. Otherwise we just deal with whatever pain Maven is throwing everyone's way and yell at them to fix. Er why? It is not our job to be gump and test commons builds against the latest random collection of maven plugins. rant If anyone looks objectively at the amount of time spent on maven on this mailing list over the past few years its incredible. I'd suggest its been a big distraction from actually coding for some people. The basic problem in this case is that maven builds aren't repeatable. They are only repeatable if you have exactly the same version of maven and each one of its many plugins. This isn't something that plagues ant - there if you write a build script it keeps on working - its called backwards compatibility. /rant Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (VFS-120) SFTP-Exception: com.jcraft.jsch.JSchException: session is down if the SFTP-Server was killed and restarted (a normal shutdown of the SFTP-Server occured no Exception afte
[
https://issues.apache.org/jira/browse/VFS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485958
]
Harald Brabenetz commented on VFS-120:
--
I found a Workaround:
I don't use the VFS.getManager(). Instead i create my own
StandardFileSystemManager and close it inside a finally clause:
--
StandardFileSystemManager manager = new StandardFileSystemManager();
manager.init();
try {
. //do something
} finally {
manager.close();
manager = null;
}
--
So, I always have a new Session.
Is this a correct solution, or are there maybe side-effects?
SFTP-Exception: com.jcraft.jsch.JSchException: session is down if the
SFTP-Server was killed and restarted (a normal shutdown of the SFTP-Server
occured no Exception after restart.)
---
Key: VFS-120
URL: https://issues.apache.org/jira/browse/VFS-120
Project: Commons VFS
Issue Type: Bug
Affects Versions: 1.0
Environment: Tomcat 5.5
JDK 6.0 (build with JDK 5)
commons-vfs-1.0.jar:
Specification-Title: Commons VFS
Implementation-Version: 1.0
JSCH: jsch-0.1.31.jar
Reporter: Harald Brabenetz
Priority: Critical
The error occured after restarting if the SFTP-Server was KILLed!!.
With a normal shutdown of the SFTP-Server, no exception after restarting
occured.
I found no function to force the reset of the session in SftpFileSystem.java
There is a function:
DefaultFileSystemManager manager =
(DefaultFileSystemManager)VFS.getManager();
manager.freeUnusedResources();
But this works only if AbstractFileSystem.isReleaseable() returns true.
And this this function return only true if all SFTP-FileObject are removed
from the GarbageCollection (finally()-Methode).
I cannot force a GarbageCollection.
So there is no way to handle this Error! I must restart the VM
(ServletContainer).
org.apache.commons.vfs.FileSystemException: Could not copy
file:///C:/TEMP/. to sftp://..;.
at
org.apache.commons.vfs.provider.AbstractFileObject.copyFrom(AbstractFileObject.java:902)
at
com.bearingpoint.orf.chat.core.service.ExportManagerImpl.exportChatMessages(Unknown
Source)
at
com.bearingpoint.orf.chat.core.service.ExportManagerImpl.startExportNow(Unknown
Source)
at
com.bearingpoint.orf.chat.core.service.ExportManagerImpl$ExportManagerRunnable.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.commons.vfs.FileSystemException: Could not write to
sftp://chat:[EMAIL PROTECTED]/home/chat/chatfile_12.zip.
at
org.apache.commons.vfs.provider.AbstractFileObject.getOutputStream(AbstractFileObject.java:1227)
at
org.apache.commons.vfs.provider.DefaultFileContent.getOutputStream(DefaultFileContent.java:373)
at
org.apache.commons.vfs.provider.DefaultFileContent.getOutputStream(DefaultFileContent.java:356)
at org.apache.commons.vfs.FileUtil.copyContent(FileUtil.java:100)
at
org.apache.commons.vfs.provider.AbstractFileObject.copyFrom(AbstractFileObject.java:893)
... 4 more
Caused by: org.apache.commons.vfs.FileSystemException: Could not connect to
SFTP server at sftp://chat:[EMAIL PROTECTED]/.
at
org.apache.commons.vfs.provider.sftp.SftpFileSystem.getChannel(SftpFileSystem.java:144)
at
org.apache.commons.vfs.provider.sftp.SftpFileObject.doGetOutputStream(SftpFileObject.java:402)
at
org.apache.commons.vfs.provider.AbstractFileObject.getOutputStream(AbstractFileObject.java:1219)
... 8 more
Caused by: com.jcraft.jsch.JSchException: session is down
at com.jcraft.jsch.Session.openChannel(Session.java:756)
at
org.apache.commons.vfs.provider.sftp.SftpFileSystem.getChannel(SftpFileSystem.java:122)
... 10 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [parent-pom] versions
On 02.04.2007, at 09:49, Stephen Colebourne wrote: Henri Yandell wrote: Personally I think we should only have the plugins defined if the release jar itself needs them for stability. ...and then have the project define the reports they want? Otherwise we just deal with whatever pain Maven is throwing everyone's way and yell at them to fix. Er why? It is not our job to be gump and test commons builds against the latest random collection of maven plugins. Don't get that either. I want to make our life's less painful. Specifying the versions helps a great deal with that. If anyone looks objectively at the amount of time spent on maven on this mailing list over the past few years its incredible. I'd suggest its been a big distraction from actually coding for some people. True The basic problem in this case is that maven builds aren't repeatable. They are only repeatable if you have exactly the same version of maven and each one of its many plugins. The good thing - you *can* achieve this. The bad thing - it's not the default. This isn't something that plagues ant - there if you write a build script it keeps on working - its called backwards compatibility. I have been bashing maven once I did the multi-project move for JCI ...but I am now more exposed to ant again and I have to say for small builds ant may be OK ...but for big builds it makes you cry. So I am again back to preferring maven over ant ...but we'll see how the JCI release will work out :) cheers -- Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (FILEUPLOAD-131) MultipartStream always assumes transfer encoding to be BINARY
[ https://issues.apache.org/jira/browse/FILEUPLOAD-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485970 ] Oleg Kalnichevski commented on FILEUPLOAD-131: -- Folks, I doubt HttpCore would be of any use here, as it does not (and is not supposed to) provide any content codecs. You probably may want to take a closer look at Commons Codec, which provides two content transfer codecs mentioned in RFC1521: quoted-printable and base64. Some efforts will have to spent on getting those codecs to work with I/O streams, though. Oleg MultipartStream always assumes transfer encoding to be BINARY - Key: FILEUPLOAD-131 URL: https://issues.apache.org/jira/browse/FILEUPLOAD-131 Project: Commons FileUpload Issue Type: Bug Environment: N/A Reporter: Walco van Loon MultipartStream always assumes transfer encoding to be BINARY and does not handle 'Content-Transfer-Encoding' header at all. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [parent-pom] versions
On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote: On 02.04.2007, at 09:49, Stephen Colebourne wrote: Henri Yandell wrote: Personally I think we should only have the plugins defined if the release jar itself needs them for stability. ...and then have the project define the reports they want? Sorry - plugin versions. Or is that the problem now, you can't use a version that's tied to your Maven installation because said plugin is not a part of the core system? Otherwise we just deal with whatever pain Maven is throwing everyone's way and yell at them to fix. Er why? It is not our job to be gump and test commons builds against the latest random collection of maven plugins. Don't get that either. I want to make our life's less painful. Specifying the versions helps a great deal with that. Maybe I'm being Maven1 minded. I don't think we should be wasting time figuring out which plugin version is good and which is bad for the many many plugins that are just there to stick crap on the site. Then again - it's in the central pom and not each project so not a biggy I guess. Go for it. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [parent-pom] versions
Torsten Curdt wrote on Sunday, April 01, 2007 2:17 PM: I've noticed that the plugin versions are not specified in the commons parent pom. From my experience this is a *really* bad idea as maven then picks the most recent from local repository. Which again can easily lead to inconsistent site builds across the team. So if no one objects I will add the latest version information to the plugins. For a reproducible site build. +1 I had once the situation, that a plugin was updated while I did a release shrug/. Therefore using fixed plugin versions are absolutely recommended. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (VFS-120) SFTP-Exception: com.jcraft.jsch.JSchException: session is down if the SFTP-Server was killed and restarted (a normal shutdown of the SFTP-Server occured no Exception afte
[ https://issues.apache.org/jira/browse/VFS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485984 ] Mario Ivankovits commented on VFS-120: -- As a workaround you can do it that way, as long as you do not use this manager instance as singleton I see no side-effects. Still, I (or we? :-) ) should try to fix it. Ciao, Mario SFTP-Exception: com.jcraft.jsch.JSchException: session is down if the SFTP-Server was killed and restarted (a normal shutdown of the SFTP-Server occured no Exception after restart.) --- Key: VFS-120 URL: https://issues.apache.org/jira/browse/VFS-120 Project: Commons VFS Issue Type: Bug Affects Versions: 1.0 Environment: Tomcat 5.5 JDK 6.0 (build with JDK 5) commons-vfs-1.0.jar: Specification-Title: Commons VFS Implementation-Version: 1.0 JSCH: jsch-0.1.31.jar Reporter: Harald Brabenetz Priority: Critical The error occured after restarting if the SFTP-Server was KILLed!!. With a normal shutdown of the SFTP-Server, no exception after restarting occured. I found no function to force the reset of the session in SftpFileSystem.java There is a function: DefaultFileSystemManager manager = (DefaultFileSystemManager)VFS.getManager(); manager.freeUnusedResources(); But this works only if AbstractFileSystem.isReleaseable() returns true. And this this function return only true if all SFTP-FileObject are removed from the GarbageCollection (finally()-Methode). I cannot force a GarbageCollection. So there is no way to handle this Error! I must restart the VM (ServletContainer). org.apache.commons.vfs.FileSystemException: Could not copy file:///C:/TEMP/. to sftp://..;. at org.apache.commons.vfs.provider.AbstractFileObject.copyFrom(AbstractFileObject.java:902) at com.bearingpoint.orf.chat.core.service.ExportManagerImpl.exportChatMessages(Unknown Source) at com.bearingpoint.orf.chat.core.service.ExportManagerImpl.startExportNow(Unknown Source) at com.bearingpoint.orf.chat.core.service.ExportManagerImpl$ExportManagerRunnable.run(Unknown Source) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.commons.vfs.FileSystemException: Could not write to sftp://chat:[EMAIL PROTECTED]/home/chat/chatfile_12.zip. at org.apache.commons.vfs.provider.AbstractFileObject.getOutputStream(AbstractFileObject.java:1227) at org.apache.commons.vfs.provider.DefaultFileContent.getOutputStream(DefaultFileContent.java:373) at org.apache.commons.vfs.provider.DefaultFileContent.getOutputStream(DefaultFileContent.java:356) at org.apache.commons.vfs.FileUtil.copyContent(FileUtil.java:100) at org.apache.commons.vfs.provider.AbstractFileObject.copyFrom(AbstractFileObject.java:893) ... 4 more Caused by: org.apache.commons.vfs.FileSystemException: Could not connect to SFTP server at sftp://chat:[EMAIL PROTECTED]/. at org.apache.commons.vfs.provider.sftp.SftpFileSystem.getChannel(SftpFileSystem.java:144) at org.apache.commons.vfs.provider.sftp.SftpFileObject.doGetOutputStream(SftpFileObject.java:402) at org.apache.commons.vfs.provider.AbstractFileObject.getOutputStream(AbstractFileObject.java:1219) ... 8 more Caused by: com.jcraft.jsch.JSchException: session is down at com.jcraft.jsch.Session.openChannel(Session.java:756) at org.apache.commons.vfs.provider.sftp.SftpFileSystem.getChannel(SftpFileSystem.java:122) ... 10 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-id (in module jakarta-commons-sandbox) 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 [EMAIL PROTECTED] Project commons-id has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-id : Commons Identifier Package Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-id-02042007.jar] identifier set to project name -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/jakarta-commons-sandbox/id/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/jakarta-commons-sandbox/id/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/jakarta-commons-sandbox/id/project.properties -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/gump_work/build_jakarta-commons-sandbox_commons-id.html Work Name: build_jakarta-commons-sandbox_commons-id (Type: Build) Work ended in a state of : Failed Elapsed: 38 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/jakarta-commons-sandbox/id] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-02042007.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/packages/maven-cobertura-plugin/maven-cobertura-plugin-1.1.jar:/usr/local/gump/packages/maven-xdoc-plugin/maven-xdoc-plugin-1.9.2.jar - [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.536 sec [junit] Running org.apache.commons.id.serial.PrefixedLeftPaddedNumericGeneratorTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.505 sec [junit] Running org.apache.commons.id.serial.TimeBasedAlphanumericIdentifierGeneratorTest [junit] Tests run: 12, Failures: 1, Errors: 0, Time elapsed: 0.932 sec [junit] [ERROR] TEST org.apache.commons.id.serial.TimeBasedAlphanumericIdentifierGeneratorTest FAILED [junit] Running org.apache.commons.id.serial.AlphanumericGeneratorTest [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0.579 sec [junit] Running org.apache.commons.id.serial.LongGeneratorTest [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.531 sec [junit] Running org.apache.commons.id.serial.NumericGeneratorTest [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.569 sec [junit] Running org.apache.commons.id.uuid.state.StateHelperTest [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.666 sec [junit] Running org.apache.commons.id.uuid.state.NodeTest [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.7 sec [junit] Running org.apache.commons.id.uuid.state.InMemoryStateImplTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.664 sec [junit] Running org.apache.commons.id.uuid.state.ReadOnlyResourceStateImplTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.855 sec [junit] Running org.apache.commons.id.uuid.state.ReadWriteFileStateImplTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.767 sec [junit] Running org.apache.commons.id.uuid.clock.SystemClockImplTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.531 sec [junit] Running org.apache.commons.id.uuid.clock.ThreadClockImplTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.528 sec [junit] Running org.apache.commons.id.uuid.NodeManagerImplTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.758 sec [junit] Running org.apache.commons.id.uuid.UUIDTest [junit] Tests run: 17, Failures: 0, Errors: 0, Time elapsed: 0.573 sec [junit] Running
[EMAIL PROTECTED]: Project commons-id (in module jakarta-commons-sandbox) 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 [EMAIL PROTECTED] Project commons-id has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-id : Commons Identifier Package Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-id-02042007.jar] identifier set to project name -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/jakarta-commons-sandbox/id/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/jakarta-commons-sandbox/id/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/jakarta-commons-sandbox/id/project.properties -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-id/gump_work/build_jakarta-commons-sandbox_commons-id.html Work Name: build_jakarta-commons-sandbox_commons-id (Type: Build) Work ended in a state of : Failed Elapsed: 38 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/jakarta-commons-sandbox/id] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-02042007.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/packages/maven-cobertura-plugin/maven-cobertura-plugin-1.1.jar:/usr/local/gump/packages/maven-xdoc-plugin/maven-xdoc-plugin-1.9.2.jar - [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.536 sec [junit] Running org.apache.commons.id.serial.PrefixedLeftPaddedNumericGeneratorTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.505 sec [junit] Running org.apache.commons.id.serial.TimeBasedAlphanumericIdentifierGeneratorTest [junit] Tests run: 12, Failures: 1, Errors: 0, Time elapsed: 0.932 sec [junit] [ERROR] TEST org.apache.commons.id.serial.TimeBasedAlphanumericIdentifierGeneratorTest FAILED [junit] Running org.apache.commons.id.serial.AlphanumericGeneratorTest [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0.579 sec [junit] Running org.apache.commons.id.serial.LongGeneratorTest [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.531 sec [junit] Running org.apache.commons.id.serial.NumericGeneratorTest [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.569 sec [junit] Running org.apache.commons.id.uuid.state.StateHelperTest [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.666 sec [junit] Running org.apache.commons.id.uuid.state.NodeTest [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.7 sec [junit] Running org.apache.commons.id.uuid.state.InMemoryStateImplTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.664 sec [junit] Running org.apache.commons.id.uuid.state.ReadOnlyResourceStateImplTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.855 sec [junit] Running org.apache.commons.id.uuid.state.ReadWriteFileStateImplTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.767 sec [junit] Running org.apache.commons.id.uuid.clock.SystemClockImplTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.531 sec [junit] Running org.apache.commons.id.uuid.clock.ThreadClockImplTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.528 sec [junit] Running org.apache.commons.id.uuid.NodeManagerImplTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.758 sec [junit] Running org.apache.commons.id.uuid.UUIDTest [junit] Tests run: 17, Failures: 0, Errors: 0, Time elapsed: 0.573 sec [junit] Running
[jira] Commented: (VFS-120) SFTP-Exception: com.jcraft.jsch.JSchException: session is down if the SFTP-Server was killed and restarted (a normal shutdown of the SFTP-Server occured no Exception afte
[
https://issues.apache.org/jira/browse/VFS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485992
]
Harald Brabenetz commented on VFS-120:
--
I'm happy about the Workaround. It makes also a clean connection.open()
connection.close() on the SFTP-Server-Side.
But for general use and worst case of Exceptions there should be a
reinitialization of the JSCH-Session like the following (see also
SftpFileSystem-patch.txt):
if (session is down.equals(e.getMessage())){
//reinitialize the Session. The next execution should work.
doCloseCommunicationLink();
}
So the Exception should occured only one time after killing and restart the
SFTP-Server.
But I have not tested it
SFTP-Exception: com.jcraft.jsch.JSchException: session is down if the
SFTP-Server was killed and restarted (a normal shutdown of the SFTP-Server
occured no Exception after restart.)
---
Key: VFS-120
URL: https://issues.apache.org/jira/browse/VFS-120
Project: Commons VFS
Issue Type: Bug
Affects Versions: 1.0
Environment: Tomcat 5.5
JDK 6.0 (build with JDK 5)
commons-vfs-1.0.jar:
Specification-Title: Commons VFS
Implementation-Version: 1.0
JSCH: jsch-0.1.31.jar
Reporter: Harald Brabenetz
Priority: Critical
Attachments: SftpFileSystem-patch.txt
The error occured after restarting if the SFTP-Server was KILLed!!.
With a normal shutdown of the SFTP-Server, no exception after restarting
occured.
I found no function to force the reset of the session in SftpFileSystem.java
There is a function:
DefaultFileSystemManager manager =
(DefaultFileSystemManager)VFS.getManager();
manager.freeUnusedResources();
But this works only if AbstractFileSystem.isReleaseable() returns true.
And this this function return only true if all SFTP-FileObject are removed
from the GarbageCollection (finally()-Methode).
I cannot force a GarbageCollection.
So there is no way to handle this Error! I must restart the VM
(ServletContainer).
org.apache.commons.vfs.FileSystemException: Could not copy
file:///C:/TEMP/. to sftp://..;.
at
org.apache.commons.vfs.provider.AbstractFileObject.copyFrom(AbstractFileObject.java:902)
at
com.bearingpoint.orf.chat.core.service.ExportManagerImpl.exportChatMessages(Unknown
Source)
at
com.bearingpoint.orf.chat.core.service.ExportManagerImpl.startExportNow(Unknown
Source)
at
com.bearingpoint.orf.chat.core.service.ExportManagerImpl$ExportManagerRunnable.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.commons.vfs.FileSystemException: Could not write to
sftp://chat:[EMAIL PROTECTED]/home/chat/chatfile_12.zip.
at
org.apache.commons.vfs.provider.AbstractFileObject.getOutputStream(AbstractFileObject.java:1227)
at
org.apache.commons.vfs.provider.DefaultFileContent.getOutputStream(DefaultFileContent.java:373)
at
org.apache.commons.vfs.provider.DefaultFileContent.getOutputStream(DefaultFileContent.java:356)
at org.apache.commons.vfs.FileUtil.copyContent(FileUtil.java:100)
at
org.apache.commons.vfs.provider.AbstractFileObject.copyFrom(AbstractFileObject.java:893)
... 4 more
Caused by: org.apache.commons.vfs.FileSystemException: Could not connect to
SFTP server at sftp://chat:[EMAIL PROTECTED]/.
at
org.apache.commons.vfs.provider.sftp.SftpFileSystem.getChannel(SftpFileSystem.java:144)
at
org.apache.commons.vfs.provider.sftp.SftpFileObject.doGetOutputStream(SftpFileObject.java:402)
at
org.apache.commons.vfs.provider.AbstractFileObject.getOutputStream(AbstractFileObject.java:1219)
... 8 more
Caused by: com.jcraft.jsch.JSchException: session is down
at com.jcraft.jsch.Session.openChannel(Session.java:756)
at
org.apache.commons.vfs.provider.sftp.SftpFileSystem.getChannel(SftpFileSystem.java:122)
... 10 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (VFS-120) SFTP-Exception: com.jcraft.jsch.JSchException: session is down if the SFTP-Server was killed and restarted (a normal shutdown of the SFTP-Server occured no Exception after
[ https://issues.apache.org/jira/browse/VFS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harald Brabenetz updated VFS-120: - Attachment: SftpFileSystem-patch.txt see last comment SFTP-Exception: com.jcraft.jsch.JSchException: session is down if the SFTP-Server was killed and restarted (a normal shutdown of the SFTP-Server occured no Exception after restart.) --- Key: VFS-120 URL: https://issues.apache.org/jira/browse/VFS-120 Project: Commons VFS Issue Type: Bug Affects Versions: 1.0 Environment: Tomcat 5.5 JDK 6.0 (build with JDK 5) commons-vfs-1.0.jar: Specification-Title: Commons VFS Implementation-Version: 1.0 JSCH: jsch-0.1.31.jar Reporter: Harald Brabenetz Priority: Critical Attachments: SftpFileSystem-patch.txt The error occured after restarting if the SFTP-Server was KILLed!!. With a normal shutdown of the SFTP-Server, no exception after restarting occured. I found no function to force the reset of the session in SftpFileSystem.java There is a function: DefaultFileSystemManager manager = (DefaultFileSystemManager)VFS.getManager(); manager.freeUnusedResources(); But this works only if AbstractFileSystem.isReleaseable() returns true. And this this function return only true if all SFTP-FileObject are removed from the GarbageCollection (finally()-Methode). I cannot force a GarbageCollection. So there is no way to handle this Error! I must restart the VM (ServletContainer). org.apache.commons.vfs.FileSystemException: Could not copy file:///C:/TEMP/. to sftp://..;. at org.apache.commons.vfs.provider.AbstractFileObject.copyFrom(AbstractFileObject.java:902) at com.bearingpoint.orf.chat.core.service.ExportManagerImpl.exportChatMessages(Unknown Source) at com.bearingpoint.orf.chat.core.service.ExportManagerImpl.startExportNow(Unknown Source) at com.bearingpoint.orf.chat.core.service.ExportManagerImpl$ExportManagerRunnable.run(Unknown Source) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.commons.vfs.FileSystemException: Could not write to sftp://chat:[EMAIL PROTECTED]/home/chat/chatfile_12.zip. at org.apache.commons.vfs.provider.AbstractFileObject.getOutputStream(AbstractFileObject.java:1227) at org.apache.commons.vfs.provider.DefaultFileContent.getOutputStream(DefaultFileContent.java:373) at org.apache.commons.vfs.provider.DefaultFileContent.getOutputStream(DefaultFileContent.java:356) at org.apache.commons.vfs.FileUtil.copyContent(FileUtil.java:100) at org.apache.commons.vfs.provider.AbstractFileObject.copyFrom(AbstractFileObject.java:893) ... 4 more Caused by: org.apache.commons.vfs.FileSystemException: Could not connect to SFTP server at sftp://chat:[EMAIL PROTECTED]/. at org.apache.commons.vfs.provider.sftp.SftpFileSystem.getChannel(SftpFileSystem.java:144) at org.apache.commons.vfs.provider.sftp.SftpFileObject.doGetOutputStream(SftpFileObject.java:402) at org.apache.commons.vfs.provider.AbstractFileObject.getOutputStream(AbstractFileObject.java:1219) ... 8 more Caused by: com.jcraft.jsch.JSchException: session is down at com.jcraft.jsch.Session.openChannel(Session.java:756) at org.apache.commons.vfs.provider.sftp.SftpFileSystem.getChannel(SftpFileSystem.java:122) ... 10 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] jci out of sandbox
Torsten Curdt tcurdt at apache.org writes: As already announced I would like to move http://jakarta.apache.org/commons/sandbox/jci/ out of the sandbox so I can then prepare a first RC. Please cast your votes for the graduation! Despite the result already posted: +1 Joerg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (BEANUTILS-274) BeanUtils cannot set property of type Long with value of Double
BeanUtils cannot set property of type Long with value of Double
---
Key: BEANUTILS-274
URL: https://issues.apache.org/jira/browse/BEANUTILS-274
Project: Commons BeanUtils
Issue Type: Bug
Components: Bean / Property Utils, ConvertUtils Converters
Affects Versions: 1.7.0
Environment: Windows XP, JDK 1.6.0
Reporter: Xianmin Kwauk
I tried to set a field of type Long with a double value (e.g. 100.0) and I got
0.
In BeanUtilsBean, in the following code:
} else if (getConvertUtils().lookup(value.getClass()) != null) {
newValue = getConvertUtils().convert(value.toString(), type);
} else {
value.toString() is passed to LongConverter which would handle value (Double)
correctly but fails when a String (e.g. 100.0) is passed in. It seems
changing value.toString() to value should fix the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (BEANUTILS-273) Public methods overriden in anonymous or private subclasses are not recognized by PropertyUtils
[
https://issues.apache.org/jira/browse/BEANUTILS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Liberato updated BEANUTILS-273:
---
Fix Version/s: (was: 1.8.0)
Affects Version/s: 1.7.0
updating affects/fix versions
Public methods overriden in anonymous or private subclasses are not
recognized by PropertyUtils
---
Key: BEANUTILS-273
URL: https://issues.apache.org/jira/browse/BEANUTILS-273
Project: Commons BeanUtils
Issue Type: Bug
Components: Bean / Property Utils
Affects Versions: 1.7.0
Reporter: Marcelo Liberato
Attachments: anonymous-subclass-override-patch.txt
When you do something like:
TestBean anonymous = new TestBean() {
public String getStringProperty() {
return foo;
}
};
PropertyUtils.getProperty(anonymous, stringProperty);
PropertyUtils fails as:
java.lang.NoSuchMethodException: Property 'stringProperty' has no getter
method in class 'class org.apache.commons.beanutils.PropertyUtilsTestCase$1'
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) 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 [EMAIL PROTECTED] Project commons-jelly-tags-jsl-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 127 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jsl-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on ant exists, no need to add for property maven.jar.ant-optional. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build) Work ended in a state of : Failed Elapsed: 32 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-02042007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-02042007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar - [junit] at org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:64) [junit] at org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:59) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:263) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187) [junit] at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:66) [junit] at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:113) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187) [junit] at org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:161) [junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59) [junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80) [junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171) [junit]
[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) 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 [EMAIL PROTECTED] Project commons-jelly-tags-jsl-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 127 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jsl-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on ant exists, no need to add for property maven.jar.ant-optional. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build) Work ended in a state of : Failed Elapsed: 32 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-02042007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-02042007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar - [junit] at org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:64) [junit] at org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:59) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:263) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187) [junit] at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:66) [junit] at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:113) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187) [junit] at org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:161) [junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59) [junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80) [junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171) [junit]
[EMAIL PROTECTED]: Project commons-jelly-tags-fmt-test (in module commons-jelly) 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 [EMAIL PROTECTED] Project commons-jelly-tags-fmt-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 127 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-fmt-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/gump_work/build_commons-jelly_commons-jelly-tags-fmt-test.html Work Name: build_commons-jelly_commons-jelly-tags-fmt-test (Type: Build) Work ended in a state of : Failed Elapsed: 22 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-classpath-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-core-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-util-2.0b4.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/beanshell/target/commons-jelly-tags-beanshell-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-02042007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-02042007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/commons-jelly-tags-fmt-02042007.jar - [junit] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) [junit] at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) [junit] at java.net.URLClassLoader.access$100(URLClassLoader.java:56) [junit] at java.net.URLClassLoader$1.run(URLClassLoader.java:195) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:306) [junit] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:251) [junit] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) [junit] at org.apache.commons.jelly.tags.ant.AntTagLibrary.createProject(AntTagLibrary.java:128)
[EMAIL PROTECTED]: Project commons-jelly-tags-fmt-test (in module commons-jelly) 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 [EMAIL PROTECTED] Project commons-jelly-tags-fmt-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 127 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-fmt-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/gump_work/build_commons-jelly_commons-jelly-tags-fmt-test.html Work Name: build_commons-jelly_commons-jelly-tags-fmt-test (Type: Build) Work ended in a state of : Failed Elapsed: 22 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-classpath-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-core-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-util-2.0b4.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/beanshell/target/commons-jelly-tags-beanshell-02042007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-02042007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-02042007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-02042007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/commons-jelly-tags-fmt-02042007.jar - [junit] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) [junit] at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) [junit] at java.net.URLClassLoader.access$100(URLClassLoader.java:56) [junit] at java.net.URLClassLoader$1.run(URLClassLoader.java:195) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:306) [junit] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:251) [junit] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) [junit] at org.apache.commons.jelly.tags.ant.AntTagLibrary.createProject(AntTagLibrary.java:128)
[jira] Created: (VFS-121) Support of HTTP headers
Support of HTTP headers --- Key: VFS-121 URL: https://issues.apache.org/jira/browse/VFS-121 Project: Commons VFS Issue Type: Improvement Affects Versions: Nightly Builds Reporter: Philippe Poulard Priority: Blocker I've looked at the code of the HTTP provider, and I didn't find any mean to play with HTTP headers ; I think it should be in HttpFileSystemConfigBuilder this is important for content negociation : Accept, Accept-language, etc Applications that are dealing with content negociation are stalling ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r524915 - /jakarta/commons/proper/dbcp/tags/DBCP_1_2_2/
Author: psteitz Date: Mon Apr 2 13:39:33 2007 New Revision: 524915 URL: http://svn.apache.org/viewvc?view=revrev=524915 Log: tagging release (copied from RC3 tag). Added: jakarta/commons/proper/dbcp/tags/DBCP_1_2_2/ - copied from r522358, jakarta/commons/proper/dbcp/tags/DBCP_1_2_2_RC3/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [parent-pom] versions
Henri Yandell wrote: On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote: On 02.04.2007, at 09:49, Stephen Colebourne wrote: Henri Yandell wrote: Personally I think we should only have the plugins defined if the release jar itself needs them for stability. ...and then have the project define the reports they want? Sorry - plugin versions. Or is that the problem now, you can't use a version that's tied to your Maven installation because said plugin is not a part of the core system? Speaking of Maven 2 here. The Maven installation doesn't contain any plugins, they are downloaded when they are needed. Unless you specify the version of a plugin that you want to use, you get the latest version. This in turn is found in the metadata in the repository, from which the plugin is downloaded. Otherwise we just deal with whatever pain Maven is throwing everyone's way and yell at them to fix. Er why? It is not our job to be gump and test commons builds against the latest random collection of maven plugins. Don't get that either. I want to make our life's less painful. Specifying the versions helps a great deal with that. Maybe I'm being Maven1 minded. I don't think we should be wasting time figuring out which plugin version is good and which is bad for the many many plugins that are just there to stick crap on the site. Then again - it's in the central pom and not each project so not a biggy I guess. Go for it. Hen -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [parent-pom] versions
Torsten Curdt wrote: I've noticed that the plugin versions are not specified in the commons parent pom. From my experience this is a *really* bad idea as maven then picks the most recent from local repository. Which again can easily lead to inconsistent site builds across the team. So if no one objects I will add the latest version information to the plugins. For a reproducible site build. cheers -- Torsten +1 This is a good idea, and also a recommended practice. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r524951 - /jakarta/commons/proper/jci/trunk/pom.xml
Author: tcurdt Date: Mon Apr 2 15:27:41 2007 New Revision: 524951 URL: http://svn.apache.org/viewvc?view=revrev=524951 Log: enable the gpg plugin Modified: jakarta/commons/proper/jci/trunk/pom.xml Modified: jakarta/commons/proper/jci/trunk/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/pom.xml?view=diffrev=524951r1=524950r2=524951 == --- jakarta/commons/proper/jci/trunk/pom.xml (original) +++ jakarta/commons/proper/jci/trunk/pom.xml Mon Apr 2 15:27:41 2007 @@ -74,7 +74,6 @@ /scm build plugins -!-- plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-gpg-plugin/artifactId @@ -88,7 +87,6 @@ /execution /executions /plugin --- plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r524954 - in /jakarta/commons/proper/jci/trunk: ./ compilers/eclipse/ compilers/groovy/ compilers/janino/ compilers/javac/ compilers/jsr199/ compilers/rhino/ core/ examples/ fam/
Author: tcurdt Date: Mon Apr 2 15:31:22 2007 New Revision: 524954 URL: http://svn.apache.org/viewvc?view=revrev=524954 Log: ignore cobertura files Modified: jakarta/commons/proper/jci/trunk/ (props changed) jakarta/commons/proper/jci/trunk/compilers/eclipse/ (props changed) jakarta/commons/proper/jci/trunk/compilers/groovy/ (props changed) jakarta/commons/proper/jci/trunk/compilers/janino/ (props changed) jakarta/commons/proper/jci/trunk/compilers/javac/ (props changed) jakarta/commons/proper/jci/trunk/compilers/jsr199/ (props changed) jakarta/commons/proper/jci/trunk/compilers/rhino/ (props changed) jakarta/commons/proper/jci/trunk/core/ (props changed) jakarta/commons/proper/jci/trunk/examples/ (props changed) jakarta/commons/proper/jci/trunk/fam/ (props changed) Propchange: jakarta/commons/proper/jci/trunk/ -- --- svn:ignore (original) +++ svn:ignore Mon Apr 2 15:31:22 2007 @@ -1,9 +1,11 @@ -build.properties -dist +eclipse +target +*~ +*.log .classpath .project -.checkstyle -target -maven.log -velocity.log -eclipse_classes +.settings +*.ipr +*.iws +*.iml +*.ser Propchange: jakarta/commons/proper/jci/trunk/compilers/eclipse/ -- --- svn:ignore (original) +++ svn:ignore Mon Apr 2 15:31:22 2007 @@ -1,3 +1,4 @@ +eclipse target *~ *.log @@ -7,4 +8,4 @@ *.ipr *.iws *.iml - +*.ser Propchange: jakarta/commons/proper/jci/trunk/compilers/groovy/ -- --- svn:ignore (original) +++ svn:ignore Mon Apr 2 15:31:22 2007 @@ -1,3 +1,4 @@ +eclipse target *~ *.log @@ -7,4 +8,4 @@ *.ipr *.iws *.iml - +*.ser Propchange: jakarta/commons/proper/jci/trunk/compilers/janino/ -- --- svn:ignore (original) +++ svn:ignore Mon Apr 2 15:31:22 2007 @@ -1,3 +1,4 @@ +eclipse target *~ *.log @@ -7,4 +8,4 @@ *.ipr *.iws *.iml - +*.ser Propchange: jakarta/commons/proper/jci/trunk/compilers/javac/ -- --- svn:ignore (original) +++ svn:ignore Mon Apr 2 15:31:22 2007 @@ -1,3 +1,4 @@ +eclipse target *~ *.log @@ -7,4 +8,4 @@ *.ipr *.iws *.iml - +*.ser Propchange: jakarta/commons/proper/jci/trunk/compilers/jsr199/ -- --- svn:ignore (original) +++ svn:ignore Mon Apr 2 15:31:22 2007 @@ -1,3 +1,4 @@ +eclipse target *~ *.log @@ -7,4 +8,4 @@ *.ipr *.iws *.iml - +*.ser Propchange: jakarta/commons/proper/jci/trunk/compilers/rhino/ -- --- svn:ignore (original) +++ svn:ignore Mon Apr 2 15:31:22 2007 @@ -1,3 +1,4 @@ +eclipse target *~ *.log @@ -7,4 +8,4 @@ *.ipr *.iws *.iml - +*.ser Propchange: jakarta/commons/proper/jci/trunk/core/ -- --- svn:ignore (original) +++ svn:ignore Mon Apr 2 15:31:22 2007 @@ -1,3 +1,4 @@ +eclipse target *~ *.log @@ -7,4 +8,4 @@ *.ipr *.iws *.iml - +*.ser Propchange: jakarta/commons/proper/jci/trunk/examples/ -- --- svn:ignore (original) +++ svn:ignore Mon Apr 2 15:31:22 2007 @@ -1,3 +1,4 @@ +eclipse target *~ *.log @@ -7,4 +8,4 @@ *.ipr *.iws *.iml - +*.ser Propchange: jakarta/commons/proper/jci/trunk/fam/ -- --- svn:ignore (original) +++ svn:ignore Mon Apr 2 15:31:22 2007 @@ -1,3 +1,4 @@ +eclipse target *~ *.log @@ -7,4 +8,4 @@ *.ipr *.iws *.iml - +*.ser - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[all] docs on doing maven2 releases
Guys, Do we already have docs on how to do commmons releases with maven2 somewhere? cheers -- Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r524960 - /jakarta/commons/proper/jci/trunk/pom.xml
Author: tcurdt Date: Mon Apr 2 16:00:30 2007 New Revision: 524960 URL: http://svn.apache.org/viewvc?view=revrev=524960 Log: use gpg plugin from parent, define some properties for the parent pom Modified: jakarta/commons/proper/jci/trunk/pom.xml Modified: jakarta/commons/proper/jci/trunk/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/pom.xml?view=diffrev=524960r1=524959r2=524960 == --- jakarta/commons/proper/jci/trunk/pom.xml (original) +++ jakarta/commons/proper/jci/trunk/pom.xml Mon Apr 2 16:00:30 2007 @@ -31,11 +31,6 @@ moduleexamples/module /modules distributionManagement -snapshotRepository -idapache-maven-snapshot/id -namerepository/name - urlscpexe://scpexe://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository//url -/snapshotRepository site idwebsite/id urlscpexe://people.apache.org/www/jakarta.apache.org/commons/jci//url @@ -76,19 +71,6 @@ plugins plugin groupIdorg.apache.maven.plugins/groupId -artifactIdmaven-gpg-plugin/artifactId -executions -execution -idsign-artifacts/id -phaseverify/phase -goals -goalsign/goal -/goals -/execution -/executions -/plugin -plugin -groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.3/version configuration @@ -111,8 +93,7 @@ /goals /execution /executions -/plugin - +/plugin /plugins extensions extension @@ -200,4 +181,10 @@ /plugin /plugins /reporting + +properties +maven.compile.source1.4/maven.compile.source +maven.compile.target1.4/maven.compile.target +commons.deployment.protocolscpexe/commons.deployment.protocol +/properties /project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r524961 - in /jakarta/commons/proper/jci/trunk: compilers/eclipse/pom.xml compilers/groovy/pom.xml compilers/janino/pom.xml compilers/javac/pom.xml compilers/rhino/pom.xml core/pom.xml exa
Author: tcurdt Date: Mon Apr 2 16:10:58 2007 New Revision: 524961 URL: http://svn.apache.org/viewvc?view=revrev=524961 Log: [maven-release-plugin] prepare release 1.0-RC1 Modified: jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml jakarta/commons/proper/jci/trunk/compilers/groovy/pom.xml jakarta/commons/proper/jci/trunk/compilers/janino/pom.xml jakarta/commons/proper/jci/trunk/compilers/javac/pom.xml jakarta/commons/proper/jci/trunk/compilers/rhino/pom.xml jakarta/commons/proper/jci/trunk/core/pom.xml jakarta/commons/proper/jci/trunk/examples/pom.xml jakarta/commons/proper/jci/trunk/fam/pom.xml jakarta/commons/proper/jci/trunk/pom.xml Modified: jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml?view=diffrev=524961r1=524960r2=524961 == --- jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml (original) +++ jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml Mon Apr 2 16:10:58 2007 @@ -4,17 +4,17 @@ parent groupIdorg.apache.commons/groupId artifactIdcommons-jci/artifactId -version1.0-SNAPSHOT/version +version1.0-RC1/version /parent packagingjar/packaging artifactIdcommons-jci-eclipse/artifactId -version1.0-SNAPSHOT/version +version1.0-RC1/version namecompiler-eclipse/name dependencies dependency groupIdorg.apache.commons/groupId artifactIdcommons-jci-core/artifactId -version1.0-SNAPSHOT/version +version1.0-RC1/version /dependency dependency groupIdorg.apache.commons/groupId Modified: jakarta/commons/proper/jci/trunk/compilers/groovy/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/compilers/groovy/pom.xml?view=diffrev=524961r1=524960r2=524961 == --- jakarta/commons/proper/jci/trunk/compilers/groovy/pom.xml (original) +++ jakarta/commons/proper/jci/trunk/compilers/groovy/pom.xml Mon Apr 2 16:10:58 2007 @@ -4,17 +4,17 @@ parent groupIdorg.apache.commons/groupId artifactIdcommons-jci/artifactId -version1.0-SNAPSHOT/version +version1.0-RC1/version /parent packagingjar/packaging artifactIdcommons-jci-groovy/artifactId -version1.0-SNAPSHOT/version +version1.0-RC1/version namecompiler-groovy/name dependencies dependency groupIdorg.apache.commons/groupId artifactIdcommons-jci-core/artifactId -version1.0-SNAPSHOT/version +version1.0-RC1/version /dependency dependency groupIdorg.apache.commons/groupId Modified: jakarta/commons/proper/jci/trunk/compilers/janino/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/compilers/janino/pom.xml?view=diffrev=524961r1=524960r2=524961 == --- jakarta/commons/proper/jci/trunk/compilers/janino/pom.xml (original) +++ jakarta/commons/proper/jci/trunk/compilers/janino/pom.xml Mon Apr 2 16:10:58 2007 @@ -4,17 +4,17 @@ parent groupIdorg.apache.commons/groupId artifactIdcommons-jci/artifactId -version1.0-SNAPSHOT/version +version1.0-RC1/version /parent packagingjar/packaging artifactIdcommons-jci-janino/artifactId -version1.0-SNAPSHOT/version +version1.0-RC1/version namecompiler-janino/name dependencies dependency groupIdorg.apache.commons/groupId artifactIdcommons-jci-core/artifactId -version1.0-SNAPSHOT/version +version1.0-RC1/version /dependency dependency groupIdorg.apache.commons/groupId Modified: jakarta/commons/proper/jci/trunk/compilers/javac/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/compilers/javac/pom.xml?view=diffrev=524961r1=524960r2=524961 == --- jakarta/commons/proper/jci/trunk/compilers/javac/pom.xml (original) +++ jakarta/commons/proper/jci/trunk/compilers/javac/pom.xml Mon Apr 2 16:10:58 2007 @@ -4,17 +4,17 @@ parent groupIdorg.apache.commons/groupId artifactIdcommons-jci/artifactId -version1.0-SNAPSHOT/version +version1.0-RC1/version /parent packagingjar/packaging artifactIdcommons-jci-javac/artifactId -version1.0-SNAPSHOT/version +version1.0-RC1/version namecompiler-javac/name dependencies dependency groupIdorg.apache.commons/groupId artifactIdcommons-jci-core/artifactId -version1.0-SNAPSHOT/version +
svn commit: r524962 - in /jakarta/commons/proper/jci/tags/1.0-RC1: ./ compilers/eclipse/pom.xml compilers/groovy/pom.xml compilers/janino/pom.xml compilers/javac/pom.xml compilers/rhino/pom.xml core/p
Author: tcurdt Date: Mon Apr 2 16:11:16 2007 New Revision: 524962 URL: http://svn.apache.org/viewvc?view=revrev=524962 Log: [maven-scm] copy for tag 1.0-RC1 Added: jakarta/commons/proper/jci/tags/1.0-RC1/ - copied from r524960, jakarta/commons/proper/jci/trunk/ jakarta/commons/proper/jci/tags/1.0-RC1/compilers/eclipse/pom.xml - copied unchanged from r524961, jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml jakarta/commons/proper/jci/tags/1.0-RC1/compilers/groovy/pom.xml - copied unchanged from r524961, jakarta/commons/proper/jci/trunk/compilers/groovy/pom.xml jakarta/commons/proper/jci/tags/1.0-RC1/compilers/janino/pom.xml - copied unchanged from r524961, jakarta/commons/proper/jci/trunk/compilers/janino/pom.xml jakarta/commons/proper/jci/tags/1.0-RC1/compilers/javac/pom.xml - copied unchanged from r524961, jakarta/commons/proper/jci/trunk/compilers/javac/pom.xml jakarta/commons/proper/jci/tags/1.0-RC1/compilers/rhino/pom.xml - copied unchanged from r524961, jakarta/commons/proper/jci/trunk/compilers/rhino/pom.xml jakarta/commons/proper/jci/tags/1.0-RC1/core/pom.xml - copied unchanged from r524961, jakarta/commons/proper/jci/trunk/core/pom.xml jakarta/commons/proper/jci/tags/1.0-RC1/examples/pom.xml - copied unchanged from r524961, jakarta/commons/proper/jci/trunk/examples/pom.xml jakarta/commons/proper/jci/tags/1.0-RC1/fam/pom.xml - copied unchanged from r524961, jakarta/commons/proper/jci/trunk/fam/pom.xml jakarta/commons/proper/jci/tags/1.0-RC1/pom.xml - copied unchanged from r524961, jakarta/commons/proper/jci/trunk/pom.xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r524963 - in /jakarta/commons/proper/jci/trunk: compilers/eclipse/pom.xml compilers/groovy/pom.xml compilers/janino/pom.xml compilers/javac/pom.xml compilers/rhino/pom.xml core/pom.xml exa
Author: tcurdt Date: Mon Apr 2 16:11:29 2007 New Revision: 524963 URL: http://svn.apache.org/viewvc?view=revrev=524963 Log: [maven-release-plugin] prepare for next development iteration Modified: jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml jakarta/commons/proper/jci/trunk/compilers/groovy/pom.xml jakarta/commons/proper/jci/trunk/compilers/janino/pom.xml jakarta/commons/proper/jci/trunk/compilers/javac/pom.xml jakarta/commons/proper/jci/trunk/compilers/rhino/pom.xml jakarta/commons/proper/jci/trunk/core/pom.xml jakarta/commons/proper/jci/trunk/examples/pom.xml jakarta/commons/proper/jci/trunk/fam/pom.xml jakarta/commons/proper/jci/trunk/pom.xml Modified: jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml?view=diffrev=524963r1=524962r2=524963 == --- jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml (original) +++ jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml Mon Apr 2 16:11:29 2007 @@ -4,11 +4,11 @@ parent groupIdorg.apache.commons/groupId artifactIdcommons-jci/artifactId -version1.0-RC1/version +version1.0-SNAPSHOT/version /parent packagingjar/packaging artifactIdcommons-jci-eclipse/artifactId -version1.0-RC1/version +version1.0-SNAPSHOT/version namecompiler-eclipse/name dependencies dependency Modified: jakarta/commons/proper/jci/trunk/compilers/groovy/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/compilers/groovy/pom.xml?view=diffrev=524963r1=524962r2=524963 == --- jakarta/commons/proper/jci/trunk/compilers/groovy/pom.xml (original) +++ jakarta/commons/proper/jci/trunk/compilers/groovy/pom.xml Mon Apr 2 16:11:29 2007 @@ -4,11 +4,11 @@ parent groupIdorg.apache.commons/groupId artifactIdcommons-jci/artifactId -version1.0-RC1/version +version1.0-SNAPSHOT/version /parent packagingjar/packaging artifactIdcommons-jci-groovy/artifactId -version1.0-RC1/version +version1.0-SNAPSHOT/version namecompiler-groovy/name dependencies dependency Modified: jakarta/commons/proper/jci/trunk/compilers/janino/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/compilers/janino/pom.xml?view=diffrev=524963r1=524962r2=524963 == --- jakarta/commons/proper/jci/trunk/compilers/janino/pom.xml (original) +++ jakarta/commons/proper/jci/trunk/compilers/janino/pom.xml Mon Apr 2 16:11:29 2007 @@ -4,11 +4,11 @@ parent groupIdorg.apache.commons/groupId artifactIdcommons-jci/artifactId -version1.0-RC1/version +version1.0-SNAPSHOT/version /parent packagingjar/packaging artifactIdcommons-jci-janino/artifactId -version1.0-RC1/version +version1.0-SNAPSHOT/version namecompiler-janino/name dependencies dependency Modified: jakarta/commons/proper/jci/trunk/compilers/javac/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/compilers/javac/pom.xml?view=diffrev=524963r1=524962r2=524963 == --- jakarta/commons/proper/jci/trunk/compilers/javac/pom.xml (original) +++ jakarta/commons/proper/jci/trunk/compilers/javac/pom.xml Mon Apr 2 16:11:29 2007 @@ -4,11 +4,11 @@ parent groupIdorg.apache.commons/groupId artifactIdcommons-jci/artifactId -version1.0-RC1/version +version1.0-SNAPSHOT/version /parent packagingjar/packaging artifactIdcommons-jci-javac/artifactId -version1.0-RC1/version +version1.0-SNAPSHOT/version namecompiler-javac/name dependencies dependency Modified: jakarta/commons/proper/jci/trunk/compilers/rhino/pom.xml URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/compilers/rhino/pom.xml?view=diffrev=524963r1=524962r2=524963 == --- jakarta/commons/proper/jci/trunk/compilers/rhino/pom.xml (original) +++ jakarta/commons/proper/jci/trunk/compilers/rhino/pom.xml Mon Apr 2 16:11:29 2007 @@ -4,11 +4,11 @@ parent groupIdorg.apache.commons/groupId artifactIdcommons-jci/artifactId -version1.0-RC1/version +version1.0-SNAPSHOT/version /parent packagingjar/packaging artifactIdcommons-jci-rhino/artifactId -version1.0-RC1/version +version1.0-SNAPSHOT/version namecompiler-rhino/name dependencies dependency Modified: jakarta/commons/proper/jci/trunk/core/pom.xml URL:
Re: [all] docs on doing maven2 releases
On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote: Guys, Do we already have docs on how to do commmons releases with maven2 somewhere? No. Once [dbcp] is out (pushing it out as we speak), do we expect any more 1.x releases? If not, we should just update the releasing docs to m2. Phil cheers -- Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] docs on doing maven2 releases
On 4/2/07, Phil Steitz [EMAIL PROTECTED] wrote: On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote: Guys, Do we already have docs on how to do commmons releases with maven2 somewhere? No. Once [dbcp] is out (pushing it out as we speak), do we expect any more 1.x releases? If not, we should just update the releasing docs to m2. +1. We should move the nightlies over to the m2's. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] docs on doing maven2 releases
On 03.04.2007, at 01:34, Phil Steitz wrote: On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote: Guys, Do we already have docs on how to do commmons releases with maven2 somewhere? No. Once [dbcp] is out (pushing it out as we speak), do we expect any more 1.x releases? If not, we should just update the releasing docs to m2. From looking at the parent pom I tried mvn -Prc clean install -Dgpg.passphrase=... mvn -Prc release:clean release:prepare mvn -Prc release:perform -Dcommons.deployment.protocol=scpexe But the release:perform failed :-/ ...well, off to bed for now. cheers -- Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] docs on doing maven2 releases
On 4/2/07, Henri Yandell [EMAIL PROTECTED] wrote: On 4/2/07, Phil Steitz [EMAIL PROTECTED] wrote: On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote: Guys, Do we already have docs on how to do commmons releases with maven2 somewhere? No. Once [dbcp] is out (pushing it out as we speak), do we expect any more 1.x releases? If not, we should just update the releasing docs to m2. +1. We should move the nightlies over to the m2's Yeah, assuming the m2's work. Its probably best in each case to post something like [foo] moving to m2 and make sure that nobody screams, all are OK with the pom can get the build to work, etc., before moving the associated nightly and deprecating the m1 build (to be removed in next release). I was planning something like that for [math]. Phil Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[all] Going TLP?
I think the end should be nigh for Jakarta (those on private@ will have seen a thread in which I side-topic'd with the feeling that the end should be nigh for Jakarta). Previously I've suggested that Commons should flatten into Jakarta and that Jakarta should become a general 'Java components' project; however there are some negatives to that that I think are critical. Firstly, it leaves the future Jakarta with a lot of dead projects that are going nowhere. That's not going to change in the short to medium term, so it just becomes a millstone for the project's neck. Secondly, the Jakarta PMC will always remain a big group of people who care about the brand name and the various legacies, rather than a small focused PMC. I think this isn't desirable for any active community that are a part of Jakarta currently - trying to have a PMC that are acting as one community when not being one community doesn't work. Thirdly, I think by being here we are helping to delay the inevitable and keeping the old, broken umbrella going. Moving to TLP will help things move along, and will provide a place for things to move to. So with that said - I'd like to propose that we move to commons.apache.org. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Going TLP?
On 4/2/07, Henri Yandell [EMAIL PROTECTED] wrote: I think the end should be nigh for Jakarta (those on private@ will have seen a thread in which I side-topic'd with the feeling that the end should be nigh for Jakarta). Previously I've suggested that Commons should flatten into Jakarta and that Jakarta should become a general 'Java components' project; however there are some negatives to that that I think are critical. Firstly, it leaves the future Jakarta with a lot of dead projects that are going nowhere. That's not going to change in the short to medium term, so it just becomes a millstone for the project's neck. Secondly, the Jakarta PMC will always remain a big group of people who care about the brand name and the various legacies, rather than a small focused PMC. I think this isn't desirable for any active community that are a part of Jakarta currently - trying to have a PMC that are acting as one community when not being one community doesn't work. Thirdly, I think by being here we are helping to delay the inevitable and keeping the old, broken umbrella going. Moving to TLP will help things move along, and will provide a place for things to move to. So with that said - I'd like to propose that we move to commons.apache.org. +1 We have talked about this lots of times before and some discussions have had us breaking commons itself apart into pieces. My +1 is for the whole of commons as an Apache TLP. To answer some other questions that have come up before and will resurface: +1 for only Java components (flame away, this is just my HO) +1 for bringing sandbox along +1 for welcoming small components from other Jakarta subprojects +0 for waiting to do this until we have a clear idea of where the rest of the Jakarta subprojects are going. Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Going TLP?
On 4/2/07, Phil Steitz [EMAIL PROTECTED] wrote: On 4/2/07, Henri Yandell [EMAIL PROTECTED] wrote: So with that said - I'd like to propose that we move to commons.apache.org. +1 We have talked about this lots of times before and some discussions have had us breaking commons itself apart into pieces. My +1 is for the whole of commons as an Apache TLP. To answer some other questions that have come up before and will resurface: +1 for only Java components (flame away, this is just my HO) Yep - though in reality this means: We'll do whatever the community wants to do. If someone proposes a Ruby library and we have a community interested in creating and supporting a Ruby library, then it would of course be strongly considered. The argument here is going to be in what we put in our resolution. Do we explicitly state Java, or do we leave things language agnostic and rely on the fact that it is our community, and generally our community is going to want to do Java and Java related things. +1 for bringing sandbox along And dormant. +1 for welcoming small components from other Jakarta subprojects +0 for waiting to do this until we have a clear idea of where the rest of the Jakarta subprojects are going. Once we go TLP, I imagine a few would head in our direction, whereas until we go TLP there won't be much of a decision made either way. I know I plan to suggest that the RDC taglib moves to Commons so it can be with SCXML (they're fairly tied aren't they?), and then the other parts of Taglibs can be put gently to sleep (unsure on JSTL). Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (FILEUPLOAD-132) How do we retrieve the HTTP Headers in the request?
How do we retrieve the HTTP Headers in the request? --- Key: FILEUPLOAD-132 URL: https://issues.apache.org/jira/browse/FILEUPLOAD-132 Project: Commons FileUpload Issue Type: Wish Affects Versions: 1.2 Environment: Open Suse 10.1 Reporter: Lewis Choo Man I would like to retrieve the HTTP request headers from the org.apache.commons.fileupload.FileUpload class, while still being able to save any file that is embedded in the HTTP body. Is there a public method to do so? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
