[eclipsedarcs-develop] New patches

[Leif F. <hi...@le...>]

Hi everybody,

I have just pushed a few patches (including some older ones by Radek and
me, plus a number of newer ones). Notable changes include:

- I did a number of code cleanups, and also switched to Java 5 source format
  (so that we can use generics for more type safety) and to Eclipse 3.2
(see below).
- Renamed Current to Pristine (a change in the Darcs repo format, since
Darcs
  1.0.7 - both Darcs and EclipseDarcs are of course backwards compatible and
  can deal with the old repo format).
- You can now watch the output from the Darcs commands directly in the
Console.
  Open the Console View and select 'Darcs commands' from the View menu.
- There are new actions for 'darcs check' and 'darcs repair'. In addition, I
  have re-organized the context menu entries and added placeholder for other
  things that are not yet implemented (e.g. optimized etc.). So far I
have not
  managed to get these actions to correctly show up in the 'Team' menu, I'm
  working on that one.
- actions for recording and reverting from the synchronize view

The reason why I have started this sudden activism has to do with the
imminent
Eclipse 3.2 release. Actually, Eclipse 3.2 is finished, but since
eclipse.org wants
to do a simultaneous release of ten eclipse.org projects (which all
depend on Eclipse
3.2 and therefore still need to do some adjustments), the eventual
release will only
be at the end of this month (and, fitting to current vogue, that release
has a fancy and
useless code name too, namely "Callisto" ;-).

Now, when this 'Callisto' release happens, there will be a number of
different
download offers on the eclipse.org website. They will include only
Eclipse 3.2 and
the software from eclipse.org mostly. The notable exception is the Yoxos
distribution
(which is done by my company). It will be present on the eclipse.org
download site
and it includes plugins from all over the community, including
EclipseDarcs :-).

I think this is a great chance to get a slice of awareness for Darcs and
EclipseDarcs.
However, the thing is that the plugin must be ready for Eclipse 3.2 -
now. And voila -
I think I have just made that sure :-) (Hope I haven't introduced too
many bugs
thereby ... ;-). I have named the current state 0.2.3 and I'll see that
this (or possibly
another build that we may do in the next days, if necessary) goes into
the distribution.
Of course I'll also put that build to the usual update site
(http://leiffrenzel.eu/eclipse).

Apart from that, I also have some more experimental code, which I don't
think is
fit for anything :-( I'll give you an update about the happenings on the
record-front in
one of the next mails.

Ciao,
Leif