Showing posts with label Eclipse. Show all posts
Showing posts with label Eclipse. Show all posts
-
Please follow the link in the title for full content.
-
I will probably have to start with some apologies for letting you guys wait so long for the plugin I have announced in a couple of previous posts, but (as you probably already know the excuse) I've been very busy lately.
However in order to keep things short: here is the download link. It is not a real release, but the version I've been tweaking for a while and I am currently using. There are still problems with it, but most of the time it works (or at least using another programmer excuse: it works for me [smile/]). Please give it a try and let me know. -
In a previous post I was talking about some small changes I have applied to one of the first OSS projects I was a core developer and committer: Coffee-Bytes. After that post, I have received quite a few messages expressing their interest in this plugin and the changes I have done to make it work with Eclipse 3.2. Lately I have been very busy (speaking at JavaZone and JAOO) and I haven't been able to do much about it. Still, on this project we were two developers, so before doing anything I will have to discuss these details and see what are the options. However, I promise I will keep everybody interested posted.category: Eclipse
-
This evening I had a horid surprise: after upgrading my SVN client (TortoiseSVN) to version 1.4.0 which supports the latest subversion (same 1.4.0) and committing some folder level properties, I was starting to see that some projects in my Eclipse workspace were not anymore recognized as SVN projects. As I do these activities more or less without paying too much attention, I've found myself bitching around quite soon (and I've even hadn't known who to blame) When checking the Subversion 1.4.0 Release Notes the following fragment explained everything:
Due to certain improvements and bugfixes made to the working copy library, the version number of the working copy format has been incremented. This means that Subversion clients earlier than 1.4 will not be able to work with working copies produced by Subversion 1.4. Similarly, the repository format has changed as well, meaning that pre-1.4 Subversion tools that normally access a repository directly (e.g. svnserve, mod_dav_svn, svnadmin) won't be able to read a repository originally created by Subversion 1.4. WARNING: if a Subversion 1.4 client encounters a pre-1.4 working copy, it will automatically upgrade the working copy format as soon as it touches it, making it unreadable by older Subversion clients. If you are using several versions of Subversion on your machine, you need to be careful about which version you use in which working copy, to avoid accidentally upgrading the working copy format. This "auto upgrade" feature, however, does not occur with the new repository format.
So, both SVN Eclipse plugins (or at least the two I know): Subversive (the one I am using) and Subclipse are now screwed because none of them has yet incorporated the new Subversion release. My advise: if you are an Eclipse user and you want to upgrade your SVN client, wait for the plugins to be upgraded themselves, because otherwise you will not be able anymore to work with SVN from within Eclipse. -
One of the my first open source projects I have worked on was Coffee-Bytes code folding plugin. It happened a long time ago and at some point the development has been discontinued. However, tonight, working on some very long sources I have remembered it and I said I should give it a new try. Unfortunately, once I enabled it no editors could been displayed. Checking the
.logfile I have found the reason: the folding code was broken with aNoSuchMethodexception. I have found in my archives the last version of the plugin and I thought I should check the API. To my surprise the API was still available (or at least reachable), but what made me post this entry is a feature added in Eclise 3.1: Access Restrictions, according to which when you create a plugin you can restrict others plugin access to its code. While I find the idea quite good (as it makes the API more clear), I have found out that almost everything related to java source code editors is restricted, and I am wondering why? I thought some other plugins would benefit from a clear API (for example AJDT), and now finding this makes me wonder about the reasons (I am quite sure there are good reasons). However, getting back to the points of this entry, you can read more about Access restrictions: here. Following the last advise specified at the above link:But what if you really, really, really, really need to use the class? In that case, you can use it, but you need to be aware of what it means (four really's usually does it for me).
I have done some small changes to readapt the code and now I have again Coffee-Bytes code folding working on Eclipse 3.2. Just look at the picture to see how reach it is compaired with the default code folding offered by Eclipse:
It offers you folding for:
- top level types
- normal methods
- constructors
- getters and setters
- main methods
- inner types
- static initializers
- import statements
- source headers
- comment blocks
- javadocs
category: Eclipse -
I am wondering if Eclipse is actually waiting for Callisto before it releases the final 3.2. There haven't been any post 3.2RC7 release candidates and not even maintenance builds on the 3.2. I know that Callisto aims to be a concerted release of multiple projects/plugins, and that some of us may like this idea, but I am thinking that this is making the life harder for other plugin developers (even if Eclipse has been in API freeze state for quite a while) and other products based on Eclipse (f.e. MyEclipse).
Update: I think there is already a confirmation for my supposition.
-
After reading Cedric's post on Code reviews I remembered that I have used an Eclipse plugin that helped me doing code reviews: Jupiter (I have even submitted at that time some patches [blink/]). As far as I know the plugin is continuously improved so if you are in need for something like this go and get it a try.
Another nice Eclipse plugin that might help with code reviews is Mylar even if its intention is not exactly this one.
