History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CC-400
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Jeffrey Fredrick
Reporter: Jeffrey Fredrick
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
CruiseControl

internal ant can't create optional tasks (such as junit)

Created: 28/Jan/06 08:59 AM   Updated: 19/Aug/06 11:16 PM
Component/s: None
Affects Version/s: 2.4
Fix Version/s: 2.6

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Relationship
This issue Relates to:
CC-268 [PATCH] Add Ant style launcher Major Resolved
This issue Relates to:
CC-488 Ant Jar in the binary distro twice, b... Major Open


 Description  « Hide
since the various ant jars aren't on the system classpath (when CC is launched) the internal ant can't create those optional tasks. this makes it more or less useless as it doesn't even work with the sample project from our binary release.

this problem effects both the binary and source releases.

 All   Comments   Work Log   Change History      Sort Order:
Jeffrey Fredrick [28/Jan/06 09:01 AM]
using an ant style launcher (CC-268) should allow us to more easily add the required jars to the system classpath (CC-400).

Jeffrey Fredrick [02/Jul/06 09:48 PM]
the mismatch should have no effect.

if you use antscript/anthome to use the bundled apache-ant-1.6.5 then you should have no problem using the optional tasks there, and as you are executing in a separate VM from CC there should be no classpath conflicts.

if you aren't using antscript/anthome and are instead using the internal version of ant -- the one on the CC classpath -- then there is a known bug with the internal version of CC not supporting optional tasks (CC-400).


Jeffrey Fredrick [19/Aug/06 11:16 PM]
patch on devel list from Dan Rollo committed w/modifications.