I'm researching it today (can't promise a solution, but will try).  I belive you use activation profiles which allow inclusion of custom properties. I've never used them before, but will see if I can plug through it.  Unfortunately, I've found that M2's documentation on this type of fringe stuff is just a little bit better than our own! :)  Maybe we can help both projects by working through this.

I might refactor things in the plugin a little bit.  What do you think about the following:

1) any dir specified on the command line (-Dpluto.installDir=blah) takes precedence over everything
2) look at the settings.xml file and use the prop set there
3) use default -- or should there be no default and a nice error message?


David

On 10/25/05, Craig Doremus <[EMAIL PROTECTED]> wrote:
Hi David:

>
> I think probably the biggest gotcha is that by default it deploys to a
> directory called "pluto-tomcat" which it assumes is a child dir of
> your <pluto-home>.  This is configurable in settings.xml (according to
> maven's site).
>
I could not find out how to set the installationDirectory element in
pluto-util/pom.xml using settings.xml, so I modified this file directly
to get the automated deployment to work. Do you know how to use
settings.xml to set the installationDirectory element?

TIA
/Craig

Reply via email to