+1 What would be the next steps in your opinion?
-- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Wed, Aug 12, 2015 at 9:21 AM, Violeta Georgieva <[email protected]> wrote: > Hi, > > I'm also interested in this topic and the idea for TomEE Buildpack. > > Regards, > Violeta Georgieva > > > Rohit Kelapure wrote > > TomEETribe, > > > > With the spread of Platforms As A Service such as Heroku, Cloud Foundry, > > Bluemix and Containers++ it becomes critical that TomEE provides first > > class support to the deployment of apps in the cloud. > > In many ways you already provide this with the ability to package fat > jars > > and TomEE Shades > > <http://www.tomitribe.com/blog/2015/03/50-shades-of-tomee/> > > and an official container > > <https://github.com/tomitribe/docker-tomee> that > > dockerized apps can build on. > > > > *I take the liberty here to suggest a feature that will accelerate the > > adoption of TomEE in the cloud*- *A buildpack for TomEE* > > > > *WHAT ?* This is a continuation of the conversation started here > > < > https://rmannibucau.wordpress.com/2015/06/18/java-ibm-bluemix-cloudfoundry-setup-how-to-get-tomee-on-bluemix-javaee/> > ;. > > This TomEE buildpack will allow Enterprise Java and JavaEE developers to > > push apps to Heroku > > <https://devcenter.heroku.com/articles/buildpacks>, > > Cloud Foundry AND all its derivatives like Bluemix, Pivotal Cloud > Foundry, > > HP Helion etc. The TomEE buildpack just like the JBOSS buildpack > > <https://github.com/cloudfoundry-community/jboss-buildpack> will > be > > a > > managed fork of the java buildpack > > <https://github.com/cloudfoundry/java-buildpack>. > > > > *WHY ?* Providing a buildpack allows developers to ONLY focus on the war > > files and NOT bundle the server within the app. It also provides a way > for > > the operators to upgrade and manage the versions of Java and JavaEE as > > well > > as other libraries independent of the app. It maintains a clean > separation > > between app code and the app server in the cloud. For a quick > introduction > > to the CF and the buildpack staging process see > > http://www.cloudcredo.com/a-droplet-of-value/. Buildpacks provide a way > to > > package code and prepare an immutable code artifact aka a droplet. > > > > *HOW ?* We would follow the process created by the Cloud Foundry Open > > Source foundation > > <https://www.cloudfoundry.org/foundation/at-a-glance/> to > > contribute the buildpack to the community > > < > https://github.com/cloudfoundry-community/cf-docs-contrib/wiki/Buildpacks> > ; > > and ultimately https://github.com/cloudfoundry. > > > > Thanks, > > Rohit Kelapure, > > Pivotal CF > > > Architectrkelapure@ > > > cell: 9197242524 > > > http://cloud.rohitkelapure.com/2015/07/migrating-websphere-application-server.html > > > http://cloud.rohitkelapure.com/2015/07/migrating-websphere-weblogic-apps-to-cf.html > > > > > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Request-for-a-TomEE-Buildpack-tp4675612p4675844.html > Sent from the TomEE Dev mailing list archive at Nabble.com. >
