I'm fine to see my changes reverted if you are able get a sucessful tools build with a clean maven repo (removing .m2\repository\org\apache\tuscany).
On Mon, Oct 27, 2008 at 7:55 PM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > Luciano Resende wrote: >> >> Let me see if I can clearly explain the issue : in the sca-pom, when >> you defined the maven-compiler-plugin, you had a dependency on >> tuscany-maven-eclipse-compiler, this kind made maven try to build the >> tuscany-maven-eclipse-compiler with a dependency on itself..... > > Are you sure? Here is the maven-eclipse-compiler's POM: > http://svn.apache.org/repos/asf/tuscany/branches/sca-equinox/tools/maven/maven-eclipse-compiler/pom.xml > > I may have missed something but I had customized it to avoid that kind of > circular dependency (it has a different parent POM). > > This >> >> issue would only happen if you don't have the maven-eclipse-compiler >> in your local repo, and that was probably why you didn't see the >> issue. >> >> Anyway, were you thinking to use this to all modules (e.g modules, >> samples, itest, etc ?), or is it ok to have it in the tuscany modules >> (a.k.a sca/modules) only ? > > I am happily using it for all modules (as it's much faster and lighter, more > flexible wrt error reporting and can be made OSGi-aware). > > -- > Jean-Sebastien > -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
