Simon Laws wrote:
I was talking offline to the other Simon about how to import existing
projects into Eclipse. Looking at the docs I realized that we talk
about how to use Eclipse when starting from scratch but don't say much
about how to use Eclipse with existing projects. I had a go at putting
some instructions together in 1.x [1]. If anyone has any suggesting
for improvements please feel free.
Once they settle down we can add/link similar info to the 2.x site.
[1]
http://tuscany.apache.org/import-existing-tuscany-sca-projects-into-eclipse.html
Simon
The maven-based instructions on this web page work fine for importing
the Tuscany SCA samples into Eclipse. However I'm finding it difficult
to debug the Tuscany runtime with this setup.
The problem is that each imported sample project has a list of dependencies
pointing to tuscany-xxx jar files in my local maven repository (M2_REPO).
Eclipse doesn't know the location of the source code for these jar files,
so I can't view the source and set debug breakpoints within Tuscany
runtime code.
I found a very painful workaround by selecting one particular dependent
jar that I wanted to debug and doing an Eclipse source attachment for
that specific jar only. This worked but I shudder at the thought of
having to repeat this manual source attachment for dozens of dependent
jars in dozens of samples.
Is there a simple convenient way to tell Eclipse that all the dependent
jars in the M2_REPO/org/apache/tuscany/sca/xxx path have their source in
the Tuscany source distribution zip file?
Simon
