[
https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy...
]
Andre Dietisheim edited comment on JDF-172 at 12/15/12 6:58 AM:
----------------------------------------------------------------
Using JBDS to publish ticket-monster is pretty easy (I can do a screencast if that
helps):
# ASSERT: have ticketmonster repo cloned to your machine
# EXEC: Launch *OpenShift Application* wizard from central and create a jbossas-7/eap-6
application.
# ASSERT: you get the application imported into a project in your workspace, and a server
adapter is created for it.
# EXEC: *File->Import->Maven->Existing Maven Project* and point it to the demo
folder in the ticket-monster repo.
# EXEC: drag and drop the ticket-monster project (you just imported in the former step) to
your Openshift server adapter (*Servers* view). When it asks you if it shall publish,
answer *No*
# EXEC: in the openshift project: go to the deplyoments folder and rename the
ticket-monster.war - that was created when you dragged'n'dropped it - to ROOT.war
# EXEC: open the *Navigator* view, browse the imported OpenShift project and get to the
*.openshift/markers* folder. Create an empty file called *skip_maven_build*.
# EXEC: select .openshift/markers/skip_maven_build and pick *Team->Add to Index* from
context-menu.
Your imported Openshift project and the server adapter should now look like this:
!ticket-monster.png!
# EXEC: Tell your OpenShift server adapter to *Publish*
To now look at your ticket-monster application, wait until the publishing progress
disappeared from the status bar and point your browser to the OpenShift application:
*Show in -> Web Browser* in the context menu of your OpenShift server adapter.
was (Author: adietish):
Using JBDS to publish ticket-monster is pretty easy (I can do a screencast if that
helps):
# ASSERT: have ticketmonster repo cloned to your machine
# EXEC: Launch *OpenShift Application* wizard from central and create a jbossas-7/eap-6
application.
# ASSERT: you get the application imported into a project in your workspace, and a server
adapter is created for it.
# EXEC: *File->Import->Maven->Existing Maven Project* and point it to the demo
folder in the ticket-monster repo.
# EXEC: drag and drop the ticket-monster project (you just imported in the former step) to
your Openshift server adapter (*Servers* view). When it asks you if it shall publish,
answer *No*
# EXEC: in the openshift project: go to the deplyoments folder and rename the
ticket-monster.war - that was created when you dragged'n'dropped it - to ROOT.war
# EXEC: open the *Navigator* view, browse the imported OpenShift project and get to the
*.openshift/markers* folder. Create an empty file called *skip_maven_build*.
Your imported Openshift project and the server adapter should now look like this:
!ticket-monster.png!
# EXEC: Tell your OpenShift server adapter to *Publish*
To now look at your ticket-monster application, wait until the publishing progress
disappeared from the status bar and point your browser to the OpenShift application:
*Show in -> Web Browser* in the context menu of your OpenShift server adapter.
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