Breaking changes with 0.1.4?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Breaking changes with 0.1.4?

asotobu
Yes, it was a mistake I have done, because instantation of extensions is done in Ruby part, I need a way to send JRuby runtime there, and I decided to use attributes, without thinking about collateral effects, for next version I will create a JRuby context similar as Graphene Context to get JRuby from everywhere

El dissabte 12 d’octubre de 2013, mojavelinux [via Asciidoctor :: Discussion] ha escrit:
On Wed, Oct 9, 2013 at 11:30 PM, asotobu [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Andres thanks for the stacktrace now I see the problem. This will change for next version so you don t have to clone the map. In fact it will be not necessary to clone nothing because I am going to create a context environment to get the Ruby environment for extensions instead of using as attribute which throws this exception in Gradle

That's great news, Alex! The cleaner the integration, the more comfortable users will feel about the use of JRuby.

-Dan

--



If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Breaking-changes-with-0-1-4-tp757p793.html
To unsubscribe from Breaking changes with 0.1.4?, click here.
NAML


--
Enviat amb Gmail Mobile
12