commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From (Jeffrey D. Brekke)
Subject Re: [NET] Re: dependency dilemma
Date Sun, 02 Mar 2003 04:26:50 GMT

Does using maven fail running the tests also?

maven java:jar

There may be a problem with the ant build.xml generation.  If using
maven for builds can get you buy for now, once you check in I'll try
to see if maven's ant plugin needs to be altered.  Otherwise if you
don't/can't use maven for your builds, you could add the xml jars to
the deps and regen the ant build.xml I guess.  I no longer use ant.

>>>>> On Sat, 1 Mar 2003 21:57:13 -0600, "Steve Cohen" <>

> Jeff - I hadn't known that I wasn't supposed to touch build.xml
> directly.  I didn't know maven could generate it for me.  That's a
> cool feature.  Simply adding oro to the dependency list as you
> indicated does get it into the build file and allows the project to
> build.  However, the xml-parsing jars are NOT in the classpath when
> the test goal is run and the test target fails.  I can get it to
> succeed either by manually changing the build.xml to run the test
> target with fork false, or by adding xml-apis.jar and xercesImpl.jar
> to the get-deps list.  But out of the box, it fails.

> So something is wrong.  The tests won't run without these jars and
> there's nothing in the build.xml file as created by maven that puts
> them there.  (These jars are not needed to compile the tests, only
> to run them).  So I would assume that there are some maven
> configuration options we need to change to do to get them there.

> I will take a look at the maven docs that deal with genning the
> build.xml and see if I can find an answer.

Jeffrey D. Brekke                         
Wisconsin,  USA                           

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message