On Tue, Jun 24, 2003 at 11:24:00PM +0200, Rafal Krzewski wrote:
> Incze Lajos wrote:
> > On a fresh CVS clean bootstrap build I get (building maven with itself phase):
> >
> > ----
> > ...
> > [exec] [junit] dir attribute ignored if running in the same VM
> > [exec] [junit] Running org.apache.maven.project.ProjectInheritanceTest
> > [exec] [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 6.397
> > sec
> > [exec] [junit] [ERROR] TEST
> > org.apache.maven.project.ProjectInheritanceTest FAILED
> > ...
> > [exec] BUILD FAILED
> > [exec] There were test failures.
> >
> > BUILD FAILED
> > file:/home/s/tmp/maven/build-bootstrap.xml:313: exec returned: 70
> > ----
>
> I've seen that yesterday too, I even tried to post a message on that but
> it got munched by my email client (bad network day, or rather week to
> be more specific...)
>
> Could you please locate the associated failure report in
> target/test-reports (it'll be something-ProjectInheritanceTest.txt) and
> post it? I don't have mine handy ATM.
>
Yes, that's it:
line 122 (from src/test/java/test/org/apache/maven/project/ProjectInheritenceTest.java)
// Test Source Directories
assertEquals( "src/java", p.getBuild().getSourceDirectory() );
and the fail:
FAILED
expected:<...> but was:</home/s/tmp/maven/src/test/extend/...>
junit.framework.ComparisonFailure: expected:<...> but
was:</home/s/tmp/maven/src/test/extend/...>
-----
So, it expects relative path and gets an absolute.
iSeems to me, that time to stick with on econvention (basedir relative,
or ${basedir}/... in POM) and gow through all the plugins and tests
to behave accordingly.
incze
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
