The MercurialEclipse plugin doesn’t play well with the latest 1.9 release of Mercurial.
If you’re on Ubuntu, you can replace the “mercurial” package with “mercurial-1.8” to get the old version back (see Launchpad packages). Thanks go to Max Bowsher for a quick solution:
sudo aptitude install mercurial-1.8
Leave a Comment » | 
Software | Tagged: Eclipse, Mercurial, MercurialEclipse, Ubuntu | 
Permalink
Posted by digulla
If your Eclipse IDE suddenly crashes with an error in java.util.zip.ZipFile.getEntry() chances are that you’re hit by this bug: Crash in ZipEntry when some other process changes the ZIP File at the same time
Workarounds:
1 Comment | Software | Tagged: Apache Maven, Eclipse, Maven | Permalink
Posted by digulla
My Maven Tools for Eclipse (MT4E) project has now a wiki page: http://wiki.eclipse.org/Maven_Tools_4_Eclipse
And I’ve started to convert the tools from Python to Groovy.
Leave a Comment » | Software | Tagged: Apache Maven, Eclipse, Maven, mt4e, Project Dash | Permalink
Posted by digulla
The constant NAMED_BUILDER_SCOPE has been moved from org.eclipse.xtext.scoping.impl.AbstractGlobalScopeProvider to org.eclipse.xtext.resource.impl.ResourceDescriptionsProvider.
1 Comment | Software | Tagged: Eclipse, Xtext2 | Permalink
Posted by digulla
If you downloaded the JEE edition of Eclipse 3.7, you’ll find that m2eclipse is missing.
Don’t worry, it’s part of the Indigo release train. Just install it manually from the Indigo p2 repository: http://download.eclipse.org/releases/indigo
Links: Oh my god, but where is m2e?
Leave a Comment » | Software | Tagged: Eclipse, m2e, Maven | Permalink
Posted by digulla
One of the big problems with WYSIWYG editors is that they don’t really cut it. They look good in the beginning but as your experience grows, the editor tends to get in your way of getting things done.
Stackoverflow used an interesting solution: There is a wiki markup editor and a preview which is updated as you type. So you get the best of both worlds: You can see your intention and the result at the same time.
Riena is now following along the same path: They created a preview which updates when you save your UI code. That way, you can quickly see the effect of your changes without stumbling over tedious property editors all the time.
2 Comments | Software | Tagged: Eclipse, Editor, Java, Preview, Riena, wiki, Wiki markup, WYSIWYG | Permalink
Posted by digulla
Eclipse Mylyn: Redefining the “I” of the IDE – Benjamin Muskalla
Mylyn is one of those things that can change your world if you just give it a chance. The talk emphasized one of the major points: We write the code in an IDE (integrated, not intelligent), we track bugs in a bug tracker, we communicate with email, twitter and Facebook and we track progress on a piece of paper.
Being able to save the context (i.e. the classes and files involved) in a bug, so, say, a junior doesn’t have to wade through the whole source to even get started, is something that I’ve been missing several times already. If only I wasn’t such an old dog, already.
Links:
1 Comment | Conference | Tagged: Development Tools, Eclipse, IDE, Java, Jazoon, Mylyn | Permalink
Posted by digulla
With Indigo, more Eclipse projects will move to Git.
Kudos go to the Git Task Force.
I’m especially happy that BIRT and the Eclipse platform is on the list.
Leave a Comment » | Software | Tagged: BIRT, CVS, Eclipse, GIT | Permalink
Posted by digulla
I’ve come to love Xtext. It’s powerful out of the box, simple enough to grasp and the rough edges cut you just once (i.e. after you put tape over them, the hurting stops).
But sometimes, a picture says more than a thousand words. Unfortunately, creating a graphical editor is still a daunting task. Which probably explains why most graphical editors aren’t worth the shadow the mouse pointer casts over them.
If we only had a compact language to define UI editors … but wait, we have. Or rather we could have with a bit of help with Xtext.
Welcome project Spray. Spray is a DSL to create Graphiti editors.
Leave a Comment » | Software | Tagged: Eclipse, Editor, Graphical Editor, Graphiti, Java, Spray, Xtext | Permalink
Posted by digulla
Dark Views 
Hudson and Jenkins Won’t Merge
18. May, 2011There has been recent discussion about a merge between Jenkins and Hudson, after Oracle pushed the dead weight to Eclipse.
My prediction: Won’t happen.
Why not? Because Eclipse is run by lawyers and developers hate lawyers.
Exhibit A: “Is the Eclipse process so bad? … Yes. It’s very bad (for developers). Bad enough to end many contributions.” (https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Hudson+Reconciliation+Requirements)
Exhibit B: “MIT (or MIT-ish, e.g., ASL, BSD, EDL) license” (same page)
Exhibit C: To work on Eclipse projects, you must become a committer (http://wiki.eclipse.org/Development_Resources). That means signing a contract. You have to have an IP Log. All projects on eclipse.org must submit to the Eclipse Public License (http://www.eclipse.org/legal/).
Why is that? Because IBM is rich and Kohsuke Kawaguchi is poor. So trolls are suing IBM and they won’t sue Mr. Kawaguchi. Which is why IBM is raising their barriers and why Jenkins isn’t.
The projects won’t merge
Share this: