[
https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy...
]
Andre Dietisheim commented on JDF-172:
--------------------------------------
Btw. there's the "skip_maven_build" to prevent source from being built. IMHO
that's the better option than to remove the pom.
We actually exactly the same as you: The openshift git repo (with the starter app) is
imported into 1 workspace project, the ticket-monster repo is in a different workspace
project. Drag and dropping the ticket-monster project to the OpenShift project does what
you achieve by building the war and copying it into the OpenShift clone. We add the
"skip_maven_build" to achieve what you do by killing the pom.
I agree on saying that we could offer some UI to point out, facilitate and offer a better
user experience. Nevertheless I'm not convinced that this is all solved with
checkboxes. I'll have a chat with Max, collecting ideas after my PTO.
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