Re: [Clirr-devel] running clirr on cactus

[<lak...@t-...>]

OK, I can now reproduce your problem. Thanks for guiding me through the 
Cactus setup.

Lars

PS: Note that I have added Maven to the main navigation, as I have 
sucessfully tested it on commons-collections and commons-logging, so it 
seems that it "kinda works".


Vincent Massol wrote:

>Hi Lars,
>
>I've tried adding the newClasspah and oldClasspath as follows in
>plugin.jelly:
>
>    <clirr failOnWarning="${clirr.fail.on.warning}"
>        failOnError="${clirr.fail.on.error}">
>      <origFiles dir="${clirr.baseline.destination.dir}" 
>          includes="${clirr.baseline.destination.basename}"/>
>      <newFiles dir="${maven.build.dir}"
>includes="${maven.final.name}.jar"/>
>      <formatter type="xml" outfile="${clirr.report.file}"/>
>
>      <newClassPath refid="maven.dependency.classpath"/>
>      <oldClassPath refid="maven.dependency.classpath"/>
>
>    </clirr>  
>
>But I still get the same error.
>
>Here's what I do to run clirr on the cactus framework project:
>
>* cd to jakarta-cactus/framework
>* create a build.properties file and add the following to it:
>
>clirr.baseline.destination = C:/Documents and Settings/Vincent
>Massol/.maven/repository/cactus/jars/cactus-13-1.6.1.jar
>
>(i.e. the location of the previous version to compare with)
>
>* type "maven clirr"
>
>You're right, I need to sort out the organization. Actually Cactus does not
>really build with Maven yet (it's a work in progress which is not
>progressing much right now). But forcing the location of the base jar should
>work.
>
>Thanks
>-Vincent
>
>  
>