Issue 46 in instinct: InstinctTask requires specification classes to be present in taskdef classpath

[codesite...@google.com]

Issue 46: InstinctTask requires specification classes to be present in
taskdef classpath
http://code.google.com/p/instinct/issues/detail?id=46

New issue report by jem.mawson:
What steps will reproduce the problem?
1. Create an ant build where the instinct task is taskdef(ined) prior to
the specification classes being compiled.
2. Execute the ant target

What is the expected output? What do you see instead?
Expected: All specifications run, as the task should use the nested
classpath provided, and not the classpath used for the taskdef
Actual: The specifications are not found and nothing is executed.

Issue attributes:
Status: Accepted
Owner: jem.mawson
Labels: Type-Defect Priority-Medium

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Issue 46: InstinctTask requires specification classes to be present in
taskdef classpath
http://code.google.com/p/instinct/issues/detail?id=46

Comment #1 by jem.mawson:
(No comment was entered for this change.)

Issue attribute updates:
Status: Started

[codesite...@google.com]

Issue 46: InstinctTask requires specification classes to be present in
taskdef classpath
http://code.google.com/p/instinct/issues/detail?id=46

Comment #2 by jem.mawson:
See my email to the dev mailing list dated 18/11.

Issue attribute updates:
Status: Fixed