dev@maven-glassfish-plugin.java.net

Re: Glassfish Maven 2 Plugin

From: Craig Davidson <craig_at_cd15.co.uk>
Date: Sat, 27 Aug 2011 10:17:41 +0100

Hi Dave,

I totally understand and appreciate your situation with work and other
priorities. I am however interested in contributing to the project and would
be keen to look into what you have suggested as this would be a welcome
addition to the plugin to allow the administration of a glassfish server
without the reliance on the asadmin CLI.

Is your thoughts to have the plugin using the REST API aswell as the asadmin
utility so the new version would be compatible with both v2 and v3 or do you
think it would be worth while making a 2.2 release addressing some
outstanding issues that will use the asadmin CLI for v2 and v3 and
concentrate on purely the REST API for Glassfish v3 on version 3.0 for
the plugin as the demand for glassfish v2 will surely decline?

Thanks,
Craig





On 25 August 2011 00:13, Dave Whitla <dave.whitla_at_ocean.net.au> wrote:

> Hi Craig,
>
> While I really want to be actively working on this right now, my employer
> will not allow me work time on it at the moment and I have too much on my
> plate outside work. The plan for remote management was to use the ws API in
> GFv3. Adding such functionality for v2 cannot be done in a cross-platform
> way without massive effort or forcing some users to install dependencies.
> would you mind playing with the API approach and getting back to me?
>
> Dave
>
>
> On 25/08/2011, at 3:49 AM, Craig Davidson <craig_at_cd15.co.uk> wrote:
>
> Hi folks,
>
> Sorry to have to drop you an email but I was looking for some information
> regarding the roadmap for maven glassfish plugin and whether or not there is
> any plans for the next release and the changes that will be sucked into
> that.
>
> I raised the issueMAVEN_GLASSFISH_PLUGIN-3<http://java.net/jira/browse/MAVEN_GLASSFISH_PLUGIN-3>but
> after further thought into the matter I think the deployment commands in
> general need further refinement as the deploy command starts the domain if
> it doesn't exist (this wont work on remote instances), the undeploy checks
> is the domain exists locally (which doesnt work for remote instances) and
> the redeploy doesn't check if the domain is running or not.
>
> 3 very similar commands which have been delivered differently. Is there
> room for this to be standardised by checking the domain is running and then
> performing the required command?
>
> Would be interested in hearing your thoughts on this and whether there will
> be a new release coming. For the time being i'll be running my own version
> of the plugin with the above changes and including the
> MAVEN_GLASSFISH_PLUGIN-5<http://java.net/jira/browse/MAVEN_GLASSFISH_PLUGIN-5>
> issue.
>
> Thanks in advance,
> Craig
>
>