[
https://jira.jboss.org/jira/browse/JBIDE-4889?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4889:
------------------------------------
I have no idea what to do here.
The mere fact that the container
"org.eclipse.jst.server.core.container/org.jboss.ide.eclipse.as.core.server.runtime.runtimeTarget/JBoss
EAP 4.3 Runtime" is on the classpath means that that project WANTS access to all the
default server jars for that runtime.
This means, IMO, that this method should *ALWAYS* return the list of jars, ALWAYS.
So I'm confused as to how exactly this impacts the portlet code. Why is it necessary
to return null for portlet? If you make a portlet project, shouldn't we add all of the
jars from the server runtime to your project? Why shouldn't we do this?
I do not understand this issue at all.
JBoss Tools server runtime responds as capable of providing libraries
for portlet facets although it doesn't provide them
-------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-4889
URL:
https://jira.jboss.org/jira/browse/JBIDE-4889
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.M3
Reporter: Snjezana Peco
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.1.0.CR2
Attachments: org.jboss.ide.eclipse.as.classpath.core.patch
The problem is in the ProjectRuntimeClasspathProvider.getClasspathEntries() method that
returns libraries for every facet.
For more details see
http://www.jboss.org/community/wiki/PortletFacetLibraries
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira