Hi Craig,
In short, yes.
I began plugin version 3.0 over a year ago on a Mercurial clone of the SVN repo used for the plugin up until 2.1.
I began a complete overhaul, and have addressed many of the outstanding issues against 2.1 but the wind changed at work and the 3.0 branch is broken.
I will endeavour over the weekend to get this admin stuff sorted and I will email this list with Mercurial repository details so you can pull your own clones.
I made this harder for myself I guess when I chose to move to Mercurial for its obvious benefits for accepting contibutions. Sadly CollabNet never supported it and java.net still doesn't as far as I know.
If people prefer Git I could always move to Git instead - it's all the same to me.
Backporting my bug fixes from 3.0 to 2.2 shouldn't be a problem. I'll get the repo in a better state for contribution first though.
Thanks for the interest.
Dave
On 27/08/2011, at 7:17 PM, Craig Davidson wrote:
> 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