I think the plugin should be a separate project to it's not tied
to the
same release cycle. There's already a groupId of org.wildfly.plugins
where the wildfly-maven-plugin exists. Maybe it should use the same groupId.
This would also allow other projects to use the plugin sooner and start
to assemble their own runtime. It might help determine some issues
quicker as well.
I agree, although initially I want to keep it in the WF code base, just
so we do not need to do a new release every day while it is evolving
rapidly.
Overall I think this plan is great. I personally can't wait until
we at
least have a true core server to use.
FWIW IBM uses the term "feature pack" for WebSphere Application Server
extras. Though they tend to be huge and not easy to apply.
If anyone has any better names I would love to hear them.
Stuart
>
>
>
>
>
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev