Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.3.2
-
Fix Version/s: None
-
Component/s: Ant Tasks
-
Labels:None
-
Number of attachments :
Description
I've been trying to make this work for hours now. It appears that the Ant tasks run the Embedders with the classpath used to run Ant and that there is no way to override this. This means I cannot run JBehave against the classpaths used to build and test the application.
How do we specify a classpath for JBEhave's Ant tasks????
Activity
Mauro Talevi
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Affects Version/s | 3.3.2 [ 17308 ] | |
| Affects Version/s | web-3.2 [ 16758 ] |
Normally would love to do so. But that means I'd have to do a full development cycle and ATM I don't have the bandwidth to take on another project.
My thoughts are that without being able to set a classpath for the ant tasks, they might as well be retired. The reason is that every Ant project I've worked on is always about building and testing software. So running tests always means compiling code into directories, building a classpath with those directories and then handing it to the test runners. Without the ability to specific an ant class path property to work with, these ant tasks cannot work because the the classpath as used by ant doesn't contain any of the compiled code and never will.
Derek Clarkson
added a comment - Normally would love to do so. But that means I'd have to do a full development cycle and ATM I don't have the bandwidth to take on another project.
My thoughts are that without being able to set a classpath for the ant tasks, they might as well be retired. The reason is that every Ant project I've worked on is always about building and testing software. So running tests always means compiling code into directories, building a classpath with those directories and then handing it to the test runners. Without the ability to specific an ant class path property to work with, these ant tasks cannot work because the the classpath as used by ant doesn't contain any of the compiled code and never will. 
Classloading in Ant is less than transparent, so ATM it uses the classloader used to load the task itself. Feel free to provide a patch that specifies the classloader in the "Ant way".