Small enhancement (creating additional test methods)

Tonight I had some time to take a look at the list of feature requests of moreUnit.

Supporting move support for instance methods is not possible because eclipse does not allow participants in MoveInstanceMethodProcessor. So I left a comment in bugzilla and started to implement something different.

I have choosen a small enhancement: if you create a additional test method via the shortcut moreUnit appended the new test method at the bottom of the test case. I have changed that and moreUnit will append the additional test method directly below the test method in which the shortcut was pressed.

Version 2.0.1 released

Today a new version of MoreUnit released. Because of the new feature id I created a new update site (because you need to uninstall older version to switch to the newest version). Thanks to Andreas who helped me to solve the problem with the missing property page.

Frustrattion again

Today I wanted to play around with the new planned release and when installing the plugin the property page does not appear. That is a behaviour one of my teammates already had with the current release (and the prooblem disappeared at his laptop suddenly ...).

So now I am little bit frustrated because it does not seem to be a problem from the property page configuration :-(

Preparation for release of version 2.0.0

After changing the feature id, I decided to give a higher version number to the new release.

Changing the feature id, will make it necessary to uninstall and reinstall the plugin, so I created a new update site for the plugin.

http://moreunit.sourceforge.net/update-site/ hosts the new release already, but the official release will take some more days (to update documentation...)

Not that a big deal

While playing around with Buckminster I read about the p2.mirror-Ant task. That's excatly what I am looking for: merging a new release into a p2-enabled update site. A great pity that it took so long to find it.

I played around with it on my test update site and everthing worked fine.

Perhaps p2-frustration will come to an end...

... and for the Germans: Kaum macht man's richtig schon geht's ;-)

Next try: Buckminster

While looking around to find a nice tutorial how to automate p2-update-site generation I found a link to Buckminster. In the introduction (why use Buckminster) it says:

As a developer, you want to stay focused on the construction of your code, you expect it to be built interactively giving you instant error feedback.

That is exactly what I am looking for :-)

Let's start reading the introduction and try it out...

Patch and missing jar

Today  a teammate had a problem with MoreUnit. He can't see property pages of MoreUnit but everything else worked fine. This evening I tried to reproduce this problem in a fresh installation but had no success. Googling around did not give any hints.

While working on this I recognized that update site does not offer the latest release 1.3.3 anymore. I'm using archive-path in the site.xml so that sourceforge tracks my downloads but the direct link to the feature jar has been moved. Really annoying. It is the second time that my update site is broken because the download links did not work anymore.

So I decided to remove archive path inn the site.xml and will upload the jars directly into to updates site directories. This will cause a loss of the download statistic, but how cares...