[
https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy...
]
Andre Dietisheim commented on JDF-172:
--------------------------------------
Not sure I follow you completely.
Source and binary deployments are done via pushing the source or pushing a war in the
deployments folder. Those 2 are not mutually exclusive, you can have both at the same time
when using cmd-line. JBDS doesn't behave any different. The only difference to
cmd-line in the above steps is that JBDS would build your war when you drag and drop the
project to the adapter. When publishing, the server adapter git pushes the wohle repo to
openshift, pushing the source and wars within the deployments folder.
Do I miss something?
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