[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #23 from Thomas Opfer --- (In reply to Rainer Jung from comment #22) > Do we actually understand, what would be wrong with the line > > 2\>\&1 \& echo \$! \>\"$catalina_pid_file\" \; \} $catalina_out_command "&" > > (single escaped ampersand)? I don't really know what the problem is, but it might be that this writes a PID even if nohup fails. But this is just a guess. And this problem should also appear with the old version before bug 53930. For me, this line does not really look wrong. Still, I don't like the process timing in this line. I'm asking myself whether we could omit the "&" at the end of the line. The first \& should already put the process into the background, shouldn't it? Best regards, Thomas -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63023] Provide a way to load SecurityProviders into the system classloader compatible with Java 9+
https://bz.apache.org/bugzilla/show_bug.cgi?id=63023 Jonathan Horowitz changed: What|Removed |Added Version|9.0.14 |9.0.16 -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [PROPOSAL] Copy DBCP 1.x (and POOL 1.x) source to 7.0.x
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 2/12/19 08:55, Mark Thomas wrote: > Hi, > > Tomcat 7 depends on DBCP 1.x and POOL 1.x. The last release of each > of these was in 2013. There are a number of fixes I would like to > be able to pull into Tomcat 7 - including the fix for BZ 58338. > > There is little/no appetite in the Commons community to release > DBCP 1.x or Pool 1.x. > > Having tried to get releases out via the release process Commons > uses, I have no desire to try and get these releases out myself. > > It would greatly simplify things if 7.0.x took the same approach to > DBCP and Pool as 8.5.x and 9.0.x and maintained a local fork of the > code. > > Like the fork of DBCP 2.x and Pool 2.x, changes would be made in > commons and the Tomcat fork updated. The only local changes would > be the package re-naming and and changes required to keep > checkstyle and FindBugs happy (and some of those may get made in > Commons first). > > I therefore propose to import the DBCP/Pool 1.x source into Tomcat > 7.x following the same pattern as for DBCP/Pool 2.x in 8.5.x. > > If there are no objections, I'll probably do this late this week > early next. Is there any appetite for maintaining patches-only and merging-on-build? It would mean a smaller repo for us not just in terms of size (which is largely irrelevant) but also in terms of brain-cycles. If I can see that we patch pool-1.x with a 5-line change and add a sour\ce file versus there are 500 source files in there that all need to be diff'd against their original sources, it makes it easier for anyone to look at the code to see what's happening. It does complicate the release process, though. - -chris -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlxjUlUACgkQHPApP6U8 pFjZ1g/9EdYu1jC2JDTd6F6X7QZx7i+1VXKytdr0umzFfqKDQ+pbsVIKZDDWgoLU cHRX/2jw3IBpObxTL/44cJNGvy2g9PGOKL4I7IQHF1/zm9jyspTmp01JIPbznWgK /Kw0+lbsd0parxu+UzEzV4plDHLg4uyvTEXdmKr0ZMoe2MqSYSUR6zHIcGPIVW/T JLwpxVkk4alpRonYquOdKVB9W6iH67/OgqVLyrLNP+KBU2RTHCL5/OP6FVcEIWvZ Hqekt8q8tZQA1biGUTFNzp15P3oseugwd2DVrstvbEapF37juRJIOApMxONBjIXQ ntQ1d8T6RwD743ThRQfyn3BI8DoZua7LYLIgeRyaV3PYij3uklyeGuY8xtsQxJtz Q3vfDEuHg+AqFvnSvjjDnbX4umybNsxGq1W5zYyhCOyaMcXVsvTVgYu6nRw3esc7 jhuB+3PDAB6glQ7Hy4b0ugmjte5pGmQGjczW/8S6KBvlqJwjR8RKykjX9oT8Yr16 2hPL9EZaUyDfda0v/u/fQZAJdqZqEwdXXgQUh4BgBInX30QMo5BlT5OgBipA4Jtt +lmf1bNlviIpbc800t35VswXzzp4Joh8r1wYKuWMwBlPT9fR60EcSWgwm2tutyJw yA6YZs63PkYHhwxCDwdBE59e36ZJuqL3R/rwXcMS/xAAWxu7Tjg= =wXz0 -END PGP SIGNATURE- - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #22 from Rainer Jung --- Do we actually understand, what would be wrong with the line 2\>\&1 \& echo \$! \>\"$catalina_pid_file\" \; \} $catalina_out_command "&" (single escaped ampersand)? As far as I understand from this ticket here, there was an issue about not being able to shut down. Does this happen only in combination with systemd? I can not reproduce locally with normal shell start/stop. Wo ever tests this: did you set CATALINA_PID to some reasonable value, eg. to logs/catalina.pid? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Jakarta EE TCKs and compatibility logo
On Tue, Feb 12, 2019 at 6:16 PM Mark Thomas wrote: > Any other thoughts on this topic? > I think we should have EE compatibility back if possible. Rémy > Mark > > > On 21/01/2019 10:56, Mark Thomas wrote: > > Switching hats and speaking as a Tomcat committer. > > > > My experience is that folks expect Tomcat to follow the spec and want to > > know that it does. However, formal certification (or lack of it) hasn't > > seemed to be a big deal for our users in recent years. I don't know how > > much of that is because end users care more about actual behaviour than > > formal certification and how much it is because they understand the > > historical issues between the ASF and Sun/Oracle over access to the TCKs. > > > > Maybe those expectations will change with the specs moving to Eclipse. > > > > If the community wants to see the compatibility logo then I have no > > objection as the requirements don't seem very onerous. > > > > Mark > > > > > > On 18/01/2019 22:53, Mark Thomas wrote: > >> Hi all, > >> > >> I am writing to your dev@ lists (on BCC) as your project has, in the > >> past, requested access to the Java EE TCKs while they were controlled by > >> Sun and then Oracle. > >> > >> As I am sure you are aware, Java EE has moved to Eclipse and is now > >> Jakarta EE. The good news is that the TCKs have been open sourced. > >> > >> https://github.com/eclipse-ee4j/jakartaee-tck > >> > >> (I haven't tried to build the latest TCK from source yet but it is on my > >> TODO list.) > >> > >> Shipping compatible implementations of the Jakarta EE specs (and being > >> able to make public statements to that effect) will be subject only to > >> the spec [1] and TCK [2] licenses. There will no longer be a TCK > >> agreement or NDA to sign. However... > >> > >> The question has arisen whether or not any ASF projects will want to use > >> the Jakarta EE compatible logo [3]. If a project wants to be able to do > >> this, there are some organisational hoops to jump through. Before the > >> ASF starts down that path the board has asked me to see if there are any > >> projects that want to use the Jakarta EE compatible logo. After all, > >> there is no point jumping through the hoops if no-one wants to use the > logo. > >> > >> With the above in mind can you please discuss this amongst your project > >> community and reply back to jcp-o...@apache.org whether or not your > >> project is interested in being able to use the Jakarta EE compatible > >> logo. I ask that you complete this no later than the next board meeting > >> (20th February 2019). > >> > >> If you have any questions about any of the above, please also use > >> jcp-o...@apache.org to ask them. > >> > >> Thanks, > >> > >> Mark > >> > >> > >> [1] https://www.eclipse.org/legal/efsl.php > >> [2] https://www.eclipse.org/legal/tck.php > >> [3] https://www.eclipse.org/legal/tck.php > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > >> For additional commands, e-mail: dev-h...@tomcat.apache.org > >> > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #21 from Thomas Opfer --- > If I am understanding this correctly that would mean: > > - reverting r1848046 and r1850829 for 9.0.x > - reverting r1848048 and r1850830 for 8.5.x > - reverting r1848049 and r1850831 for 7.0.x That should at least fix the actual trouble. > Re-opening bug 53930 and resolving it as WONTFIX - suggesting that a named > pipe is used. I'm not an expert on named pipes. The documentation of mkfifo says: "However, it has to be open at both ends simultaneously before you can proceed to do any input or output operations on it. Opening a FIFO for reading normally blocks until some other process opens the same FIFO for writing, and vice versa." I don't know whether this is ok or not. I don't need the new feature from bug 53930 at all. > Assuming my understanding is correct, do we view this as sufficient to > warrant a new 9.0.x and 8.5.x release? Currently, I don't need a new version (I just use the old catalina.sh). But it might still be a good idea, because other people might run into this issue. I don't know how much work a new release really is. Best regards, Thomas -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "AddOns" by KonstantinKolinko
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "AddOns" page has been changed by KonstantinKolinko: https://wiki.apache.org/tomcat/AddOns?action=diff&rev1=13&rev2=14 Comment: Move PicketLink Vault to a named section + = PropertySource = + + == PicketLink Vault == + + * [[https://github.com/picketbox/tomcat-vault|PicketLink Vault extension for Apache Tomcat]] - Provides a custom `PropertySource` that can be used with Tomcat. See [[FAQ/Password]]. + + + = Web Applications = == PSI Probe manager application == @@ -43, +51 @@ (Historically, the name is a tribute to Lambda Probe project, which they continued as a fork. The original Lambda Probe project (www.lambdaprobe.org) closed more than 10 years ago (2006) and is not applicable to current versions of Tomcat). - - = Other = - - * [[https://github.com/picketbox/tomcat-vault|PicketLink Vault extension for Apache Tomcat]] - Provides a custom `PropertySource` that can be used with Tomcat. See [[FAQ/Password]]. - - [[CategoryFAQ]] - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "AddOns" by KonstantinKolinko
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "AddOns" page has been changed by KonstantinKolinko: https://wiki.apache.org/tomcat/AddOns?action=diff&rev1=14&rev2=15 Comment: Add a link to Agafua-syslog (Historically, the name is a tribute to Lambda Probe project, which they continued as a fork. The original Lambda Probe project (www.lambdaprobe.org) closed more than 10 years ago (2006) and is not applicable to current versions of Tomcat). + + = Logging = + + == Logging to Syslog == + + * See a [[https://stackoverflow.com/questions/2311697/is-there-a-robust-java-util-logging-handler-implementation-of-syslog|StackOverflow question]] and [[http://rusv.github.io/agafua-syslog/|Agafua-syslog]] project ([[https://github.com/rusv/agafua-syslog/tree/master|GitHub]]). + + [[CategoryFAQ]] - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Jakarta EE TCKs and compatibility logo
Any other thoughts on this topic? Mark On 21/01/2019 10:56, Mark Thomas wrote: > Switching hats and speaking as a Tomcat committer. > > My experience is that folks expect Tomcat to follow the spec and want to > know that it does. However, formal certification (or lack of it) hasn't > seemed to be a big deal for our users in recent years. I don't know how > much of that is because end users care more about actual behaviour than > formal certification and how much it is because they understand the > historical issues between the ASF and Sun/Oracle over access to the TCKs. > > Maybe those expectations will change with the specs moving to Eclipse. > > If the community wants to see the compatibility logo then I have no > objection as the requirements don't seem very onerous. > > Mark > > > On 18/01/2019 22:53, Mark Thomas wrote: >> Hi all, >> >> I am writing to your dev@ lists (on BCC) as your project has, in the >> past, requested access to the Java EE TCKs while they were controlled by >> Sun and then Oracle. >> >> As I am sure you are aware, Java EE has moved to Eclipse and is now >> Jakarta EE. The good news is that the TCKs have been open sourced. >> >> https://github.com/eclipse-ee4j/jakartaee-tck >> >> (I haven't tried to build the latest TCK from source yet but it is on my >> TODO list.) >> >> Shipping compatible implementations of the Jakarta EE specs (and being >> able to make public statements to that effect) will be subject only to >> the spec [1] and TCK [2] licenses. There will no longer be a TCK >> agreement or NDA to sign. However... >> >> The question has arisen whether or not any ASF projects will want to use >> the Jakarta EE compatible logo [3]. If a project wants to be able to do >> this, there are some organisational hoops to jump through. Before the >> ASF starts down that path the board has asked me to see if there are any >> projects that want to use the Jakarta EE compatible logo. After all, >> there is no point jumping through the hoops if no-one wants to use the logo. >> >> With the above in mind can you please discuss this amongst your project >> community and reply back to jcp-o...@apache.org whether or not your >> project is interested in being able to use the Jakarta EE compatible >> logo. I ask that you complete this no later than the next board meeting >> (20th February 2019). >> >> If you have any questions about any of the above, please also use >> jcp-o...@apache.org to ask them. >> >> Thanks, >> >> Mark >> >> >> [1] https://www.eclipse.org/legal/efsl.php >> [2] https://www.eclipse.org/legal/tck.php >> [3] https://www.eclipse.org/legal/tck.php >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: dev-h...@tomcat.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Quick review of outline for Tomcat security presentation?
Nice ... Some possible adds .. - Keep your java up to date (companion point to OS update) - Link to OWASP (whole talk to itself) - IP Filtering ... Consider a WAF - IP Filtering ... Where possible - Block all outbound connections - Maybe Lockout realm worth a quick mention? - IIRC: Clustering has assumptions on the security of the network -Tim On Mon, Feb 11, 2019 at 2:53 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > All, > > New and improved! With a link to the outline! > > https://people.apache.org/~schultz/Apache%20RoadShow%20DC%202019/Locking > - -Down%20Apache%20Tomcat_outline.pdf > >
Re: [PROPOSAL] Copy DBCP 1.x (and POOL 1.x) source to 7.0.x
On Tue, Feb 12, 2019 at 2:55 PM Mark Thomas wrote: > Hi, > > Tomcat 7 depends on DBCP 1.x and POOL 1.x. The last release of each of > these was in 2013. There are a number of fixes I would like to be able > to pull into Tomcat 7 - including the fix for BZ 58338. > > There is little/no appetite in the Commons community to release DBCP 1.x > or Pool 1.x. > > Having tried to get releases out via the release process Commons uses, I > have no desire to try and get these releases out myself. > > It would greatly simplify things if 7.0.x took the same approach to DBCP > and Pool as 8.5.x and 9.0.x and maintained a local fork of the code. > > Like the fork of DBCP 2.x and Pool 2.x, changes would be made in commons > and the Tomcat fork updated. The only local changes would be the package > re-naming and and changes required to keep checkstyle and FindBugs happy > (and some of those may get made in Commons first). > > I therefore propose to import the DBCP/Pool 1.x source into Tomcat 7.x > following the same pattern as for DBCP/Pool 2.x in 8.5.x. > > If there are no objections, I'll probably do this late this week early > next. > +1 Obviously if there's never going to be any new releases, then this is the only option. Rémy
[PROPOSAL] Copy DBCP 1.x (and POOL 1.x) source to 7.0.x
Hi, Tomcat 7 depends on DBCP 1.x and POOL 1.x. The last release of each of these was in 2013. There are a number of fixes I would like to be able to pull into Tomcat 7 - including the fix for BZ 58338. There is little/no appetite in the Commons community to release DBCP 1.x or Pool 1.x. Having tried to get releases out via the release process Commons uses, I have no desire to try and get these releases out myself. It would greatly simplify things if 7.0.x took the same approach to DBCP and Pool as 8.5.x and 9.0.x and maintained a local fork of the code. Like the fork of DBCP 2.x and Pool 2.x, changes would be made in commons and the Tomcat fork updated. The only local changes would be the package re-naming and and changes required to keep checkstyle and FindBugs happy (and some of those may get made in Commons first). I therefore propose to import the DBCP/Pool 1.x source into Tomcat 7.x following the same pattern as for DBCP/Pool 2.x in 8.5.x. If there are no objections, I'll probably do this late this week early next. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63041] shutdown.sh exits non 0 requires KILLSIG from OS
https://bz.apache.org/bugzilla/show_bug.cgi?id=63041 --- Comment #20 from Mark Thomas --- (In reply to Konstantin Kolinko from comment #19) > An idea: use a named pipe (a FIFO special file) to solve the original bug > 53930. If I am understanding this correctly that would mean: - reverting r1848046 and r1850829 for 9.0.x - reverting r1848048 and r1850830 for 8.5.x - reverting r1848049 and r1850831 for 7.0.x Re-opening bug 53930 and resolving it as WONTFIX - suggesting that a named pipe is used. This is consistent with the work-around of reverting to an earlier version of catalina.sh. Assuming my understanding is correct, do we view this as sufficient to warrant a new 9.0.x and 8.5.x release? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63167] Network Requirements To Resolve No Members Active In Cluster Group
https://bz.apache.org/bugzilla/show_bug.cgi?id=63167 Mark Thomas changed: What|Removed |Added Component|Cluster |Documentation Severity|normal |enhancement --- Comment #1 from Mark Thomas --- Moving to enhancement request for docs. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[GUMP@vmgump-vm3]: Project tomcat-trunk-test-nio2 (in module tomcat-trunk) 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 tomcat-trunk-test-nio2 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: - tomcat-trunk-test-nio2 : Tomcat 9.x, a web server implementing the Java Servlet 4.0, ... Full details are available at: http://vmgump-vm3.apache.org/tomcat-trunk/tomcat-trunk-test-nio2/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on bnd exists, no need to add for property bndlib.jar. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-trunk/output/logs-NIO2 -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-trunk/output/test-tmp-NIO2/logs -WARNING- No directory [/srv/gump/public/workspace/tomcat-trunk/output/test-tmp-NIO2/logs] The following work was performed: http://vmgump-vm3.apache.org/tomcat-trunk/tomcat-trunk-test-nio2/gump_work/build_tomcat-trunk_tomcat-trunk-test-nio2.html Work Name: build_tomcat-trunk_tomcat-trunk-test-nio2 (Type: Build) Work ended in a state of : Failed Elapsed: 24 mins 18 secs Command Line: /usr/lib/jvm/java-8-oracle/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only -Dsun.zip.disableMemoryMapping=true org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbase.path=/srv/gump/public/workspace/tomcat-trunk/tomcat-build-libs -Dbnd.jar=/srv/gump/packages/bnd/bnd-4.0.0/biz.aQute.bnd-4.0.0.jar -Dsaaj-api.jar=/srv/gump/packages/saaj-api/saaj-api-1.3.5.jar -Djaxrpc-lib.jar=/srv/gump/packages/jaxrpc/geronimo-spec-jaxrpc-1.1-rc4.jar -Dtest.temp=output/test-tmp-NIO2 -Djunit.jar=/srv/gump/public/workspace/junit/target/junit-4.13-SNAPSHOT.jar -Djava.net.preferIPv4Stack=/srv/gump/public/workspace/tomcat-trunk/true -Dobjenesis.jar=/srv/gump/public/workspace/objenesis/main/target/objenesis-3.1-SNAPSHOT.jar -Dexamples.sources.skip=true -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/target/commons-daemon-1.1.1-SNAPSHOT.jar -Dtest.openssl.path=/srv/gump/public/workspace/openssl-master/dest-20190212/bin/openssl -Dexecute .test.nio=false -Dhamcrest.jar=/srv/gump/packages/hamcrest/hamcrest-core-1.3.jar -Dbndlib.jar=/srv/gump/packages/bnd/bndlib-4.0.0/biz.aQute.bndlib-4.0.0.jar -Dexecute.test.apr=false -Dwsdl4j-lib.jar=/srv/gump/packages/wsdl4j/wsdl4j-1.6.3.jar -Dtest.reports=output/logs-NIO2 -Dexecute.test.nio2=true -Djdt.jar=/srv/gump/packages/eclipse/plugins/R-4.7.3a-201803300640/ecj-4.7.3a.jar -Dtest.relaxTiming=true -Dtest.excludePerformance=true -Dtest.accesslog=true -Deasymock.jar=/srv/gump/public/workspace/easymock/core/target/easymock-4.1-SNAPSHOT.jar -Dcglib.jar=/srv/gump/packages/cglib/cglib-nodep-2.2.jar test [Working Directory: /srv/gump/public/workspace/tomcat-trunk] CLASSPATH: /usr/lib/jvm/java-8-oracle/lib/tools.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-trunk/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.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/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/servlet-api.ja r:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/websocket-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jaspic-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-storeconfig.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib
