[
https://issues.jboss.org/browse/RF-12809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761135#comment-12761135
]
Pete Muir commented on RF-12809:
--------------------------------
We have a standard set of BOMs for all product components. I understand this
may be more confusing for RichFaces users who aren't used to this, but it is a
lot more consistent across the whole product line.
It's easy to update the version in the JBoss BOMs, just send a pull request to
that project, and we will do a release. The only reason it's old is because no
one from the RichFaces team has requested that it is updated :-)
Whilst it may make the example clearer to you, when viewed across all examples,
it's more confusing, IMO as its not consistent.
> Richfaces-related examples should use -with-richfaces BOM
> ---------------------------------------------------------
>
> Key: RF-12809
> URL: https://issues.jboss.org/browse/RF-12809
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Tomas Repel
> Fix For: 4.3.2, 5.0.0.M2
>
>
> There is jboss-javaee-6.0-with-richfaces BOM, I think this should be used
> instead of richfaces-bom in case that jboss-javaee-6.0 BOM is required as
> well. This holds for helloworld-rf, kitchensink-rf and richfaces-validation.
> In case of helloworld-rf it is sufficient the dependencyManagement section to
> contain only -with-richfaces BOM, the jboss-javaee-6.0 BOM can be removed
> completely.
--
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: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
