[
https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi...
]
Hardy Ferentschik commented on JBIDE-22128:
-------------------------------------------
{quote}
my problem was I didn't create the helloworld-msa project in the 1st place
{quote}
Exactly, so really it would have helped to get something like:" Project
helloworld-msa does not exist. Unable to import resources", instead of: "Error
from server: User "openshift-dev" cannot create imagestreams in project
"helloworld-msa"", which suggests (at least to me), that there is a project
_helloworld-msa_, but I don't have permissions to modify it.
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
Assignee: Fred Bricon
Labels: respin-b
Fix For: 4.3.1.CR1
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)