Hi,
I encountered a problem when attempting to create a Java plug-in that can act as a module forge client for Eclipse. The
Modulefile and all the types are written in Ruby. I don't have a Ruby evaluator in my Java environment. I can of course
add JRuby, but that will increase the footprint of the bundle with an additional 7Mb. It will also introduce license
issues that will make it difficult to publish the bundle from Eclipse.org (they are very picky about GPL, even LGPL).
The Modulefiles that I've looked at so far seems to use a very straight forward syntax. Since it is used only to define
a limited set of meta-data values, perhaps I can safely assume that this will always be the case? If so, I have no
immediate need for Ruby just to parse them. The types however, is a trickier problem. If I've understood it correctly,
the only information that I need to extract from each type is the type name and the @doc tag and I can probably hack
that too.
The question I'd like to ask is if it's feasible to use a hack to extract the needed meta-data without using Ruby, or if
that will break anyway because more Ruby specific code is planned. I love Ruby, it's a beautiful language, but in this
particular case it would be nice if I could circumvent it.
Ideas and suggestions are very welcome.
Regards,
Thomas Hallgren
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.