[ 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? -- 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