[
https://issues.jboss.org/browse/RFPL-3416?page=com.atlassian.jira.plugin....
]
Brian Leathem commented on RFPL-3416:
-------------------------------------
The reply from [~gastaldi] via e-mail:
{quote}
The main benefit is to make your exposed plugin API available for other addons (as
extension points), and also faster installation, since it skips the compilation phase
{quote}
I suspect the RichFaces plugin will not be used as an extension point for other addons.
Also the small size of the plugin means it won't take a long time to compile.
I suggest we _not_ publish the plugin to maven central unless a user requests that we do
so. This will reduce our maintenance overhead when we want to update the plugin.
Update the RichFaces Forge plugin to work with RichFaces 4.5.x
--------------------------------------------------------------
Key: RFPL-3416
URL:
https://issues.jboss.org/browse/RFPL-3416
Project: RichFaces Planning
Issue Type: Feature Request
Components: examples
Reporter: Brian Leathem
Assignee: Michal Petrov
Fix For: 4.5.0.Final
The existing plugin targets Forge 1:
https://github.com/richfaces/richfaces-forge-plugin
It's likely best now to develop a new forge plugin that targets Forge 2:
http://forge.jboss.org/document/develop-an-addon
http://forge.jboss.org/document/share-your-addon-on-the-forge-website
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)