Follow by Email

Friday, May 14, 2010

Update: Workspace Mechanic now has an update site

Sorry for not getting this done earlier today, but now the Workspace Mechanic for Eclipse now has an update site

Also I renamed the mailing list from to -- yes the hyphen has been removed.


David Plass said...

probably should update the wiki; right now it says to build from source

nutmac said...

I get the following error:

An error occurred while collecting items to be installed
session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Artifact not found: org.eclipse.update.feature,,0.0.0.

Foodberg said...

Now this is very odd. I will look at this later this evening and see what I can do.

Foodberg said...

Aha, it looks like perhaps the update site works for Eclipse 3.5 but not 3.6m7? Which version of Eclipse are you using, and which platform?

nutmac said...

I am using 3.6M7, which is one of the supported platforms on Workspace Mechanic home page (

The Workspace Mechanic works with Eclipse 3.5 (not 3.5.0) and 3.6, and requires Java 1.5 or later.

Foodberg said...

Oh yeah I wrote that myself! The raw source will definitely run in 3.6. The update site, though, does not seem to work. And that's gonna be fun to figure out.

Can you please do me a favor and drop me an email? You can send me a note through konigsberg at gmail dot com. That way we can talk through a faster medium.

Foodberg said...

OK nutmac I believe I've fixed the update site so it works with 3.5.0 through 3.6M7 (though I haven't, and won't test any earlier 3.6 milestone releases.)

nutmac said...

Robert, thanks. It installed and working fine under 3.6M7 (Ubuntu 10.04).

Unknown said...

Hello Robert,

there is an HTML error in the update site preventing the display of page contents in Internet Explorer 7 (possibly other versions as well). The closing title tag in the HTML head section is missing the right side angle bracket, resulting in a completely white page. Could you please fix this? Pages in subfolders show the same error, so this is probably cured by editing a template. Firefox is much more tolerant than IE, but alas I'm stuck with the company browser.


Anonymous said...

you should change it to