Re: [RDT-Dev] debugger: stepReturn fix, next+, step+ support
Hi Martin! I'm going to merged support of next+ and step+ into ruby-debug-ide (will be 0.1.3). This is a new feature added by Kent into ruby-debug 0.9.1: http://www.datanoise.com/articles/2007/4/3/ruby-debug-version-0-9-1-has-been-released Yes. Thanks. In the last days Kent has released ruby-debug-base 0.9.3, which includes at least one bug fix, which is relevant for us, too. In the following example the third line would not be covered from a next command. 1: if a==0 2: p a is 0 3: elsif a==1 4: p a is 1 5: end So, I have released ruby-debug-ide 0.1.4 which binds to ruby-debug-base 0.9.3 and also has the following changes:** * fixed noise on stdout * debug_eval got a 10 sec timeout * fixed exit command I've also notice that RubyDebugCommandFactory#createStepReturn uses 'next' command. It should use 'finish' command instead I believe. But maybe I've missed some hidden purpose. No, it was just plain ignorance from my side. Attaching possible patch containing createStepReturn fix as well as possible next+/step+ utilization. Thanks, I have applied them. So let me know if you commit the fix to createStepReturn into RDT so I may proceed with next+/step+ merge. I have no idea yet how we should integrate the forced (+) next/step commands into the debug perspective. AFAIU the comments from Kent they make most sense in rhtml files although they can be used in every file. So, it might be a good default to use forced commands in rhtml files but so far you can't even set a breakpoint in an rhtml file. Thanks Markus - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] RDT 0.9.0?
Christopher Williams wrote: Markus, On 3/1/07, Markus Barchfeld [EMAIL PROTECTED] wrote: Christopher Williams wrote: Markus, A couple things: 1. The nightly builds seem to have PRD qualifier at the end now. Shouldn't it be NGT? I think it's messing up my config so I'm not sure if I have the latest nightly installed when I hit the updatesite... I just checked but could not find any nightly with a PRD qualifier. Where did you find it? Hmm, I may just be dumb. I think what's happenign is that I'm using the update currently installed features of Eclipse and it is checking the production release update site and grabs down 0.8.1 (which supersedes all the 0.8.0 based nightly builds). I'm not sure how tough this woudl be, but is tehre a way we could vary the update site declared in the feature based on the type of build we're doing - so a nightly build would point to the nightly update site and when you did a check for latest version you'd grab the latest nightly (instead of the latest production). I guess another way around this is to incremement the base version of the nightlies after any release (which we've done with 0.x.0releases, but didn't do after 0.8.1). The first option was already working - until I messed it up when moving to pluginbuilder. Should be OK again with the next nightly build. But in order to get rid of the release update site you might have to uninstall all RDT versions. The lock in to a particular stream is achieved by replacing the production update site URL in the feature.xml with the nightly build update site. Markus - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Ruby-debug integration
Outside of this work do we have any other outstanding stuff to be looked at for the 0.9.0? [] Only some cleanup: It still seems as if there are two sets of constants which are used as keys in the launch configuration. Could we merge them? The other failing test is for the interpreter stuff, and until I have a linux machine that can reproduce the error I'm not sure if I can nail what's going on. Essentially the libraries it's detecting are missing the set of core stubs that get generated when you first add an interpreter. I don't know if there's just some oddity going on with the test on the build machine - or if those stubs aren't getting generated and added to the library list on Linux (I'm guessing the former, since this works on Mac OSX). OK, I can check this error. Thanks Markus - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Ready for debug-commons
Martin Krauskopf wrote: Martin Krauskopf wrote: TBD: mainly adding ruby-debug.rb I've just update Kent's ruby-debug and it seems that Markus was successful with propagating his changes directly there into v 0.8, right Markus? Congratulations! :) So there is no need to make it part of debug-commons any more? Hi Martin! Sorry also from my side for not replying to your other request earlier. But actually there was not much to comment from my side: it sounds good to me and just go for it. I will then move the development of the debugger tests to debug-commons, too (I have got to get a rubyforge account first). Do you have any chance to automate the tests and run them on various ruby versions (and on different platforms)? I had lot of trouble with running the tests as part of the Eclipse JUnit test suite. They took a lot of time and were unstable but it should get better without the Java stuff around. I think we should also run the test suite with ruby-debug if it is supposed to be a sort of compatibility test. And I would have to maintain the Test Suite in org.rubypeople.rdt.debug.test. otherwise. Furthermore there are also some extensions to ruby-debug which should be tested, too. Thanks Markus - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Refactorings - initial import
Christopher Williams wrote: There are still some things that need to be addressed: - Cruisecontrol: The plug-ins aren't built and integrated into the automated build yet and I'm not sure what needs to be done. Markus? OK. Build is up again. Your modifications to the feature.xml and svn_co_rdt were all right but I had to update the cruiseControlWorksapce on the server (cd /home/rdt/cruiseControlWorkspace; svn update). Furthermore I have added the refactoring.tests plug-in to the tests feature. BTW: two build failed because the subversion checkout was not complete, but I do not think that this is related to the refactoring plug-ins. I just assume that the sourceforge subversion service has not been very reliable. cheers Markus - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Refactorings - initial import
Hi Chris! I guess it'd be nice if I knew how to do some of the more common things we do: Set up a new release and add/remove a plugin. I'd be fumbling quite a bit to do either of those... The release stuff is pretty well explained in the wiki. Adding/removing a plug-in is like * make sure the plug-in builds in the workspace with the build files generated with PDE-Tools-Create ANT build file (I just figured out that rdt.refactoring was missing a build.properties and was therefore not built in the nightlies) * update feature.xml * update svn_co_rdt * log in to server, cd to cruiseControlWorkspace, call svn update The problem with the current configuration is that the subversion stuff is really hacked in. I have started a project called pluginbuilder (www.pluginbuilder.org) which eases the set-up of a PDE build. Subversion support is included and also a clear schema for building releases. Currently a PDE build can easily be set up with pluginbuilder and it also runs as nightly build at rdt.pluginbuilder.org. There are two features missing currently: building update-sites (ought to be simple) and test integration. After this is done I want to replace the current build scripts with the pluginbuilder configuration. Cruise control can further be used for scheduling, viewing build logs and results and sending the build notification emails. I have also planned to use pluginbuilder to provide a patched RadRails nightly build against our RDT nightly builds so that e.g. the ruby-debug feature will become more easily accessible for rails development. But yeah - my spare time is limited :-) Markus. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Remote Debug project
Any preferences for the name of the project? Remote Debug? Or Remote Debug Commons? :) I think commons is important, so Remote Debug Commons or Debugger Commons sounds good. BTW is anybody actively working on FTC_ClassicDebuggerCommunicationTest? I've noticed that always when there is a new fix/commit only few test cases (currently three) are enabled. I would stabilize those test and uncomment as much of test cases as possible. I'll also uncomment WasteReader thread in FTC_Abstract... which, if uncommented/enabled, would currently breaks some tests. If anybody also working on this let me know. Please enable all. I have used the suite method during development and then forgotten to comment it again. BTW: running the tests (again) after the cc build is still on my list Markus - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Remote Debug project
BTW on which version of debug.rb is eclipseDebug.rb built on? According to: http://rubyeclipse.mktec.com/cgi-bin/trac.py/ticket/225 it seems quite old. There was not merged fix in debug.rb which was five years old. That might be. I started on eclipseDebug.rb in 2002 on stable version. And unfortunately I did not merge back any fixes from ruby.rb ever since. Markus - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] State of RDT
I also managed to break the RI/RDoc stuff in the process, as well as launching debug mode and Test::Unit. I went back and fixed as much as I could, but Markus, Martin and others I could use some help making sure that debugging is set up to work OK again. Chris, I tried to launch a rdebug session on linux (ubuntu) but failed. I finally could start rdebug with the necessary arguments and the communication between Eclipse and the ruby process started but then the ruby process died. Does it run on OS X? I have checked in some fixes, please review them, because I do not have an overview of the new design and it was just poking. E.g. the keys for the launch configuration seem to be defined twice, and so the launch configuration could not determine the project of the ruby file to launch. The configuration for a default ubuntu/debian installation (apt-get install ruby1.8) is also quite awkward. You have to configure /usr as path to the interpreter and the default site_ruby directory does not exist. So I deleted the entry but then there were problems anyway so that I had to create the default site_ruby in order to proceed at all. Any idea how to mitigate these pains on a standard Linux installation? Thanks Markus - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Updating JRuby?
Mirko Stocker wrote: On Monday 15 January 2007 15:34, Markus Barchfeld wrote: As version number I would suggest the base version of JRuby (0.9.2) plus maybe the revision number of JRuby's subversion as qualifier (2742). So, if you create a jar from the current trunk of JRuby, the version could be 0.9.2.2742. This schema should work despite the current version number of 1.0.0. (The org.jruby plug-in was not part of the 0.8.x release, therefore problems should arise with nightly build installations if there are problems at all). It looks like I just broke the build because of the plug-in version: Unable to find plug-in: org.jruby_1.0.0. What can we do about that? It seems as if you have found feature.xml already :-) Markus - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Updating JRuby?
Mirko Stocker wrote: On Monday 15 January 2007 14:32, Christopher Williams wrote: Mirko, Feel free to update jruby. I just generate a jar and stick it into our org.jruby plugin. Be sure to increment the plugin.xml version number so it will override any previous versions. About the version.. I'm going to need a version from svn, what version string do I use there? If you update the plug-in ID, please also modify the feature.xml. As version number I would suggest the base version of JRuby (0.9.2) plus maybe the revision number of JRuby's subversion as qualifier (2742). So, if you create a jar from the current trunk of JRuby, the version could be 0.9.2.2742. This schema should work despite the current version number of 1.0.0. (The org.jruby plug-in was not part of the 0.8.x release, therefore problems should arise with nightly build installations if there are problems at all). If the JRuby source is patched the patch should be included in the JRuby plug-in, too. Furthermore I would suggest to add the sources as zip file, too (just to simplify debugging, it should not be included in binary builds). Markus - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] RDT Continuous Build Server
Christopher Williams wrote: Markus, Can you set up our continuous build server to email the offending contributors when the build breaks? The build list is activated again, please subscribe to [EMAIL PROTECTED] if not yet done. Also my work firewall blocks any HTTP requests for ports other than 80, so I can't check the build server pages to see what's up. Is there any chance we could host it on port 80 of the machine rather than 8080? The build host is now available at http://rdtcc.pluginbuilder.org. Only the JMX console still uses another port (8000), so you won't be able to trigger a build if you are behind a firewall. Markus - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] RDT Continuous Build Server
Christopher Williams wrote: Markus, Can you set up our continuous build server to email the offending contributors when the build breaks? Since we moved to subversion I did not look into this. In CVS we had maintained the CVSROOT/users file for this purpose. I do not know what is necessary for subversion. But I can reactive the build mailing list ([EMAIL PROTECTED]) and send the build mails to it. But of course that would require that all developers subscribe there. Also my work firewall blocks any HTTP requests for ports other than 80, so I can't check the build server pages to see what's up. Is there any chance we could host it on port 80 of the machine rather than 8080? Yes. I am going to set up a new domain tomorrow. Markus - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] [PATCH] Open debug perspective on suspend
Werner Schuster (murphee) wrote: Markus Barchfeld wrote: The debugger will need some serious refactoring. Currently I work on the integration of ruby-debug which will probably make the debugger 2,5 times faster (e.g. wait 10 instead of 25 secs until reaching a breakpoint). Unfortunately ruby-debug needs some refactoring (if it is feasible at all) to support threads in the same way as the current debugger. What's the current state for debugging JRuby? I looked at org.rubypeople.rdt.launching/ruby/eclipseDebug.rb I did not do anything towards support for JRuby debugging (I am just not using JRuby, so ...). Is that still used or will this be replaced by ruby-debug? (That's the debugging lib that's using a native extension, is it?) For debugging with ruby-debug eclipseDebug.rb will not be used at all. But I think we should support both since ruby-debug is not (yet?) part of the ruby installers and needs to be installed with gem. Of course we will need RDT compatible releases of ruby-debug and I hope that we will have one soon. Yes, ruby-debug is the one with the native extension. Compared to the current implementation there is logic moved into C code resulting in less ruby calls (mainly for checking if a breakpoint is being hit). I trying out org.rubypeople.rdt.launching/ruby/eclipseDebug.rb and JRuby. It didn't work out of the box because it just froze/blocked after startup. I got it to work up to a certain point, where it at least reads from the commandLoop, but there's a problem because the Regexes that this uses don't work in JRuby. You can have a look at the test suites in org.rubypeople.rdt.debug.core. There you can see all the commands we send to the debugger and what results we expect. As mentioned before the main issue with ruby-debug was the threading model. With the test suite you will find out soon which scenarios will do or not. Thanks Markus - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] [PATCH] Open debug perspective on suspend
It seems that RDT doesn't open debug perspective on suspend such as breakpoints (JDT does). I read LaunchSuspendTrigger#handleDebugEvents() and created a patch for this problem. Please check it. Small, but effective. Excellent. Thanks, it is committed. The debugger will need some serious refactoring. Currently I work on the integration of ruby-debug which will probably make the debugger 2,5 times faster (e.g. wait 10 instead of 25 secs until reaching a breakpoint). Unfortunately ruby-debug needs some refactoring (if it is feasible at all) to support threads in the same way as the current debugger. There is some basic support already checked in which supports a very basic scenario. It still needs patching of ruby-debug, hopefully we will get a compatible ruby-debug release in the future. So, if you want to get further involved, have a look. Markus - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Enabling email notification on ticket changes?
Mirko Stocker wrote: On Sunday 27 August 2006 06:02, zdennis wrote: I belive this was turned on at one time, but then it was disabled. I cannot remember why, but I can add this back in if folks want it. Where should the emails be sent? We have our Trac configured to notify the reporter, the owner and the CCs and are quite happy with it. I'd also vote for a copy to the mailing list which was working for a certain time. Thanks Markus - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Broken Overview and Tutorial
designker wrote: Okay all fixed now. Please apply debug.ui.patch.txt to rdt.debug.ui. This will remove the cheatcheet extension from the plugin.xml. You still need to delete the unneeded cheetsheet files from rdt.debug.ui. Without this the cheetsheet appears twice. Now apply rdt.patch.txt to rubypeople.rdt. This fixes the webServises.xml to directly open the Ruby perspective. Hi Designker! Your changes are in the repository. Sorry, that it took so long. Do you plan further improvements? You mentioned a simple hello world example. Markus - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Broken Overview and Tutorial
designker wrote: Hi, After messing around with org.rubypeople.rdt I have fixed the RDT Overview and Tutorial that no longer appeared as of RDT 0.8. I am not 100% sure I have fixed it all as the org.rubypeople.rdt.doc.user that is in the trunk has an empty HTML folder and I think that is where the RDT help should have been? Could you move the cheatsheet to org.rubypeople.rdt? The reason why it was located in debug.ui were commands which used classes from debug.ui. And org.rubypeople.rdt should not depend on org.rubypeople.rdt.debug.ui. The html files are generated from the docbook file. Try to generated with the current information in the wiki. If that doesn't work anymore I am going to update it. Can you explain how I can now give you the changes. Should I email a patch or is there some way to commit it to a branch so you can evaluate it. Sorry for the newbie questions. You can send a patch to me. After you have sent in a few patches and if you intend to contribute further (which of course would be very much appreciated) you will be granted developer access. Thanks Markus - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Introductions
Hi all! This is also a subtle way of mentioning to list members that I've switched the RDT codebase over to SVN from CVS on Sourceforge. Markus is also switching the continuous build server to compile against Eclipse 3.2. The continuous build is using subversion now. Eclipse version is 3.2RC7. There are some open issues, though: * email notification is turned off * tests are not running * the build status page does not detect the build status file Hopefully subversion will make it easier for me and others to create tags and branches (instead of always turning to ask markus to do the dirty work). Also, The refactoring project could now use svn:externals to keep the RDT code in sync. Whereas the migration of the automatic build was easier than expected, I've got a problem with the subclipse plug-in: In the synchronisation view there is no override and update menu entry and using replace with... does not delete files which have not been checked in (e.g. build result files). Does anybody know a workaround for these two problems (revert doesn't delete these files either)? Chris, could subversion be configured to send email notifications like CVS does? Thanks Markus ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Releasing 0.7.0
Perhaps, but since we follow Ruby we need to make this additional ID feature turned on as an extension of some sort. As a quick fix I could have useless statment visitor check for a set system property? Anyname like 'jruby.less.warnings'? If this is set, then we will not throw a warning in these cases. This seems like a good quick solution. Using IDs may be a better solution for allowing people to set which warnings/errors they want ignore, but that is probably to discuss for next version of RDT. Should be OK. Please check 0.7.0.601152327NGT, if it is fine I will release 0.7.0. I can make the system property based patch tommorow evening and then drop a tag so that we can identify where on JRuby's trunk RDT happened on. That would be great. Thanks Markus --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] Releasing 0.7.0
Christopher Williams wrote:
Markus and all,
What are the fixes or other steps that everyone thinks we need to
complete before releasing a true 0.7.0 release? The Radrails guys
have been patiently waiting for the release to do their own. I think
we should push to do what we can to get it out for them - they've
been waiting a long time.
I think the useless .. warning is crucial despite the configurable
squiggels. Therefore I've created a new jruby.jar from jruby HEAD.
Thanks to the latest changes from Thomas this fixes bug #67. In order to
fix the useless warning I've applied the crude patch below. Thomas, do
you think there is a chance to add an ID to warnings for the next
release so that we can add preference page for filtering warnings?
Thomas, do you see any obstacles with HEAD of jruby? I've got one
failing test (testDigest) and one error (testRubyRequire) when running
MainTestSuite.
Please check 0.7.0.601152327NGT, if it is fine I will release 0.7.0.
Markus
Index: UselessStatementVisitor.java
===
RCS file:
/cvsroot/jruby/jruby/src/org/jruby/ast/visitor/UselessStatementVisitor.java,v
retrieving revision 1.13
diff -u -r1.13 UselessStatementVisitor.java
--- UselessStatementVisitor.java4 Nov 2005 16:12:49 -1.13
+++ UselessStatementVisitor.java15 Jan 2006 22:07:30 -
@@ -78,8 +78,8 @@
}
private void handleUselessWarn(Node node, String useless) {
-warnings.warn(node.getPosition(), Useless use of + useless
-+ in void context.);
+//warnings.warn(node.getPosition(), Useless use of + useless
+//+ in void context.);
}
/**
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Rubyeclipse-development mailing list
Rubyeclipse-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
