If Jundler will install a hook into Bundler it clearly depends on Bundler.
The other way is only necessary if we want to keep calling "bundle" for
our application and not worrying how things work internally.
Em 27-03-2012 18:26, kristian escreveu:
honestly Jundler does not need to depend on bundler just calling the
hook (maybe after a require 'jundler') should work.
- Kristian
On Wed, Mar 28, 2012 at 2:31 AM, Rodrigo Rosenfeld Rosas
<rr.ro...@gmail.com> wrote:
Em 27-03-2012 17:47, kristian escreveu:
hi,
to conclude my night and my nights topic: maven support for bundler
if JRuby could take over the call to Bundler.setup then it is possible
to get your jar deps into the classloader. first call Bundler.setup,
then parse a Mavenfile (or Jarfile) which declares jar dependencies.
then just resolve the transient deps and finally add them to the
JRubyClassLoader.
so is it possible to get a handle on that Bundler.setup method - a bit
like alias-chain it ?
If that is the only impediment, it shouldn't be hard to get a pull request
merged to add a hook on Bundler.setup.
Then JRuby users could install "jundler" a new gem maintained by the JRuby
community that would install a handler to this hook to do what is necessary
when the user runs "jundle".
After that we can request another pull request to Bundler so that it behaves
this way:
if RUBY_PLATFORM = 'java'&& File.exists?('Mavenfile')
if jundler_installed?
run_jundle
else
print_info_on_jundler_and_raise_an_exception
end
end
I mean, I'm not a Bundler expert so I don't know how it would deal with
cyclic dependencies like Bundler<=> Jundler. If there isn't any issue with
cyclic dependencies the above would be simplificated.
Just add 'Jundler' to the Gemfile automatically when the platform is 'java'
and a 'Mavenfile' exists when running "bundle".
Would that work in your opinion?
If so, I guess getting such approach accepted by the Bundler team would be
much easier.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
