On Wed, Nov 25, 2009 at 3:52 PM, Simon Laws <[email protected]> wrote: > On Wed, Nov 25, 2009 at 3:43 PM, ant elder <[email protected]> wrote: >> On Wed, Nov 25, 2009 at 3:16 PM, Simon Laws <[email protected]> >> wrote: >>>> The issue with doing that is that the contribution then gets included >>>> in the Tuscany runtime classpath and the Tuscany runtime gets included >>>> in the contribution classpath - so its not really properly testing how >>>> it would be used which leads to bugs. This is a real issue as while >>>> i'm working on all this domain and client stuff I keep coming across >>>> issues where things dont work properly as its only ever been tested >>>> with the contribution part of the system classpath. >>>> >>>> ...ant >>>> >>> >>> OK, fair point. We just then need a sample launcher project that >>> allows us and our users to easily run the samples from Eclipse in lieu >>> of us bringing up the Eclipse plugin. Even when we do I would argue >>> that it's useful for a user to be able to easily fire up a >>> contribution from the binary distribution without needing to further >>> configure their Eclipse environment. I guess we can debate that. In >>> the mean time though we do need an easy way to run sample >>> contributions during development. >>> >>> Simon >>> >> >> In r884146 I've added the maven tuscany plugin to the helloworld >> sample pom.xml so you can now run it with "mvn tuscany:run" >> >> You could also run it with the the launcher from the trunk >> distribution build by doing: >> >> ..\..\distribution\all\target\apache-tuscany-sca-all-2.0-SNAPSHOT.dir\tuscany-sca-2.0-SNAPSHOT\bin\tuscany.bat >> target\sample-helloworld.jar >> >> or more simply by first adding that to your environment path eg: >> >> set >> PATH=\Tuscany\trunk\distribution\all\target\apache-tuscany-sca-all-2.0-SNAPSHOT.dir\tuscany-sca-2.0-SNAPSHOT\bin;%PATH% >> >> and then you can run any sample with: >> >> tuscany target\sample-helloworld.jar > > nice > >> >> I'm not sure about Eclipse, ideally you would have some Eclipse plugin >> like the old Tuscany one or the STP one wouldnt you? (eg you can't run >> an webapp or ejb in eclipse without first installing some container >> plugin). > > +1 but we don't have it today > > If there's an itest for the sample like the >> itest-sample-helloworld one you can run that in eclipse, doesn't that >> do what you want or am i misunderstanding what you're suggesting? > > We can but a user of the distribution can't. I guess this comes down > to what we want to put on the TODO list for eclipse for 2.0. If we > agree to put the eclipse plugin on the list (or help the STP project > to get some support for 2.0 in the right kind of timeframe) then I > agree that's the right long term approach. If we can't do that then I > think we need to help the user out. > > I'd be happy to include either of those tasks. Ease of use should be > one of our objectives. As an aside, if we decide to go down the plugin > route in the first instance I think we can make it slicker now that we > have the registry in the runtime. > > Simon >
Interestingly according to the STP project planning page they're about to start trying to use our 2.x runtime - http://wiki.eclipse.org/STP/SCA_Project#Planning ...ant
