Peter, even now you shouldn't have to edit xml to add subsystems -- the
CLI can do that. The build split and associated tooling should make it
much easier to build up a server with the exact set of subsystems you
want, but you shouldn't be *forced* to edit xml even today.
On 6/19/14, 8:10 AM, Stuart Douglas wrote:
Yes, that is one of the goals of the build split. Eventually the
existing maven plugin will be split into a provisioning tool and a build
tool.
Stuart
Peter Cai wrote:
> Hi Stuart,
> Any plan to support dyanmic provisioning (i.e., one / a group of
> subsystems can be added via CLI rather than configuring subsystems
> in xml file before server started ) on Wildfly?
> Regards,
>
>
> On Wed, Jun 18, 2014 at 7:56 AM, Stuart Douglas
> <stuart.w.douglas(a)gmail.com <mailto:stuart.w.douglas@gmail.com>> wrote:
>
> I have created a wiki doc with details of the new build process. This
> document will be updated as work progresses.
>
>
https://community.jboss.org/wiki/WildflyBuildProcess
>
> Stuart
>
> Stuart Douglas wrote:
> > Hi all,
> >
> > The first patch of many for the build split has been merged. This
> > introduces a few changes, the most obvious of which is that the
> server
> > that is produced in the build dir is now a 'thin' server, that
> uses jars
> > directly from the local maven directory, and the full traditional
> server
> > is now built in the 'dist' directory.
> >
> >
> > Stuart
> >
> >
> > _______________________________________________
> > wildfly-dev mailing list
> > wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
> >
https://lists.jboss.org/mailman/listinfo/wildfly-dev
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev