[
https://issues.jboss.org/browse/RF-11760?page=com.atlassian.jira.plugin.s...
]
Karel Piwko commented on RF-11760:
----------------------------------
An image illustrating the problem attached to
https://issues.jboss.org/browse/JBPAPP-7632.
I think this can be solved by simply removing <parent> section from the
richfaces-bom file. The only influence this change should have on your build is that you
would probably want/need to specify plugin versions you are using to release/deploy the
richfaces-bom artifact.
Remove parent section from richfaces-bom
----------------------------------------
Key: RF-11760
URL:
https://issues.jboss.org/browse/RF-11760
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: build/distribution
Affects Versions: 4.1.0.CR1
Reporter: Karel Piwko
Priority: Blocker
Fix For: 4.1.1.Final
Having <parent> element in the BOM file is fundamentally wrong.
If user imports dependencyManagement of the BOM file, it imports even the dependencies
from its parent and upper ancestors. Since the ancestor is jboss-parent, it includes
virtually the whole world.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira