If you build the whole source tree at once, the problem should not appear.
Recently, I have tried to upload new snapshots, but the process failed
with the same kind of error you mentionned. :(
However it seems to work build running "mvn install" instead.
Cheers,
Guillaume Nodet
On 7/27/06, Renaud Bruyeron <[EMAIL PROTECTED]> wrote:
I've been trying to build from source (from trunk) for a couple of days,
and every day I run into the same issue with the servicemix-common
artifact on the mvn2 repos:
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.servicemix:servicemix-common:jar:3.0-incubating-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.servicemix
-DartifactId=servicemix-common \
-Dversion=3.0-incubating-20060726.220305-4 -Dpackaging=jar
-Dfile=/path/to/file
Path to dependency:
1)
org.apache.servicemix:servicemix-jms:jbi-component:3.0-incubating-SNAPSHOT
2)
org.apache.servicemix:servicemix-soap:jar:3.0-incubating-SNAPSHOT
3)
org.apache.servicemix:servicemix-common:jar:3.0-incubating-20060726.220305-4
If I look into the mvn2 repo on
http://people.apache.org/maven-snapshot-repository/, I see this jar:
servicemix-common-3.0-incubating-20060726.220305-5.jar
For all the other modules, I see jars with 20060726.220305-4. Why the
discrepancy?
I had the same issue yesterday with servicemix-common as well: all the
other modules were ok, but servicemix-common had its time stamp shifted
by one as well in the repo.
Anyone else having the problem? I have to download
servicemix-common-3.0-incubating-20060726.220305-5.jar and install it as
20060726.220305-4 like mvn tells me to do to be able to build
servicemix, which seems weird to me.
- Renaud
--
Cheers,
Guillaume Nodet
