[
https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-22138 at 6/12/18 2:03 PM:
-------------------------------------------------------------------
according to [~rob.stryker] the best place to make this happen is a m2e project
configurator. The configurator would then set the module name according to the pom. The
question then is how to make sure we'd only configure those project that we want to
deploy to OpenShift. I guess that the OpenShift server wizard would set some marker to the
project that the configurator would catch and set the module name accordingly? [~fbricon],
[~rawb] thoughts?
was (Author: adietish):
according to [~rob.stryker] the best place to make this happen is a m2e project
configurator. The configurator would then set the module name according to the pom. The
question then is how to make sure we'd only configure those project that we want to
deploy to OpenShift. I guess that the OpenShift server wizard would set some marker to the
project that the configurator would catch and set the module name accordingly? [~fbricon]
[~rawb] thoughts?
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: Andre Dietisheim
Labels: openshift_v3, server_adapter
Fix For: 4.6.0.AM3
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
(v7.5.0#75005)