Did you define this packaging yourself ? What extension did you assign to it
?
If this is just 'jar', try dropping the type from the dependency.
Tom
On 10/4/06, Philippe Faes <[EMAIL PROTECTED]> wrote:
Dear all,
I have a project with two modules. One module has a non-standard
packaging, say :
<groupId>be.ugent.elis.designs</groupId>
<artifactId>simple-adder</artifactId>
<version>0.0.1-SNAPSHOT</version>
<name>Simple Adder Demo</name>
<packaging>foobar</packaging>
The other module wants to depend on this:
<dependency>
<groupId>be.ugent.elis.designs</groupId>
<artifactId>simple-adder</artifactId>
<version>0.0.1-SNAPSHOT</version>
<type>foobar</type>
</dependency>
If I build and install the first module and then the second by hand, all
works well.
The build _fails_ when I build the parent project, because it is missing
be.ugent.elis.designs:simple-adder:foobar:0.0.1-SNAPSHOT
Why doesn't maven figure out to build the other module first? How can I
help maven figuring that out?
thangs
--
ir. Philippe Faes
Ghent University - Department ELIS
Sint-Pietersnieuwstraat 41 -- B-9000 Gent
Tel:+32 9 264 95 25 - Fax:+32 9 264 35 94
http://www.elis.UGent.be/~pfaes
ON5DEU -- LPIC1 -- gpg-key:173720B6
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
