thanks but unfortunately that doesn't work ( I'd already tried that ). From what I can see the context created for the jelly script unit tests is completely fresh with only the basedir ( and possibly other system properties) being included.

At this stage I'll look at using a custom tag to process the project file and place the required variables in the context but I'd hoped there would already be a solution.

-Bert




[EMAIL PROTECTED] wrote:


classpathref="maven.dependency.classpath" on your javac task.
--
dIon Gillard, Multitask Consulting
Blog:      http://blogs.codehaus.org/people/dion/



Bert van Brakel <[EMAIL PROTECTED]> wrote on 07/12/2003 08:43:18 PM:



I'm using jelly junit to run some of my tests which include using the ant:javac task to compile some generated code and I'm wondering how to include all the project dependencies in javac's classpath. If anyone could point me in the right direction it would be most appreciated, as I




haven't been able to find anything on the mail archives. I'm not really keen to duplicate the dependencies in each junit test script.

Many thanks,
-Bert


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to