[
https://jira.jboss.org/jira/browse/JBIDE-3642?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-3642:
--------------------------------------------
Ok, so we should simply just look for <config>/deploy/jboss-portal.sar and
<config>/deploy/jboss-portal-ha.sar to detect if Portal is present in both EPP or
.org
Does portal and epp.sar's have a consistent version numbering inside the .sar
somewhere ? i.e. 2.7.0 in org and 2.7.0_AP for EPP or something ?
Something we can use to detect if it is .org or epp, plus have a version number to
show/validate against.
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