Now, codebase of JRuby Embed has been merged into JRuby, so next one
would be wiki pages. Currently, JRuby Embed wiki is not in JRuby’s.
People might not find where should they go to start using newly added
embedding API. Not to make them lose their way, I want to merge Embed
wiki pages into JRuby. Also, I can expect somebody corrects and adds
more.
So, where should I put three long wiki pages? On top page creating new
topic like “JRuby on Rails,” in “Embedding JRuby” section, or new
section in “JRuby Basics”? Any idea?
Now, codebase of JRuby Embed has been merged into JRuby, so next one
would be wiki pages. Currently, JRuby Embed wiki is not in JRuby’s.
People might not find where should they go to start using newly added
embedding API. Not to make them lose their way, I want to merge Embed
wiki pages into JRuby. Also, I can expect somebody corrects and adds
more.
That sounds fine to me, or linking out would be ok too. But merging is
probably better.
So, where should I put three long wiki pages? On top page creating new
topic like “JRuby on Rails,” in “Embedding JRuby” section, or new
section in “JRuby Basics”? Any idea?
Embedding JRuby section for sure. That whole are probably could be replaced with your stuff, perhaps with links to the old stuff.
It will be great if you keep embedded maven releases going. the reason I
say
this is that for jruby integration purpose it will be nice to have
compile
time dependency on just the API vs current jruby-complete.jar.
This will make lots of things easier, specially for the app servers such
as
Glassfish which also goes as Ubuntu bundle which requires
build-from-source
and that means source build for all the compile time dependencies. I had
to
put quite some effort to build jruby-complete.jar from source and yes,
this
includes the transitive dependencies.
It will be great if you keep embedded maven releases going. the reason I say
this is that for jruby integration purpose it will be nice to have compile
time dependency on just the API vs current jruby-complete.jar.
This will make lots of things easier, specially for the app servers such as
Glassfish which also goes as Ubuntu bundle which requires build-from-source
and that means source build for all the compile time dependencies. I had to
put quite some effort to build jruby-complete.jar from source and yes, this
includes the transitive dependencies.
It may be time to consider breaking a few of our sub-extensions into
separate src hierarchies and build processes. We’ve merged a lot of
stuff into our codebase, which makes it really hard to pull individual
pieces out. If we started to think a bit more modularly about how to
structure the different pieces of JRuby, it would help folks that want
specific APIs (like Vivek with the embedding API) as well as folks
that want to rip out stuff for a reduced-size JRuby.
It will be great if you keep embedded maven releases going. the reason I say
this is that for jruby integration purpose it will be nice to have compile
time dependency on just the API vs current jruby-complete.jar.
If it is JRuby 1.4, releasing separate maven archive is easy. However,
it is not easy on JRuby 1.5 since embedding API sources have been
merged into JRuby trunk. Probably, it’s possible, but users will
wonder why JRuby Embed is not included in JRuby.
This will make lots of things easier, specially for the app servers such as
Glassfish which also goes as Ubuntu bundle which requires build-from-source
and that means source build for all the compile time dependencies. I had to
put quite some effort to build jruby-complete.jar from source and yes, this
includes the transitive dependencies.
I know solving maven’s transitive dependencies is bit annoying.
Perhaps, like Charlie talked, breaking JRuby into sub components would
be the best answer.
-Yoko
wiki pages into JRuby. Also, I can expect somebody corrects and adds
merged into JRuby trunk. Probably, it’s possible, but users will
includes the transitive dependencies.
I know solving maven’s transitive dependencies is bit annoying.
Perhaps, like Charlie talked, breaking JRuby into sub components would
be the best answer.
Yep, +1 for Charlies proposal. breaking in to subcomponent will allow
existence of jruby-embedded-api.jar or something like that, which is
just
the JRuby embedded API:-)
-vivek.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.