Since beginning of last year I participate more or less actively in the Java User Group Mannheim. Unfortunately the former main contact of the Java User Group Mannheim Alex Hanschke has moved out of the area.

Benjamin Muskalla and myself volunteered to help organize the JUG Events. Therefore Benny and I will as of now try to find great new speakers and setup cool events. I think we are starting very well, as we are proud to have Matthias Sohn and Stefan Lay speak about Git and EGit on the 02.Sept. Git is one of the leading distributed version control systems and EGit a team provider for Eclipse.

Matthias and and Stefan are both committers in the EGit project. Details on Matthias and Stefan and the presentation can be found on the Majug Event Announcement. As usual we organize to have drinks after the event and hope Matthias and Stefan will be able to join so that you can bugger them with questions. The presentation will be in German.

Rumors are that we will see a real merge via EGit on this event… Hope to see you at their.

I learned from Steffen Pingel and Ekkehard Gentz that Mylyn has the ability to save local tasks outside the workspace. This is hidden under advanced in the Preferences.

This allows you to put your local tasks outside your workspace and versionize them with git. This way you can use git to move your local tasks between machines. I really like this as I frequently use different machines and now I can not only share source code betwee them but also my mylyn taslks.

As Steffen told me, simultanous access to the Mylyn tasks might cause task corruption but I don’t think that is an issue for me as Git takes care of conflicts and I do not have two machines writing to the same local file.

Fun times with Git and Mylyn!

If you are using Eclipse you properly using Mylyn. I recently got a new machine and wanted to migrate my local Mylyn tasks from one computer to another.

Local tasks stored in your workspace in .metadata/mylyn/tasks.xml.zip. The context for local tasks stored in .metadata/.mylyn/contexts… look for files labeled local-X.xml.zip, these have the context. You can back up the entire Mylyn data directory and put it into the same place on your new computer.

Worked well for me!

Thanks to David Shepherd for the tip via twitter.

If you ever wanted to copy the full workspace to another machine you may have noticed that a billion generated files (e.g. bin) are copied and that this takes a long time. If you start Eclipse with the -clean option the workspace will regenerate all file again.

You can avoid this bye de-selecting in the “Build automatically” in the preferences under General -> Workspace.

If you now select Project -> Clean -> All and de-select “Start an Build automatically” in the dialog you end up with a workspace without the files of the build process.

Unfortunately the Eclipse team provider EGit does currently not support to use HTTPS for cloning and pushing.

Fortunately the Git command line supports this (under Linux without problems).

git clone https://vogella@github.com/vogella/de.vogella.rcp.example.git
// do some changes
git push https://vogella@github.com/vogella/de.vogella.rcp.example.git

If you are on Windows and if you are using msysGit then you may receive the following error:

error: error setting certificate verify locations:
CAfile: /bin/curl-ca-bundle.crt
CApath: none
while accessing your_repo

If you have this error you can disable ssl verification to solve it.

git config --global http.sslverify "false"

After this change cloning and pushing works via https on Windows.

Alternative the following should also make msysGit work, but I didn’t test these approaches.

copy C:\Program Files\Git\bin\curl-ca-bundle.crt to c:\bin\curl-ca-bundle.crt

or

 git config --system http.sslcainfo \bin/curl-ca-bundle.crt

The full discussion of the msysGit issue can be found here.

[Update:] If you are behind a http proxy you can set the proxy via the following command:

 git config --global http.proxy http://proxy:8080
// To check the proxy settings
git config --get http.proxy

Are you around the Dresden area?

If so it would be great if you join my presentation about Eclipse 4.0 / Eclipse e4. The german title roughly translates into “the unexpected simplicity of developing Eclipse plugin and Eclipse RCP applications”.

The talk will be in German and details can be found on Saxony Website. I’m looking forward to meet you.

Eclipse has the option to put the semicolon at the right place in your coding.

For some very annoying reason my workspace had this feature disabled. In case you have the same activate it via the following:

As you know the Eclipse 4.0 SDK is out.

It also appears in discussions that some people don’t think Eclipse e4 is a good idea.

Other people seem to like it.

To help you to decide yourself I updated my Eclipse e4 Tutorial to Eclipse 4.0 Application Platform – Tutorial.

Together with Tom Schindls Tutorial you should be able to have a good start with Eclipse 4.0 SDK.

Please remember that the target of the core e4 Project is to improve the programming model of Eclipse and to provide an improved way of influencing the UI. The standard plugins are still the same and behave the same way.

My Tutorial also needs improvements, unfortunately it is not as far and deep as I like, but I hope that is will give you a good start. If you find issues, problems with my tutorial please let me know. The “more to come” section of my tutorial lists my future plans.

As you know the OSGi Framework enforces strong modularity. This also applies to native library code, e.g. a Windows DLL.

To make your DLL available in the context of OSGi you have to use the Bundle-NativeCode section in MANIFEST.MF.

For example if your DLL is called “sapjco3.dll” and is in the main path of you bundle you can use.

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Jco
Bundle-SymbolicName: com.sap.conn.jco
Bundle-Version: 1.0.0
Bundle-ClassPath: sapjco3.jar
Bundle-NativeCode: /sapjco3.dll; osname=win32; processor=x86
Export-Package: com.sap.conn.jco,

Many thanks to Matthias Heinrich for the tip.

After some time and effort mainly by Denis Roy and Bernhard Merkle the e4 git mirrors are working.

You find the e4 repos listed Eclipes Git overview.

EGit is also kind enough to be able to import all the projects from the different levels of the projects.

So give it a try via EGit and check out the e4 source code, e.g. the e4 UI projects via git://dev.eclipse.org/org.eclipse.e4/org.eclipse.e4.ui.git or if you want to use http via http://dev.eclipse.org/git/org.eclipse.e4/org.eclipse.e4.ui.git.