[
https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-22128:
-------------------------------------
So we actually have 2 problems here:
- the openshift app was not created from a template, and we don't detect it's an
EAP kind of server. The current detection mechanism is very brittle, we can make it a tiny
bit better by checking if the name of the image contains eap or wildfly. That will fix the
immediate issue (EAP server profile automatically tries to create a ROOT.war) but that
won't be a long term solution I guess. I have a PR coming for this.
- 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-22128
URL:
https://issues.jboss.org/browse/JBIDE-22128
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
I have a Java project with an "openshift" maven profile that creates a
ROOT.war
When I create a "Server Adapter", the openshift plugins deploys the name of the
project.war
The plugin should be integrated with M2E in a way that if I select/enable the
"openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through
"Server Adapter".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)