[
http://jira.codehaus.org/browse/JBEHAVE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265680#action_265680
]
Derek Clarkson commented on JBEHAVE-505:
----------------------------------------
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.
> Ant tasks running with incorrect classpath
> ------------------------------------------
>
> Key: JBEHAVE-505
> URL: http://jira.codehaus.org/browse/JBEHAVE-505
> Project: JBehave
> Issue Type: Bug
> Components: Ant Tasks
> Affects Versions: 3.3.2
> Reporter: Derek Clarkson
>
> 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????
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
