identical to JRuby trunk, but I confirmed it worked well on JRuby
1.4.0RC3.
One more thing. You should add a tag in your repository. I used
latest rev to maven deploy your release, which should be safe since
you are the only person commiting to what amounts to an end-of-life
repo.
git tag {tag}
git push --tags # <---- This one bit me for a while
I am using the maven deployed .jar for build_lib versus your released
file since that will match a maven compile.
After that we can update the poms and add the new jar to build_lib on
1.4 branch (I can do this part once you have a new release out).
Will you update jruby-embed.jar to build_lib, Tom?
Just testing it now. Thanks Yoko,
-Tom
default value. I switched the default value of LocalContextScope from
embedding for the various threading setups (Rob’s plan). That fits
On Sun, Nov 1, 2009 at 10:40 AM, Thomas E Enebo [email protected]
wrote:
One more thing. You should add a tag in your repository. I used
latest rev to maven deploy your release, which should be safe since
you are the only person commiting to what amounts to an end-of-life
repo.
git tag {tag}
git push --tags # <---- This one bit me for a while
Thank you, Tom. I totally forgot about that. Now, jruby-embed has two
tags, 0.1.2 and 0.1.3.
I am using the maven deployed .jar for build_lib versus your released
file since that will match a maven compile.
I believe you could build .jar easily using jruby-embed’s pom.xml.