[jbosstools-issues] [JBoss JIRA] (JBIDE-16626) OpenShift Server Adapter: Binary deployment
Max Rydahl Andersen (JIRA)
issues at jboss.org
Wed Aug 27 08:45:59 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-16626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996121#comment-12996121 ]
Max Rydahl Andersen edited comment on JBIDE-16626 at 8/27/14 8:45 AM:
----------------------------------------------------------------------
[~mlabuda] we cannot call it ROOT.war by default since it will conflict with the existing project related to the openshift instance.
This is what JBIDE-14818 relates to by allowing to name the server deployments.
was (Author: maxandersen):
[~mlabuda] we cannot call it ROOT.war by default since it will conflict with the existing project related to the openshift instance.
This is what JBIDE-14818 relates to.
> 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 was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jbosstools-issues
mailing list