Re: Request for a TomEE Buildpack

[David Blevins <da...@gmail.com>]

Hi Violeta,

Sounds good to me as well.  Not entirely sure what the actions are.  How do we get started?

What has to happen on this side of the fence?


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com


> On Aug 12, 2015, at 5:48 AM, Violeta Georgieva <vi...@apache.org> wrote:
> 
> Hi,
> 
> Rohit Kelapure wrote a comment here [1] that looks promising as a starting
> point.
> 
> "I am suggesting that the Apache TomEE team own the official TomEE buildpack
> and work with Cloud Foundry community to get it included first in the
> https://github.com/cloudfoundry-incubator and then graduate to
> https://github.com/cloudfoundry GitHub org. If you guys want to drive then I
> will be more than happy to start the community process."
> 
> What do you think?
> 
> Regards,
> Violeta
> 
> [1]
> https://rmannibucau.wordpress.com/2015/06/18/java-ibm-bluemix-cloudfoundry-setup-how-to-get-tomee-on-bluemix-javaee/
> 
> 
> Jean-Louis MONTEIRO wrote
>> +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 &lt;
> 
>> violetagg@
> 
>> &gt;
>> wrote:
>> 
>>> Hi,
>>> 
>>> I'm also interested in this topic and the idea for TomEE Buildpack.
>>> 
>>> Regards,
>>> Violeta Georgieva
>>> 
>>> 
> 
> 
> 
> 
> 
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/Request-for-a-TomEE-Buildpack-tp4675612p4675848.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.

Re: Request for a TomEE Buildpack

[rkelapure <rk...@pivotal.io>]

Quick update on the TomEE Buildpack effort. 

We now have a git repository : 
https://github.com/cloudfoundry-community/tomee-buildpack.git
<https://github.com/cloudfoundry-community/tomee-buildpack.git>   and a
slack channel  https://cloudfoundry.slack.com/messages/tomee-buildpack/
<https://cloudfoundry.slack.com/messages/tomee-buildpack/>   to discuss
design and implementation details.
The TomEE buildpack will be separate from the default java buildpack. The
TomEE buildpack like the JBOSS and WebLogic buildpack will merge upstream
changes automatically from the java buildpack. 

/The following design and implementation principles will hold true for the
TomEE buildpack./

 - TomEE BP will follow the mechanism of extension[REFERENCE] laid down by
the java BP. i.e. TomEE support will be introduced via a container like
tomcat and java-main see
https://github.com/cloudfoundry/java-buildpack/blob/master/README.md#configuration-and-extension
on details of how to configure and extend the java buildpack. The TomEE
buildpack will replace or disable the Tomcat container. 
 - TomEE buildpack will setup TomEE to run enterprise java apps. This
primarily entails packaging the buildpack acquiring TomEE binaries in the
compile phase and setting up the droplet start command in the release phase.
Given the sophisticated abstractions of droplet and application_root already
in place with the java BP we expect the TomEE changes to be restricted to
one file i.e. the tomee.rb. The TomEE BP will accept and run both ear and
war files. http://tomee.apache.org/deploying-in-tomee.html  The TomEE BP
will need to be explicitly targeted by the cf push -b option when pushing a
war file since the Java BP gets first dibs at staging and running the app by
default.
 - A CI pipeline will need to be established for the TomEE buildpack. This
could involve using  Concourse
<https://github.com/starkandwayne/concourse-tutorial>   or  Travis
<https://travis-ci.org/cloudfoundry>  . TomEE comes with an excellent 
portfolio <http://tomee.apache.org/examples-trunk/>   of examples that can
be used to validate feature/function of the buildpack and document any
constraints.

We are actively looking for volunteers. We desire a single squashed commit.
Each commit is a discrete unit of work, to be understood together in it’s
entirety. Seeing a single commit that embodies the entire functionality of
the component makes reviewing and merging easier. also you will have a CLA
on file to submit contributions. https://www.cloudfoundry.org/contribute/

*REFERENCE*:
The Java buildpack is designed for extension in terms of adding adding
agents, frameworks and containers.  Documentation for extending the
buildpack can be found  here
<https://github.com/cloudfoundry/java-buildpack#additional-documentation>  . 
Extension of the buildpack is designed in such a way that it is trivial
consume upstream changes to the buildpack, keeping forks up to date. The
buildpack is designed so that all extensions should be _additive only_. Most
extensions should not need to mutate any part of the buildpack; the
buildpack is implemented as a collection of extensions





--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/Request-for-a-TomEE-Buildpack-tp4675612p4676480.html
Sent from the TomEE Dev mailing list archive at Nabble.com.