[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:
-------------------------------
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
12 years
[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/15/12 8:19 AM:
----------------------------------------------------------------
Not sure I follow you completely.
In OpenShift 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 have both at the same time in cmd-line and JBDS. There's no difference btw the 2 in this matter. The only additional feature in JBDS is that it'll war any (WTP) project you drag and drop to the OpenShift server adapter (to the deployments folder). When publishing, the server adapter git pushes the wohle repo to openshift (exactly as a git push does), pushing the source and wars within the deployments folder. I'm thus not sure what workflow isn't clear, what added value there is with a checkbox. JBDS completely matches the workflow you have when you git push on the cmd-line.
In the above scenario we rename the war (that JBDS built when we drag'n dropped the ticket-monster to the adapter) from ticket-monster.war to ROOT.war so that it'll appear at /. Since source and binary deployments both happen, the source would get built, deployed to ROOT.war, and override our prebuilt ROOT.war. We avoid that by skipping the maven build with the skip_maven_build marker.
Do I miss something?
was (Author: adietish):
Not sure I follow you completely.
In OpenShift 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 have both at the same time in cmd-line and JBDS. There's no difference btw the 2 in this matter. The only additional feature in JBDS is that it'll war any (WTP) project you drag and drop to the OpenShift server adapter (in the deployments folder).
When publishing, the server adapter git pushes the wohle repo to openshift, pushing the source and wars within the deployments folder.
In the above scenario we rename the war (that JBDS built when we drag'n dropped the ticket-monster to the adapter) from ticket-monster.war to ROOT.war so that it'll appear at /. Since source and binary deployments both happen, the source would get built, deployed to ROOT.war, too and override our prebuilt ROOT.war. We avoid that by skipping the maven build with the skip_maven_build marker.
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
12 years
[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/15/12 7:25 AM:
----------------------------------------------------------------
Not sure I follow you completely.
In OpenShift 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 have both at the same time in cmd-line and JBDS. There's no difference btw the 2 in this matter. The only additional feature in JBDS is that it'll war any (WTP) project you drag and drop to the OpenShift server adapter (in the deployments folder).
When publishing, the server adapter git pushes the wohle repo to openshift, pushing the source and wars within the deployments folder.
In the above scenario we rename the war (that JBDS built when we drag'n dropped the ticket-monster to the adapter) from ticket-monster.war to ROOT.war so that it'll appear at /. Since source and binary deployments both happen, the source would get built, deployed to ROOT.war, too and override our prebuilt ROOT.war. We avoid that by skipping the maven build with the skip_maven_build marker.
Do I miss something?
was (Author: adietish):
Not sure I follow you completely.
In OpenShift 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 have both at the same time in cmd-line and JBDS. There's no difference btw the 2 in this matter. The only additional feature in JBDS is that it'll war any (WTP) project you drag and drop to the OpenShift server adapter (in the deployments folder).
When publishing, the server adapter git pushes the wohle repo to openshift, pushing the source and wars within the deployments folder.
In the above scenario we rename the war (that JBDS built when we drag'n dropped the ticket-monster to the adapter) from ticket-monster.war to ROOT.war so that it'll appear at /. Since source and binary deployments both happen, the source would get built and deployed to ROOT.war, too. We avoid that by skipping the maven build with the skip_maven_build marker.
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
12 years
[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/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
12 years
[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/15/12 6:52 AM:
----------------------------------------------------------------
Not sure I follow you completely.
In OpenShift 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 have both at the same time in cmd-line and JBDS. There's no difference btw the 2 in this matter. The only additional feature in JBDS is that it'll war any (WTP) project you drag and drop to the OpenShift server adapter (in the deployments folder).
When publishing, the server adapter git pushes the wohle repo to openshift, pushing the source and wars within the deployments folder.
In the above scenario we rename the war (that JBDS built when we drag'n dropped the ticket-monster to the adapter) from ticket-monster.war to ROOT.war so that it'll appear at /. Since source and binary deployments both happen, the source would get built and deployed to ROOT.war, too. We avoid that by skipping the maven build with the skip_maven_build marker.
Do I miss something?
was (Author: adietish):
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
12 years
[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:
--------------------------------------
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
12 years
Quickstarts with change in target from EAP to WFK
by Sande Gilda
As promised during the hangout, here is a summary of the situation.
A number of JIRAs were added to create quickstarts using DeltaSpike
features. In a couple of cases, existing quickstarts were modified
rather than creating new quickstarts, resulting in a change in target
from EAP to WFK.
These are a problem because an existing quickstart was modified,
resulting in a change in target product.
* JDF-144: Create a quick start using the deltaspike property
configuration; Pull request sent for modified helloworld-jms
quickstart, changing the target product to WFK.
* JDF-159: Demonstrate usage of Deactivateable from Deltaspike
updating relevant Quickstarts that uses Extension. Pull request was
sent that modifies the cdi-portable-extension quickstart.
**These JIRAs are not a problem because new quickstarts were created.
* JDF-145: Create a quickstart using deltaspike's exception handling;
Pull request sent for new deltaspike-exception-handling-quickstart
* JDF-149: Add a quickstart that shows how to use DeltaSpike
BeanManagerProvider to access CDI in a EntityListener; Pull request
sent for new deltaspike-beanmanager quickstart
* JDF-156: Demonstrate usage of DeltaSpike project stage in a
quickstart, and shows usage of a conditional @Exclude; Pull request
sent for new deltaspike-projectstage quickstart.
This is not a problem because the change introduced JBoss Logging and
did not impact the target product.
* JDF-165: Upgrade i18n (ML) Quickstarts to use JBoss Logging. Pull
request sent, but this doesn't impact the target product.
These JIRAs are not yet done. We need new quickstarts are created for them:
* JDF-158: Add custom authorization example using @SecurityBindingType
from DeltaSpike
* JDF-165: Upgrade i18n (ML) Quickstarts to use JBoss Logging. Pull
request sent, but this doesn't impact the target product.
* JDF-146: Add Deltaspike version of kitchensink that shows how to use
@Transactional
* JDF-148: Add a quickstart showing how to create new beans using
DeltaSpike utilities
12 years
[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, cool. But this does make me wonder if we have a workflow issue in the OpenShift plugin. Should it ask you up front which deployment method you want (e.g. a checkbox in the wizard)?
> 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
12 years