[
https://jira.jboss.org/browse/JBDS-1410?page=com.atlassian.jira.plugin.sy...
]
Max Andersen commented on JBDS-1410:
------------------------------------
Talked with Thomas Heute concerning the layout of jars.
First of all, JBoss Tools should *never* had being dependent on *any* files in *any*
example directory and that needs to be removed ASAP. That was a very big mistake. We
should only dependt on *reliable* locations within a distribution.
For this it means we should grab the portletbridge-api-2.0.0.FINAL.jar and
portletbridge-impl-2.0.0.FINAL.jar from <EPP_HOME>/portletbridge/
and the remainder is to be found in <EPP_HOME>/seam/lib
The ER4 release has the .war described above and it currently contains the community
binaries of RF and JSF - that is a mistake from EPP side and does cause some issues with
some RF components but is being fixed in their ER5/CR1 coming out over the weekend.
Thus from JBoss Tools/JBDS side we should simply use the standard locations as described
above and if it for some reason does not work even though we have all the configuration
and right jars then it is an EPP issue that we need to inform them about.
This also means that JBDS 3 will not be able to work out of the box with any of this -
this is all for JBDS 4. JBDS 3 projects on EPP 5.1 will need to have the jars manually
fixed.
Snjezana, can you make the changes above in our trunk so we can get it tested ASAP when
EPP 5.1 CR1 comes out ?
RichFaces don't work in portlet generated by JBDS
-------------------------------------------------
Key: JBDS-1410
URL:
https://jira.jboss.org/browse/JBDS-1410
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: jsf
Affects Versions: 3.0.1.GA
Environment: Linux (and portlet generated by JBDS tested on EPP-5.1.0-ER4 (and
previous ER + GateIn-5.1.0.GA)
Reporter: Jan Jamrich
Assignee: Max Andersen
Fix For: 3.0.2.GA, 4.0.0.Beta2
RichFaces Portlet generated by JBDS don't display content of richFaces tags. (Added
manually, with RF jars added manually as well)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira