Steve I never had these issues when the ftp2 code was in the source tree.
The xml-parsing jars should be present when the test goal is run, we never had that
dependency in the POM.
Also you shouldn't be modifying the ant build file by hand, but
instead generate a new one with maven:
maven ant
This would then reflect the change in dependecies from the POM. Does
the build work properly with maven and your just having troubles with
the ant build?
Does this help?
jb
"Steve Cohen" <[EMAIL PROTECTED]> writes:
> That was easy enough.
>
> I added the ORO dependency back in (and also an entry in the
> get-deps target to pull it in) and all those problems went away.
>
> However, I then found, that with moving the tests into src/test as I
> had planned to do, simply having junit brought in through maven
> doesn't fully solve the problem as we also have to bring in the
> xml-parsing jars as well. This is a run-test-time problem that
> doesn't appear until you actually have tests to run.
>
> Two solutions here 1) make the fork attribute of the junit task-call
> in the internal-test target false and get the benefit of the
> xml-parsing jars that are already used in ant. I'm not sure what
> bad side-effects this will have 2) drag these jars over to our side,
> using the get-deps target (or perhaps a new get-test-deps target).
>
> I'm not sure what the preferred maven way is here.
--
=====================================================================
Jeffrey D. Brekke [EMAIL PROTECTED]
Wisconsin, USA [EMAIL PROTECTED]
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
