]
Stan Silvert updated WFLY-1840:
-------------------------------
Fix Version/s: 8.0.0.Alpha4
Put Multi-JSF installer into WildFly build
------------------------------------------
Key: WFLY-1840
URL:
https://issues.jboss.org/browse/WFLY-1840
Project: WildFly
Issue Type: Feature Request
Components: JSF
Affects Versions: 8.0.0.Alpha3
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 8.0.0.Alpha4
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: