
|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
File Attachments:
|
1.
cc_launcher_patch.txt (39 kb)
|
|
Issue Links:
|
Relationship
|
|
|
|
This issue Relates to:
|
|
CC-400
internal ant can't create optional ta...
|
|
|
 |
CC-720
Need to provide directory for classes...
|
|
|
|
CC-477
Remove the class-path in the cruiseco...
|
|
|
|
|
|
|
Hi all,
I've attached a patch which adds an Ant style launcher jar to
CruiseControl. Hopefully, if this works out, it should solve a lot of
the classpath problems - including command line length limits on
Windows.
It could also make things easier to move to a different packaging
structure in the future (should we choose to do so).
Note that I have had very little time to test this - in fact it's
completely untested on Unix platforms, so use with care!!!
I'm submitting this in the hopes that others will join in, give it a
try, and help me clean it up a bit. I don't expect that it's ready for
submission as it sits.
If you are familiar with Ant, then this will seem very familiar. The
launcher supports the same basic options with one additional one to
deal with the fact that CC seperates it's jars into two different
directories (dist and lib). Jars are searched in the following order:
1. Anything given on the command line using '-lib'.
2. Any jars in the per-user directory ($HOME/.cruisecontrol/lib).
3. All jars in the installation dist dir.
4. All jars in the installation lib dir
NOTE: I didn't modify the Ant Locator class to handle nested lib dirs,
so if you want to use the internal version of Ant, you'll have to add
the ant-launcher.jar using the '-lib' option.
Many thanks,
Robert
|
|
Description
|
Hi all,
I've attached a patch which adds an Ant style launcher jar to
CruiseControl. Hopefully, if this works out, it should solve a lot of
the classpath problems - including command line length limits on
Windows.
It could also make things easier to move to a different packaging
structure in the future (should we choose to do so).
Note that I have had very little time to test this - in fact it's
completely untested on Unix platforms, so use with care!!!
I'm submitting this in the hopes that others will join in, give it a
try, and help me clean it up a bit. I don't expect that it's ready for
submission as it sits.
If you are familiar with Ant, then this will seem very familiar. The
launcher supports the same basic options with one additional one to
deal with the fact that CC seperates it's jars into two different
directories (dist and lib). Jars are searched in the following order:
1. Anything given on the command line using '-lib'.
2. Any jars in the per-user directory ($HOME/.cruisecontrol/lib).
3. All jars in the installation dist dir.
4. All jars in the installation lib dir
NOTE: I didn't modify the Ant Locator class to handle nested lib dirs,
so if you want to use the internal version of Ant, you'll have to add
the ant-launcher.jar using the '-lib' option.
Many thanks,
Robert
|
Show » |
|