[
https://issues.jboss.org/browse/RF-11657?page=com.atlassian.jira.plugin.s...
]
Brian Leathem resolved RF-11657.
--------------------------------
Resolution: Rejected
We are removing the manifest entries from core introduced by this issue, in favour of
applications consuming RichFaces and targeting JBoss AS defining the manifest entries
themselves. For further details, see: RF-11951
(RichFaces documentation to this effect will be introduced with RFPL-2009)
Better integration with JBossAS 7.1
-----------------------------------
Key: RF-11657
URL:
https://issues.jboss.org/browse/RF-11657
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: build/distribution, compatibility
Affects Versions: 4.1.0.Milestone4
Reporter: Juergen Zimmermann
Assignee: Brian Leathem
Priority: Trivial
Fix For: 4.2.0.CR1
JBossAS 7.1 contains Google Guava 10.0.x (in addition to sac-1.3.jar and
cssparser-0.9.5.jar). Guava can be reused in RichFaces instead of doubling it in
WEB-INF/lib. The solution is pretty simple:
In richfaces-core-impl-VERSION.jar the file META-INF/MANIFEST.MF already contains the
line "Dependencies: ...". This line has to be extended by just
",com.google.guava" as follows:
Dependencies: org.w3c.css.sac,net.sourceforge.cssparser,com.google.guava
That's all and from now on RichFaces doesn't require the distribution of Google
Guava in WEB-INF/lib when the platform is JBossAS 7.1. Please see also
https://issues.jboss.org/browse/AS7-1809.
Be aware that there is no blank after the comma between net.sourceforge.cssparser and
com.google.guava.
--
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