Le 12 juin 2013 à 08:59, Heiko Braun <hbraun(a)redhat.com&gt; a écrit : > > I am looking for some documentation on the PRD layering (EAP 6.1) is supposed to work. Can someone point me into the right direction? this one? https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganiz... jeff -- Jeff Mesnil JBoss, a division of Red Hat http://jmesnil.net/

On 6/12/13 3:54 AM, Heiko Braun wrote: > yes, I was looking at that. But is it applicable to EAP 6.1 ? Yes. AS 7.2.0.Final and EAP 6.1 are structured as described in that doc and the included jboss-modules version does module loading as described. > Any differences to wildfly master? Not at this point. Emanuel is considering changing the location of where some patching related metadata is stored, but that would only be relevant to an end-user who was trying to use symlinks to share module roots across installations. And patching's not in master yet.

> > On Jun 12, 2013, at 9:05 AM, Jeff Mesnil <jmesnil(a)redhat.com&gt; wrote: > >> >> Le 12 juin 2013 à 08:59, Heiko Braun <hbraun(a)redhat.com&gt; a écrit : >>> >>> I am looking for some documentation on the PRD layering (EAP 6.1) is supposed to work. Can someone point me into the right direction? >> >> this one? https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganiz... >> >> jeff >> >> -- >> Jeff Mesnil >> JBoss, a division of Red Hat >> http://jmesnil.net/ >> > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev >

This is the issue Emanuel mentioned: https://issues.jboss.org/browse/WFLY-1505 We tried to install the console as a layer, but using product.conf at the same time. It seems that, when product.conf is given, the actual layer is ignored and the console always be pulled from the "base" directories. (But that's something you guys need to confirm. ) However this raises the question, if product.conf is actually needed anymore to replace the console if we start installing it as a layer. We've tested it on wildfly master, and just using the layer approach seems to work fine. But it's not clear to me, if this intented to be used this way. Regards, Heiko On Jun 12, 2013, at 5:38 PM, Emanuel Muckenhuber <emuckenh(a)redhat.com <mailto:emuckenh@redhat.com>> wrote: > I was talking to Heiko before and turns out the issue was that when > installing the console as a new layer, it did not pick up the changes in > EAP, because product.conf was overriding the console slot. _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev