Version 2.2.1 released

A new version of MoreUnit is out with the following features:

• Extension point enhancements
• Extended method search has been improved (better performance and accuracy)
• Different actions for running a single test method or the whole test case
• Better support for TestNG (now runs several test cases at once)
  

Update after a long time

It's time for another blog post after a long time.

Some of the latest news:

• A new release is out for a while now
• The MoreUnit team has grown (two motivated developers)

As I can not fall behind if the committers are so hard-working, I fixed a bug which seems to be a old one, at least the buggy code was old ;-)

Next small enhancement

Tonight I implemented another small features which was on the wish list for a long time now.

If you create a test method moreUnit will now use the line delimiter from the actual formatter setting.

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...

Move method refactoring support

I got feedback that move method refactoring is not working.

Yes thats absolutely true. Although there is already a class MoveMethodPartiticipant the Change was not created. Seems that I just forgot to implement it.

This is fixed and available in HEAD.

Implementing features is much more fun than working on the update site :-)

p2 and no end

Today I decided not to give up the attempt to p2-enable the update site and I found a blog post with a migration guide:

http://plosquare.blogspot.com/2009/05/migrating-eclipse-update-sites-to-p2.html

Perhaps I will get it work with this article, but why does eclipse not offer such a guide?

Again troubles with update sites

Today I wanted to prepare a new release of MoreUnit. But when testing everthing with the test update site the plugin does not work because of:

Unable to access file "plugins/org.moreunit_1.4.0.jar!META-INF/MANIFEST.MF".

WTH is going on? The Manifest is in the JAR, googling around did not help very much.

It is  really annoying to spend so much time about update sites. It is the first time thinking about stopping to work on this project and spending my freetime for something else.

It's working

Tonight I found out what I was doing wrong. I forgot to add the new version to the catgory.xml. As a consequence my update appeared but was uncategorized. Removing the corresponding checkbox showed the update. I fixed that and now the update appears as it should.
Not that a big thing (if you know what you have to do).

Fighting with update sites

Today I played around with my test update site, but with no success. It was not possible to add a new release and update to that (p2-enabled). I think it is a quite easy task for experienced eclipse plugin developers, but if you are a free-time open source developer who wants to concentrate on adding features to a plugin it is annoying to spend so much time for those things :-(

Test Updatesite p2-enabled

Tonight I uploaded a test update site on http://moreunit.sourceforge.net/org.moreunit.updatetest/ which should be p2-enabled. I used the File > Export > Deployable features to generate a artifacts.xml and category.xml which should be enough to p2 enable MoreUnit (hopefully). The update site seems to work so I think it's a good start.

Patch and p2

Tonight I integrated a patch to start tests from the CUT.
After that I started to read a little bit about p2 again, because MoreUnit is not p2 enabled yet. Last time I tried, it did not work properly and documenation was quite rare. Todays try was not very successfully too. Documentation about update sites on eclipse.org is outdated and the p2 site wiki did not offer a easy switch guide for plugin developers from older update sites :-(