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 :-(
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...)
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 ;-)
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...
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...
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 :-)
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?
