>From: "Craig McClanahan" <[EMAIL PROTECTED]>
>
> On 6/15/06, Gary VanMatre wrote:
> >
> > >From: "Wendy Smoak"
> > >
> > > On 6/15/06, Gary VanMatre wrote:
> > >
> > > > My second attempt was to add the cargo.jvmarg to the /shale-apps
> > pom.xml:
> > > >
> > > >
> > >>
> > > > ${artifactId}
> > > >
> > > >
> > > > org.codehaus.cargo
> > >> cargo-maven2-plugin
> > ...
> > >>
> > >> -Xdebug
> > -Xrunjdwp:server=y,transport=dt_socket,address=8000,suspend=n
> > >>
> > >
> > > Gary, this worked perfectly for me (with JSwat). Thanks! This has
> > > been on my "figure out how to..." list for a while now.
> > >
> > > (Be sure to 'mvn install' once from the top to make sure your pom
> > > changes get into your local repository.)
> > >
> >
> > Yeah, I finally got it to work too but I had to add it to the
> > shale-clay-usecases pom.xml. I thought that I tried the install at the
> > shale-apps level. So the inheritance must not be dymamic for all the sub
> > pom's. The parent pushes it's config to the child?
> >
> > But, I added those command to my maven notes.
> >
> > >>side: 'mvn help:effective-pom' will show you what's in effect,
> > l>>ewise 'mvn help:active-profiles' will show you which profiles are
> >
> >
> > I was going to commit this jvmargs setting to the shale-clay-usecases's
> > pom but what do you think about moving it up to shale-apps so we wouldn't
> > have to think about it again?
>
>
> If it really does work for all the apps, I'm definitely +1 on putting this
> in shale-apps-parent.
>
This tomcat debug setting seems to work for all the shale-apps projects. I
modified the shale-apps
pom.
Gary
> > --
> > > Wendy
> > >
> >
> > Gary
>
>
> Craig
