December 2012 - jdf-dev - Jboss List Archives

[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy... ] Andre Dietisheim edited comment on JDF-172 at 12/14/12 4:54 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*. 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 should now look like this: !ticket-monster.png! # EXEC: Tell your OpenShift server adapter to *Publish* To now look at your ticket-monster application, point your browser to the OpenShift application: Once the publishing progress disappears from the status bar, use *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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy... ] Andre Dietisheim edited comment on JDF-172 at 12/14/12 4:50 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*. Your imported Openshift project should now look like this: !ticket-monster.png! # EXEC: Tell your OpenShift server adapter to *Publish* To now look at your ticket-monster application, point your browser to the OpenShift application: Once the publishing progress disappears from the status bar, use *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 should now look like this: !ticket-monster-project.png! # EXEC: Tell your OpenShift server adapter to *Publish* To now look at your ticket-monster application, point your browser to the OpenShift application: Once the publishing progress disappears from the status bar, use *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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy... ] Andre Dietisheim updated JDF-172: --------------------------------- Attachment: ticket-monster.png > 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy... ] Andre Dietisheim edited comment on JDF-172 at 12/14/12 4:36 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*. Your imported Openshift project should now look like this: !ticket-monster-project.png! # EXEC: Tell your OpenShift server adapter to *Publish* To now look at your ticket-monster application, point your browser to the OpenShift application: Once the publishing progress disappears from the status bar, use *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: *Remove* the module, that's the original openshift application, from your OpenShift server adapter. # EXEC: Tell your OpenShift server adapter to *Publish* # EXEC: Once the publishing progress disappears from the status bar, use *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 > > 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy... ] Andre Dietisheim commented on JDF-172: -------------------------------------- Pete, the above steps are a binary deployment. The war is built when you drag and drop the project to the server adapter (see step 5. War then appears in the deployments folder in step 6 and has to be renamed 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 > > 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on JDF-172: ------------------------------- Andre, can you modify your process for binary deployment? > 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 > > 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici commented on JDF-172: -------------------------------------- The inability of running the maven GWT plugin in a truly accessible fashion (e.g. free account users don't even have access to a large gear, let alone it is pretty slow) is sort of a hard stop for deploying source on OpenShift. > 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 > > 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy... ] Andre Dietisheim commented on JDF-172: -------------------------------------- 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: *Remove* the module, that's the original openshift application, from your OpenShift server adapter. # EXEC: Tell your OpenShift server adapter to *Publish* # EXEC: Once the publishing progress disappears from the status bar, use *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 > > 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JDF-173) misplaced menu and overlaying parts at TICKETMONSTER Getting Started page

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JDF-173?page=com.atlassian.jira.plugin.sy... ] Rastislav Wagner updated JDF-173: --------------------------------- Attachment: ticketmonster.png ticketmonster1.png > misplaced menu and overlaying parts at TICKETMONSTER Getting Started page > -------------------------------------------------------------------------- > > Key: JDF-173 > URL: https://issues.jboss.org/browse/JDF-173 > Project: JBoss Developer Framework > Issue Type: Bug > Components: site > Environment: Chrome 23.0.1271.97 or Firefox 17.0.1 > 1920x1080 > Reporter: Rastislav Wagner > Attachments: ticketmonster.png, ticketmonster1.png > > -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JDF-173) misplaced menu and overlaying parts at TICKETMONSTER Getting Started page

by Rastislav Wagner (JIRA)

Rastislav Wagner created JDF-173: ------------------------------------ Summary: misplaced menu and overlaying parts at TICKETMONSTER Getting Started page Key: JDF-173 URL: https://issues.jboss.org/browse/JDF-173 Project: JBoss Developer Framework Issue Type: Bug Components: site Environment: Chrome 23.0.1271.97 or Firefox 17.0.1 1920x1080 Reporter: Rastislav Wagner Attachments: ticketmonster.png, ticketmonster1.png -- 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

11 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

jdf-dev December 2012