I just had that problem the other day ;-)
Maven is trying to find the dependencies in the repository and - unless you put something there - it won't find them.
You could try maven multiproject:install
which installs your artifacts into the local repository thus making them available to other modules.
I use snapshot dependencies maven multiproject:install-snapshot
and specify the snapshot as the desired version in my project.xml.
Hoppas det hj�lper!
God Jul!
/Mikael
[EMAIL PROTECTED] wrote:
Continuing on the discussion driven by Nicolas;
I'm testing out Maven on three of our sub-components with the following dependencies:
axxbs -> mediator -> common
(where the notation "a -> " means "a depends on b").
The directory layout is: <root> +- common | +- src | +- src_test +- axxbs | +...(as above) +- mediator
I've set up a common "maven.xml" which compiles the JARs without unit testing them and
installs the JARs into the local repository.
The maven.xml is copied into the each of the components directories.
The dependency sections for each component are:
common: No dependency to inhouse components:
axxbs: <dependency> <groupId>axxcommon</groupId> <artifactId>common</artifactId> <jar>common.jar</jar> <url>the build</url> </dependency>
mediator <dependency> <groupId>axxcommon</groupId> <artifactId>common</artifactId> <jar>common.jar</jar> <url>Thou shalt built!</url> </dependency>
<dependency> <groupId>axxtmn</groupId> <artifactId>axxbs</artifactId> <jar>common.jar</jar> <url>Thou shalt built!</url> </dependency>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
