Re: [tools-pmc] [CQ 4427] JRuby Version: 1.5.1 -- required discussion/ag

[David M Williams <david_williams@xxxxxxxxxx>]

Fellow PMC members, 

As discussed in this CQ, the Memory
Analyzer team is adding a new function to additionally "analyze"
some Ruby information in a heap. 
But, the ruby runtime has a license
such that it can not be distributed "out of the box" with Eclipse
content. From the description provided 
by Kaloyan, it does seem to me to qualify
as a "works with" dependency: If users already have it installed
or if they 
decide to accept its license terms,
then they will get that extra bit of functionality. This seems reasonable,
since 
if they were interested in Ruby "heap"
data, then they probably already have it installed ... and otherwise would
not "miss" 
the functionality (so Memory Analyzer
could not be said to be less functional without that third party jar).


If you have a different perspective,
or questions, please state that perspective, or ask the questions here
on this list. Otherwise, please
document your agreement here on this
list with it being classified as a "works with" dependency.  
 

+1 

Thanks,

From:	emo-ip-team@xxxxxxxxxxx
To:	tools-pmc@xxxxxxxxxxx
Date:	09/01/2010 05:38 AM
Subject:	[tools-pmc] [CQ 4427] JRuby Version: 1.5.1
Sent by:	tools-pmc-bounces@xxxxxxxxxxx

---

http://dev.eclipse.org/ipzilla/show_bug.cgi?id=4427





--- Comment #14 from Kaloyan Raev <kaloyan.raev@xxxxxxx>  2010-09-01
05:38:23 ---
David, this CQ is related to a new enhancement for the Eclipse Memory Analyzer
described in bug 318989. This new enhancement will be available for users
as a
separate optional feature. Existing functionality in the Memory Analyzer
is not
affected in any way. 

This new enhancement implements a "JRuby resolver" for the Memory
Analyzer.
This means that if you have jruby execution in your heap dump, then you
will
get additional information about jruby "things" in the generated
report. 

For the actual resolution of jruby-related data in the heap dump, we need
to
call the jruby runtime - hence the dependency to the jruby.jar. At the
same
time, part of the resolver's code needs to compile against JRuby classes.
We
are currently redesigning the implementation in a way that this dependency
is
optional. This means that if the jruby.jar is not present as a bundle in
the
Eclipse installation, then the JRuby resolver is not triggered, i.e. the
Memory
Analyzer behaves like the JRuby features is not installed. 

Luckily, the jruby.jar is distributed on the jruby.org download site as
an OSGi
bundle. We are able to easily implement a UI in the Memory Analyzer, that
enables users to install this JAR themselves (after downloading it) without
doing any modifications. 

I hope this clarifies the situation. 

My understanding is that this is a "works with" dependency. We
expect users to
do the additional action of downloading this JAR themselves, or consciously
hit
a button in the Memory Analyzer UI that will do the same for them (similarly
to
how EclipseLink can be installed). 

Thanks for taking care for the PMC discussion. 


-- 
Configure CQmail: http://dev.eclipse.org/ipzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the CQ.
_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc