If it happens on 7.2 prerelease tag than it happens also on current master
(one commit difference)
I also doubt OOTB build has this problems, as on vanilla build it logs no
warning.
but it might happen when user installs new jsf modules
--
tomaz
On Wed, Feb 13, 2013 at 2:36 PM, <ssilvert(a)redhat.com> wrote:
That's quite possible. I'm looking at it now. According to
the posts,
this only happens on the 7.2 prerelease? Builds before and after that
point don't get the warning?
On 2/13/2013 8:19 AM, Jaikiran Pai wrote:
> A user just reported a potential problem with the multi-JSF feature and
> the recent changes to the module loading, w.r.t the layered
> distributions architecture [2]. The
> org.jboss.as.jsf.deployment.JSFModuleIdFactory [3] relies on the
> module.path filesystem path to find the JSF modules. Reading through the
> layered distributions architecture and the goals of the new filesystem
> layout for modules, I think the multi-JSF feature design itself might
> need a relook in terms of how the users add those modules, right?
>
>
> [1]
https://community.jboss.org/thread/221254?tstart=0
> [2]
>
https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganiz...
> [3]
>
https://github.com/jbossas/jboss-as/blob/master/jsf/subsystem/src/main/ja...
> [4]
https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature
>
> -Jaikiran
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev