Rafael,
Ideally, support for multiple application servers (even AS 7) would be done by leveraging Arquillian's container adapters. You don't want to have to do all the work again of creating these adapters, so reuse is key. Arquillian's container adapters are not coupled to the Arquillian Core, so you can use them standalone.
There is a prototype of a maven plugin that supports any container with an Arquillian adapter here:
You'll likely just want to use this as a reference point when developing the forge plugin (you don't have to go through Maven).
Of course, you could also create a Forge plugin that simply configures the Arquillian Maven plugin. Feel free to experiment to figure out which approach is best.
-Dan
On Mon, Nov 5, 2012 at 6:09 AM, Rafael Soares
<rafaelcba@gmail.com> wrote:
Hello guys.
I'm a completely newbie Forge user. Looking on Forge plugins I was wondering how complex would be develop a plugin for Glassfish v3 AS.
I've cloned the jboss-as7 plugin from Github to look at the code and I could observe it uses the AS7 CLI API to interact with or manage the JBoss AS7. But I was wondering if would be possible to manage an AS using just it's Maven Plugin or a REST API (if provided by AS).
Many modern Application Servers, as JBossAS7, has Maven Plugin which supports basic management functions (start, stop, deploy, redeploy), and some others has REST Management APIs. So, I would like to know what do you think about use these kind of API to develop AS management plugins instead specific AS management API (like AS7 CLI API)?
Thanks.
________________________
Rafael Torres Coelho Soares
_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597