[
https://issues.jboss.org/browse/JBIDE-11286?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11286:
---------------------------------------------
should not be disabled for the following reasons:
1) users can change the deployments in their .openshift/config/standalone.xml file
2) there are other server/app types than JBoss AS 7 where the location can be different.
3) finally, you can use this as a way to put other dependencies up remotely that your mvn
build will use instead of putting them directly in deployments.
We could warn the user if the deployments folder is not deployments (or even better look
for .openshift/config/standalone.xml setting if the apptype is JBoss and only validate
then)
Disable output directory field in OpenShift server adapter
----------------------------------------------------------
Key: JBIDE-11286
URL:
https://issues.jboss.org/browse/JBIDE-11286
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta1
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.Beta2
Attachments: deployments.png
OpenShift PaaS is expecting this directory to be strictly named *deplyments*, so changing
this directory to a different one doesn't make sense - OpenShift won't deploy
applications in different directory, even it is built in war correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira