[
https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi...
]
Fred Bricon updated JBIDE-22138:
--------------------------------
Description:
This is a follow up on JBIDE-22128.
The maven profile is never read to determine the actual archive name. That will require
more coupling to m2e, in order to load the pom.xml model using the openshift profile, if
it exists, in order to determine the archive name. This will be a long running operation
and will require more significant changes
was:the maven profile is never read to determine the actual archive name. That will
require more coupling to m2e, in order to load the pom.xml model using the openshift
profile, if it exists, in order to determine the archive name. This will be a long running
operation and will require more significant changes
Openshift 3 plugin "Server Adapter" doesn't respect
openshift maven profile
---------------------------------------------------------------------------
Key: JBIDE-22138
URL:
https://issues.jboss.org/browse/JBIDE-22138
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
Openshift plugin 3.1.0.Final-v20160401-2357-B263
Reporter: Rafael Benevides
Assignee: Fred Bricon
Fix For: 4.4.x
This is a follow up on JBIDE-22128.
The maven profile is never read to determine the actual archive name. That will require
more coupling to m2e, in order to load the pom.xml model using the openshift profile, if
it exists, in order to determine the archive name. This will be a long running operation
and will require more significant changes
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)