Details
-
Feature Request
-
Resolution: Done
-
Major
-
8.0.0.Alpha3
-
None
Description
For each Multi-JSF implementation you want to add to WildFly, you must precisely configure modules.xml files for several modules. To make this easier, we have a Maven project that creates a CLI Deployment archive (installer) for a JSF version/WildFly version combination. See https://community.jboss.org/wiki/DesignOfWildFlyMulti-JSFFeature
Currently, the Maven projects that creates the installer lives in my GitHub at https://github.com/ssilvert/jboss-jsf-installer. However, this is not a good place for it long term, and it is difficult keep the project in sync with changes to WildFly itself.
So the place that this installer belongs is as part of the WildFly build. By default, the installer will create a CLI Deployment archive for the latest version of MyFaces. But you can run the Maven project with params to create installers for any Mojarra or MyFaces version.
Note that this only creates an installer for MyFaces. It does not add MyFaces to the default build of the WildFly server.
Attachments
Issue Links
- is related to
-
WFLY-976 Multi-JSF doesn't understand new modules structure
- Closed