Paul Tomsic wrote:
i've just grabbed tuscany from svn and i'm now
receiving a build failure when i do the following.
thoughts/help appreciated.
thx


[ptomsic] java > pwd
/Users/tomsicp/projects/tuscany/java
[ptomsic] java > uname -a
Darwin ptomsic.local 8.6.0 Darwin Kernel Version
8.6.0: Tue Mar  7 16:58:48 PST 2006;
root:xnu-792.6.70.obj~1/RELEASE_PPC Power Macintosh
powerpc
[ptomsic] java > mvn -version
Maven version: 2.0.4
[ptomsic] java > mvn
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: org.apache.tuscany.samples.das
ArtifactId: das-samples
Version: SNAPSHOT

Reason: Unable to download the artifact from any
repository

org.apache.tuscany.samples.das:das-samples:pom:SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException:
Cannot find parent:
org.apache.tuscany.samples.das:das-samples for
project: null:sample-companyweb:war:SNAPSHOT
        at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
        at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
        at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)


Paul,

Thanks for reporting this build failure. I created JIRA issue http://issues.apache.org/jira/browse/TUSCANY-369 to help you track its resolution. The problem is that samples have been moving around and we didn't detect the build break because we had the old cached samples in our local Maven repos.

Committers, to avoid this kind of break in the future, after moving projects around you should do a top Maven build after having deleted your ~/.m2/repository/org/apache/tuscany directory, to avoid picking up old artifacts, and ensure that the build is successful for somebody starting from scratch with a fresh local Maven repos. Thanks.

I was able to reproduce the problem and will commit a fix in a few minutes. Thanks again for reporting this...

--
Jean-Sebastien

Reply via email to