commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <>
Subject Re: [validator] tests all fail
Date Mon, 26 May 2003 21:00:33 GMT
(i can't speak for validator but) digester uses ant as the primary build 
tool and creating the distribution puts the dtd in the correct place. the 
maven build is secondary provided for those who prefer maven. it appears 
that the maven build doesn't create the distribution correctly. i'm afraid 
that fixing this isn't a big priority for me (at least until maven is out 
of beta, i only keep the maven build up to date on components where maven 
is the primary build tool). maybe someone else will step up and supply a 
patch to get it working again.

from what i can see, validator has a hand crafted build.xml and so i'd 
guess that ant is their primary build tool (components who use maven as 
the primary build tool usually have a generated build.xml.)

anyway, enough of the excuses - here's the advice. all the commons 
components should build using ant (and unit tests should succeed) whether 
they use maven as the primary build tool or not. so, if you have problems 
build a component using maven, try switching to ant.

- robert

On Monday, May 26, 2003, at 08:58 PM, wrote:

> Hi,
> I'm building commons sub-projects (validator, digester) from CVS, and the
> tests all fail for validator.
> It turns out, that in the build for digester (using Maven), the
> digester-rules.dtd doesn't get put in the jar, and in the validator build
> w/ Maven the digester-rules.xml doesn't get put in the classpath
> (target/classes/org/apache/commons/validator). Copying the files by hand
> fixes the problem for me.
> How are you guys building the releases for these things? Are you copying
> the xml and dtd files by hand?
> Am I missing something?
> I lost a huge amount of time figuring this out today.
> Dave

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

View raw message