On 30 June 2011 00:18, ant elder <antel...@apache.org> wrote: > On Wed, Jun 29, 2011 at 7:24 PM, Amindri Udugala > <amindriudug...@gmail.com> wrote: > > > > > > On 29 June 2011 23:43, Amindri Udugala <amindriudug...@gmail.com> wrote: > >> > >> > >> On 29 June 2011 10:47, ant elder <ant.el...@gmail.com> wrote: > >>> > >>> On Tue, Jun 28, 2011 at 5:32 PM, Amindri Udugala > >>> <amindriudug...@gmail.com> wrote: > >>> > Hi all, > >>> > > >>> > I feel that running a test case would not help me as I need Tuscany > to > >>> > run > >>> > continuously, to observe MBeans via the Jconsole. When the process > >>> > exits it > >>> > is also disconnected from the Jconsole. Somehow my requirement is to > >>> > bootstrap tuscany along with the modules I have created. > >>> > > >>> > >>> One way you can run Tuscany continuously is using the Tuscany Shell > >>> which you can start with things like the .bat / .sh scripts in the > >>> binary distribution bin folder or with Maven using the Tuscany maven > >>> plugin. For example, if you do svn co > >>> > >>> > https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/helloworld/ > , > >>> cd helloworld, mvn tuscany:run, that should start up the interactive > >>> shell. You should be able to get that to include your modules by > >>> adding <dependencies> to the Tuscany maven <plugin> definition in the > >>> helloworld pom.xml. > >> > >> Hi, > > > > Sorry for the previous mail > >> > >> Thanx for the advice.. > >> from what I understood, I need to add two dependencies in the <plugin>. > >> One dependency is for core spi (as the arifacts to be monitored are > defined > >> here) and the other other dependency for jmx-activator module which I > >> created. > >> So finally the <plugins> helloworld pom.xml would look like follows. > > > > > >> > >> <plugins> > >> > >> <plugin> > >> <groupId>org.apache.tuscany.sca</groupId> > >> <artifactId>tuscany-maven-plugin</artifactId> > >> <version>${tuscany.version}</version> > >> </plugin> > >> > >> <plugin> > >> > >> <groupId>org.apache.tuscany.sca</groupId> > >> <artifactId>tuscany-core-spi</artifactId> > >> <version>2.0-SNAPSHOT</version> > >> </plugin> > >> > >> > > > > <plugin> > > <groupId>org.apache.tuscany. > > sca</groupId> > > <artifactId>tuscany-jmx-activator</artifactId> > > <version>2.0SNAPSHOT</version> > > </plugin> > > > > </plugins> > > > > Then finally run mvn tuscany:run to bootstrap tuscany. Did I get it > right? > > If not please correct me.. > > > Thanks for the explanation. I understand this clearly now. > I wasn't clear if you've changed the core-spi module, if so then > you'll need to rebuild the the plugin to pick that up.
Yes I did changed the core-spi pom.xml and added also added a new package. So i will need to rebuild the plugin. > Otherwise, the > <dependencies> element can go within the <plugin> and you don't need > to specify the core-spi module as its already defined in the plugin, > so that gives: > > <plugins> > <plugin> > <groupId>org.apache.tuscany.sca</groupId> > <artifactId>tuscany-maven-plugin</artifactId> > <version>2.0SNAPSHOT</version> > <dependencies> > <dependency> > <groupId>org.apache.tuscany.sca</groupId> > <artifactId>tuscany-jmx</artifactId> > <version>2.0SNAPSHOT</version> > </dependency> > <dependency> > <groupId>org.apache.tuscany.sca</groupId> > <artifactId>tuscany-jmx-activator</artifactId> > <version>2.0SNAPSHOT</version> > </dependency> > </dependencies> > </plugin> > </plugins> > > ...ant > -- Thanks Amindri Udugala University of Colombo School of Computing, Sri Lanka.
