[
https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on JDF-172:
-------------------------------
Normally for binary deployment I've cloned the OpenShift repo to a different
directory, removed the pom.xml and copied the war into deployments myself. I agree that if
you do both the local build and the want to push a binary on the same project, then you
need the steps you describe.
It just seems a lot of steps to me, to do what is probably quite a common thing - push
your project binary as a war to OpenShift.
IMO it's a common enough thing to do that you could offer a nice UI to wrap it. For
example, in the setup wizard, offer two checkboxes - source deployment and binary
deployment. Depending on which is checked/unchecked, perform the steps above. If binary
deployment is selected, provide a textbox to enter the war name, defaulting to ROOT.war.
Update TicketMonster tutorial to use JBDS for OpenShift deployment
------------------------------------------------------------------
Key: JDF-172
URL:
https://issues.jboss.org/browse/JDF-172
Project: JBoss Developer Framework
Issue Type: Task
Components: ticket-monster
Affects Versions: 2.0.0.Final
Reporter: Stefan Bunciak
Assignee: Marius Bogoevici
Attachments: ticket-monster.png
We should guide users to use JBDS for OpenShift deployment, but first we need to find out
the proper/working way:
* Source deployment needs medium sized gear on OpenShift (which normal user don't
have, but should work either way): JBIDE-13295
* Binary deployment works, but there's no way to deploy it to application root:
JBIDE-13296
Once above jira issues are resolved, the TicketMonster tutorial should be updated.
--
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