[
https://jira.jboss.org/jira/browse/JBIDE-3642?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-3642:
--------------------------------------------
The correct way is that if you have a server defined that point to a runtime with a
configuration that does not contain Portal then portal shouldn't be enabled hence
programmatic config is what I would say is the correct way.
About the difference of EPP I'm going to ping Thomas to understand why there is this
difference and if there is any reason for this.
Portlet Tools hardcode "default" for configuration name
-------------------------------------------------------
Key: JBIDE-3642
URL:
https://jira.jboss.org/jira/browse/JBIDE-3642
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Portal
Affects Versions: 3.0.0.cr1
Reporter: Rob Stryker
Assignee: Snjezana Peco
IPortletConstants hardcode "default" as the configuration name in several
constants. This is bad. These constants are used by PortletRuntimeComponentProvider and
PortletRuntimeLibrariesContainerInitializer.
The PortletRuntimeComponentProvider should be checking the actual runtime configuration
by adapting it to a IJBossServerRuntime and using hte getJBossConfiguration() method to
find out what configuration the runtime represents (default, all, minimal, production)
--
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