As at 2.1 the plugin requires asadmin in order to function. Despite
the ability to network deploy to glassfish and configure a remote
domain using JMX, one major aim of the maven-glassfish-plugin is to
manage creation of domains in the developer's development cycle. In
order to achieve this with remote glassfish installations requires
some form of RPC shell wrapper such as SSH. This was planned for 2.1
but has been back burnered as too few people would find this feature
useful.
So I think the short answer is that the current version of the plugin
is only useful in working with a local glassfish installation via
asadmin.
In order to do this you need to supply the glassfish installation root
(glassfishDirectory) so the plugin can find the asadmin command.
I'd be interested to know more about your intended usage as it seems
to involve a glassfish which is remote to your build environment.
Dave
On 24/09/2008, at 9:28 AM, frenchdrip_at_spamex.com wrote:
> The glassfishDirectory is documented as being required. Does this
> mean I need to create a network file share to my Glassfish directory
> on the server I'm deploying to? Should the glassfishDirectory be a
> UNC path?
>
> How is the Glassfish Maven plug-in communicating with the server
> anyhow? Through asadmin or via the file system?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_maven-glassfish-plugin.dev.java.net
> For additional commands, e-mail: users-help_at_maven-glassfish-plugin.dev.java.net
>