[
https://issues.jboss.org/browse/JBIDE-16626?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-16626:
------------------------------------------
Since this seems not utterly urgent and tons of things to do for the "other"
binary deployment (snapshot, deploy) I'll postpone this to 4.2.x
OpenShift Server Adapter: Binary deployment
-------------------------------------------
Key: JBIDE-16626
URL:
https://issues.jboss.org/browse/JBIDE-16626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Final, 4.2.0.Alpha2
Reporter: Marián Labuda
Assignee: Andre Dietisheim
Fix For: 4.2.x
At first, I am not sure whether this is bug or desired behaviour (in that case this issue
is Enhancement). There is a problem with binary deployment.
Current workflow is following:
PRESTEPS:
1. Create OpenShift application (e.g. EAP through OpenShift explorer, context menu, new
application)
2. Open Project Explorer, select application and open context menu OpenShift - Configure
Markers...
3. Select disable maven build marker. You can select also Hot deploy to improve deploying
speed (no need to restart cartridge).
4. Open Navigator - .openshift - markers and select new markers and add them to Index
(context menu - Team - Add to Index)
5. Push application to OpenShift (e.g. context menu of application - Team - Commit...)
BINARY DEPLOYMENT
1. Now imagine, you want to binary deploy. Let's say, user change something in
index.html (for example title).
2. Then it's required to locally build application (context menu of application - Run
as - Maven build and set goal "clean package -Popenshift"). Result - application
is built in deployment folder as ROOT.war.
3. Add ROOT.war to git index (context menu - Team - Add to index)
4. Drag and drop application from Project Explorer to Servers view adapter onto the given
OpenShift adapter.
5. Confirm push.
My idea of binary deployment is:
1. User change something in application
2. Drag and drop application from Project Explorer to Servers view onto OpenShift adapter
- this step build application, add ROOT.war to index.
3. Confirm to push.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira