I have the same problem. The ear project seems to look for a jar of my war,
instead of the war...
did you get anywhere?
foo.bar:FOOBARWebApp:jar:1.0-SNAPSHOT
note the jar, not war...?
teknokrat wrote:
I have a multiproject that builds an ear file out of a war and a sar. It
is virtually
Nearly two seconds after I posted this, I took a closer look at the j2ee
archetype - maven-archetype-j2ee-simple
and found the type/type config param for dependancies, and thus modified
my EAR pom to show:
dependencies
dependency
On 6/14/06, teknokrat [EMAIL PROTECTED] wrote:
I have a multiproject that builds an ear file out of a war and a sar. It
is virtually identical to the j2ee project in the book. I have gone into
each directory and called mvn install. This has worked in the sar and
web directories. I checked my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
[INFO] Scanning for projects...
[INFO]
[INFO] Building Provisioning System Enterprise Application
[INFO]task-segment: [install]
[INFO]
Thorsten Heit wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
[INFO] Scanning for projects...
[INFO]
[INFO] Building Provisioning System Enterprise Application
[INFO]task-segment: [install]
[INFO]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
No you don't understand. The files are in my local repository already.
They are not on ibiblio. I have no idea why maven insists on looking
there. This is a purely local project.
Erm, yes, haven't read it (OutOfCoffeeException...) ;-)
Does
wish someone with more maven 2 knowledge could repair these issues.
-Original Message-
From: Thorsten Heit [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 10:01 AM
To: Maven Users List
Subject: Re: whats going wrong with my build?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thorsten Heit wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
No you don't understand. The files are in my local repository already.
They are not on ibiblio. I have no idea why maven insists on looking
there. This is a purely local project.
Erm, yes, haven't read it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Does your repository contain the corresponding pom for your war file?
AFAIK Maven checks the central repository if the pom files do not exist
in your repo, therefore the warning(s)...
yes, its in there. whats really strange is that the war