Thanks Ivan. That was the issue.
I attempted to deploy a new set of snapshots for server trunk but for
some reason hit an OOM heap error when it reached the assemblies - so
most of the snapshots are fresh as of this morning (at least all of
those that I needed).
Joe
Ivan wrote:
I suggest you build and install the car-maven-plugin in your own
machine, I think the one downloaded from the website is out of date.
2009/7/14 Joe Bohn <[email protected] <mailto:[email protected]>>
Hmmm ... I replied too soon. That solved the issue with the
car-maven-plugin and now I'm on to the next issue ... a missing
dependency on
org.apache.openejb/ejb31-api-experimental/3.1.2-20090618.052142-3/jar
Joe
Joe Bohn wrote:
I gave that a shot but it had the same results ... however when
I just cleaned out my local repo yet again it worked! There
must have been some residual junk left from the previous attempt.
Thanks!
Joe
David Jencks wrote:
Have you tried including apache.snapshots (or whatever its
called) as a plugin repository?
thanks
david jencks
On Jul 13, 2009, at 3:11 PM, Joe Bohn wrote:
I'm trying to update Daytrader trunk to keep up with the
changes in server trunk. To that end I recently updated
it to use genesis 2.0 and therefore the latest in terms
of repositories and nexus found in genesis.
However, I still can't build Daytrader without first
building Geronimo trunk.
The problem that I'm currently hitting is with the
car-maven-plugin. If I don't include any repositories
in my root pom (similar to server trunk) then I get the
following error:
Downloading:
http://repository.apache.org/snapshots/org/apache/geronimo/buildsupport/car-maven-plugin/2.2-SNAPSHOT/car-maven-plugin-2.2-SNAPSHOT.pom
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: org.apache.geronimo.buildsupport
ArtifactId: car-maven-plugin
Version: 2.2-SNAPSHOT
Reason: Unable to download the artifact from any
repository
org.apache.geronimo.buildsupport:car-maven-plugin:pom:2.2-SNAPSHOT
from the specified remote repositories:
ibiblio.org <http://ibiblio.org>
(http://mirrors.ibiblio.org/pub/mirrors/maven2),
codehaus.snapshots
(http://snapshots.repository.codehaus.org),
apache.snapshots
(http://repository.apache.org/snapshots)
Note that it is failing to find the pom for the plugin
and it didn't even look in the nexus repo (which I had
just removed a few minutes earlier to match the server
trunk).
If I add the nexus repo back in I get a slightly
different error ... but it still doesn't find the plugin:
Downloading:
http://snapshots.repository.codehaus.org/org/apache/geronimo/buildsupport/car-maven-plugin/2.2-SNAPSHOT/car-maven-plugin-2.2-SNAPSHOT.jar
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Plugin could not be found - check that the goal
name is correct: Unable to download the artifact from
any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file
-DgroupId=org.apache.geronimo.buildsupport
-DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT
-Dpackaging=maven-plugin -Dfile=/path/to/file
Alternatively, if you host your own repository you can
deploy the file there:
mvn deploy:deploy-file
-DgroupId=org.apache.geronimo.buildsupport
-DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT
-Dpackaging=maven-plugin -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]
org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT
from the specified remote repositories:
ibiblio.org <http://ibiblio.org>
(http://mirrors.ibiblio.org/pub/mirrors/maven2),
codehaus.snapshots
(http://snapshots.repository.codehaus.org),
apache.snapshots
(http://people.apache.org/repo/m2-snapshot-repository)
This time it looks like it must have found the pom and
is attempting to download the jar but for some reason it
once again isn't looking for the jar in the nexus repo.
I recall that there is something special about the
loading of maven plugins that doesn't follow the typical
dependency resolution. Any ideas on what I need to do
to get around this? I'd really like for us to be able
to build other dependent projects without having to
build server trunk first.
Thanks,
Joe
--
Ivan
