The problem I encountered was when you want to debug through otests and go down into and edit the SCA code and you have 2 separate hierarchies. If you have done mvn eclipse:eclipse independently on the 2 hierarchies, then the SCA dependencies of the otests are fulfilled in eclipse by the class/source jars in your maven repo. The SCA source is therefore readonly. I created myself a local uber-pom, sitting above my SCA and Oasis extractions. I then ran mvn eclipse:eclipse from this top level, and now all the oasis eclipse projects have dependencies on the eclipse Tuscany projects.
Kelvin. On Wed, Jun 23, 2010 at 11:48 AM, ant elder <[email protected]> wrote: > On Wed, Jun 23, 2010 at 11:14 AM, Simon Laws <[email protected]> > wrote: >> On Wed, Jun 23, 2010 at 10:55 AM, ant elder <[email protected]> wrote: >>> On Tue, Jun 22, 2010 at 3:20 PM, kelvin goodson >>> <[email protected]> wrote: >>>> 6.5 minutes for me to build the source jars with mvn -Psource >>>> >>> >>> That command doesn't rebuild the classes jars so the 6.5 minutes >>> includes all the overhead of running maven as well as building the >>> source jars. When i try several times mvn clean install with/without >>> -Psource in the modules folder I get: >>> >>> 15 minutes 51 seconds >>> 12 minutes 55 seconds with source >>> 8 minutes 17 seconds >>> 9 minutes 2 seconds with source >>> 8 minutes 14 seconds >>> 8 minutes 37 seconds with source >>> >>> (I guess theres some caching going on is why the time keeps reducing) >>> Anyway, i think that shows there's not so much extra overhead in >>> building the source jars and as its quite confusing with them getting >>> out of sync i think we should change to always build them, so i'll do >>> that unless someone has a good reason not to. >>> >>> ...ant >>> >> >> What's the impact on editing in Eclipse if the source jar is found. >> Does it cause problems? >> > > It seems ok as far as i can tell. Is there something specific you're > thinking might be a problem? > > ...ant >
