You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org> on 2006/05/14 20:15:06 UTC
[jira] Resolved: (TUSCANY-369) Build break - failed to resolve
artifact das-samples
[ http://issues.apache.org/jira/browse/TUSCANY-369?page=all ]
Jean-Sebastien Delfino resolved TUSCANY-369:
--------------------------------------------
Resolution: Fixed
Fixed in 406394. Fixed the pom.xml causing the build failure.
> Build break - failed to resolve artifact das-samples
> ----------------------------------------------------
>
> Key: TUSCANY-369
> URL: http://issues.apache.org/jira/browse/TUSCANY-369
> Project: Tuscany
> Type: Bug
> Components: Build System, Java SCA Samples, Java DAS Samples
> Versions: Java-M1
> Reporter: Jean-Sebastien Delfino
> Assignee: Jean-Sebastien Delfino
> Priority: Blocker
> Fix For: Java-M1
>
> Build failure, reported by Paul Tomsic. Paul Thanks for reporting this issue.
> Details are available at http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200605.mbox/%3c20060514160355.40525.qmail@web53608.mail.yahoo.com%3e
> The problem is that samples have been moving around and nobody detected this issue until now I guess because we all had the old samples with the old group and artifact ids cached in our Maven repos.
> We need to remember this in the future: after moving projects around, everybody should do a complte tob build after having deleted their .m2/repository/org/apache/tuscany directory to make sure that the build still works for somebody starting from scratch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira