Freitag, 28. Mai 2010

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 :-(

Donnerstag, 27. Mai 2010

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. hosts the new release already, but the official release will take some more days (to update documentation...)

Montag, 24. Mai 2010

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 ;-)

Sonntag, 23. Mai 2010

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