<html><body><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000"><div>Yes: <br></div><div><a href="https://developer.jboss.org/wiki/WildflyProvisioning">https://developer.jboss.org/wiki/WildflyProvisioning</a></div><div><br></div><div>-Bilge<br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Emmanuel Bernard" <emmanuel@hibernate.org><br><b>To: </b>"Jason Greene" <jason.greene@redhat.com><br><b>Cc: </b>wildfly-dev@lists.jboss.org<br><b>Sent: </b>Thursday, October 9, 2014 7:27:39 AM<br><b>Subject: </b>Re: [wildfly-dev] Deliver 3rd party subsystem to customers?<br><div><br></div>I'm interested in that kind of ability as well.<br>Is there a wiki describing the what and how I could lurke and contribute<br>on the use cases side?<br><div><br></div>Emmanuel<br><div><br></div>On Mon 2014-09-29 11:56, Jason Greene wrote:<br>> Yeah this is a key goal of features.<br>> <br>> You can do something like "feature install org.blah.feature”, and it fetches it from maven and installs it.<br>> <br>> On Sep 29, 2014, at 11:42 AM, Brian Stansberry <brian.stansberry@redhat.com> wrote:<br>> <br>> > Agreed. I see feature-packs as the best solution to this kind of thing.<br>> > <br>> > CLI archives are another possibility, with the archive bundling the <br>> > module and then the script executes to install it and make needed mods, <br>> > but my instinct is the feature-pack stuff will end up being a better <br>> > approach.<br>> > <br>> > On 9/29/14, 11:30 AM, Heiko Braun wrote:<br>> >> I think the recently added feature packs work that way. Stuart wrote about that last week: http://lists.jboss.org/pipermail/wildfly-dev/2014-September/002919.html<br>> >> <br>> >> <br>> >> <br>> >> <br>> >> <br>> >> <br>> >>> Am 29.09.2014 um 13:36 schrieb "Heiko W.Rupp" <hrupp@redhat.com>:<br>> >>> <br>> >>> Hey,<br>> >>> <br>> >>> suppose I am writing a subsystem for WildFly, that I can or want not add to the generic WildFly codebase (e.g. because it is not open source or because WildFly team would consider it too special for general consumption).<br>> >>> <br>> >>> Is there a way to package that up in a .zip or any other format (in the good 'ol days we used .shar files :-)<br>> >>> to deliver such a subsystem with its module but also the xsl to modify standalone.xml (or similar)?<br>> >>> <br>> >>> If not (yet), would it make sense for WildFly to reconsider allowing to provide e.g.<br>> >>> * ext.xml<br>> >>> * subsystem.xml<br>> >>> * ports.xml<br>> >>> <br>> >>> that will get merged / added to standalone.xml when the module is loaded for the very first time<br>> >>> (like when the module.jar is also indexed for the first time).<br>> >>> <br>> >>> Thanks<br>> >>> Heiko<br>> >>> <br>> >>> <br>> >>> _______________________________________________<br>> >>> wildfly-dev mailing list<br>> >>> wildfly-dev@lists.jboss.org<br>> >>> https://lists.jboss.org/mailman/listinfo/wildfly-dev<br>> >> <br>> >> _______________________________________________<br>> >> wildfly-dev mailing list<br>> >> wildfly-dev@lists.jboss.org<br>> >> https://lists.jboss.org/mailman/listinfo/wildfly-dev<br>> >> <br>> > <br>> > <br>> > -- <br>> > Brian Stansberry<br>> > Senior Principal Software Engineer<br>> > JBoss by Red Hat<br>> > _______________________________________________<br>> > wildfly-dev mailing list<br>> > wildfly-dev@lists.jboss.org<br>> > https://lists.jboss.org/mailman/listinfo/wildfly-dev<br>> <br>> --<br>> Jason T. Greene<br>> WildFly Lead / JBoss EAP Platform Architect<br>> JBoss, a division of Red Hat<br>> <br>> <br>> _______________________________________________<br>> wildfly-dev mailing list<br>> wildfly-dev@lists.jboss.org<br>> https://lists.jboss.org/mailman/listinfo/wildfly-dev<br>_______________________________________________<br>wildfly-dev mailing list<br>wildfly-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/wildfly-dev</blockquote><div><br></div></div></body></html>