Just as a follow up to anyone that wants to follow I created a JIRA for
this
https://issues.jboss.org/browse/WFMP-41. I've got a big chunk of the
refactor done. I just need to document it and probably make it a little
more user friendly.
On Wed, Jun 1, 2016 at 5:29 PM, James Perkins <jperkins(a)redhat.com> wrote:
Hello All,
I've been asked a few times about creating a WildFly Plugin Core project
with some of the utilities from the wildfly-maven-plugin. Since it came up
twice today alone I'm wondering if we should have a separate
wildfly-plugin-core project.
This would be useful if we wanted to have a Gradle or SBT plugin as well.
Maybe it's useful for JBoss Tools too. WildFly Arquillian could use it too.
The idea would be to separate out the code that creates the deployment
operations as well as the code that creates and launches a container
process (maybe). Also expose of the helper stuff done to check the status
of a sever, get all the server groups of a managed domain, etc. It would
probably be fairly small overall. Essentially just some utilities that
create some common operations so consumers don't need to know how the
operation needs to be constructed.
If it sounds reasonable the next step would be to determine if it should
be it's own project or just a maven module in the wildfly-maven-plugin. The
only reason I'd lean towards it's own project is to keep the release stream
separate from the wildfly-maven-plugin.
Thoughts?
--
James R. Perkins
JBoss by Red Hat
--
James R. Perkins
JBoss by Red Hat