Puppet development IDE (Geppetto) integrated within Eclipse using puppet & hiera - puppet module

[soumen trivedi]

I have created a puppet module that will setup an eclipse platform and integrate eclipes features using Eclipes p2 director. I have a working eclipse platform with geppetto, dltk, egit & grep console features integrated within my development environment. 

As eclipse is one of many defacto-standards for IDE based development, I believe it would be easy for rollout and acceptance within the dev community.

https://github.com/soumentrivedi/puppet-eclipse_platform

It would be helpful if you can share some feedback on this module (rspec & beaker test are in progress and will be updated in due course).

This module is based on the https://forge.puppetlabs.com/runthebusiness/eclipse and re-uses some of its features and extends the plugin deployment through hiera rather than static parameter set.

[Juan Andres Ramirez]

THis module is for Eclipse??, install Eclipse and add this module?.

[soumen trivedi]

Apologies for the delay in response.

This module will install eclipse and install Geppetto, Ruby DLTK, etc. as features into Eclipse. Required in situations where you are building dev environments frequently and want to give dev the capability to start all over again if something goes wrong with the environment without having the worry to configure the eclipse environment for development. Hope this makes sense.

[Eric Francis]

[general puppet question] In your init.pp you have:

inherits eclipse_platform::params { class { 'eclipse_platform::setup': }}

What does defining a class inside of a class achieve? I'm still new to puppet, so just a point in the right diretion would be great. Thanks, Eric Francis

[Felix Frank]

On 10/28/2014 02:27 PM, Eric Francis wrote:

[general puppet question] In your init.pp you have:

inherits eclipse_platform::params { class { 'eclipse_platform::setup': }}

What does defining a class inside of a class achieve? I'm still new to puppet, so just a point in the right diretion would be great. Thanks, Eric Francis

Misunderstanding - this is not defining a class inside another. Your quote is just a quirky way of writing

...inhertis eclipse_platform::params { include eclipse_platform::setup }


The class { 'name': } syntax allows you to pass parameters, but should generally be avoided under any circumstances (if you ask me. Or John ;-)

HTH,
Felix

[jcbollinger]

On Sunday, November 9, 2014 4:53:08 PM UTC-6, Felix.Frank wrote:

 

The class { 'name': } syntax allows you to pass parameters, but should generally be avoided under any circumstances (if you ask me. Or John ;-)

Yep :)

Especially avoid the precise form Felix gave as an example, where you don't actually give any parameters.  NEVER use that -- it has only disadvantages relative to "include 'name'".


John