RE: [picocontainer-dev] [NanoContainer] Maven 2 Multiproject Build Error?
"Michael Rimov" <[email protected]>
| Newsgroups | gmane.comp.java.picocontainer.devel |
|---|---|
| Organization | Centerline Computers, Inc |
| Message-ID | <07a801c65eac$320852f0$0202fea9@prosperity> |
> > I've been trying to wrestle with the Maven 2 build files and so far
> > Maven keeps winning.
> >
> >
> >
> > The problem appears to be only related to the multiproject builds.
> >
> >
> >
> > -PicoContainer Multiproject Build Works Fine
> >
> >
> >
> > -If I cd into each nanocontainer directory and manually use mvn install
> > for each component everything works fine.
> >
> >
> >
> > -Nanocontainer mutiproject build fails.
> >
> >
> >
> > I took a look into it and for some reason when doing a multiproject
> > build, the main container source is getting compiled into:
> >
> > *nanocontainer/target*
> >
> > while the test code is getting compiled into
> >
> > *nanocontainer/container/target*
> >
>
> Have you tried a mvn clean install?
>
> Can someone on Windows reproduce this problems?
Followup -- Just did a Clean install on a Powerbook G4 running OS X 10.3
trunk/nanocontainer$ mvn clean test
Same results, test case failure in ScriptedContainerBuilderFactoryTestCase
Here's the portion that is failing the test case:
ScriptedContainerBuilderFactoryTestCase: 49
File resource = new
File("src/test/org/nanocontainer/nanocontainer.groovy");
assertNotNull("Could not find script resource '+ TEST_SCRIPT_PATH +
'.", resource);
The problem is that using mvn test, the current working directory is always:
trunk/nanocontainer
instead of:
trunk/nanocontainer/container
So the code that depends on the current working directory be
trunk/nanocontainer/container fails.
-Mike