MercurialEclipse 1.3.1019 released

MercurialEclipse 1.3.1019 on MacOs X Leopard

MercurialEclipse 1.3.1019 on MacOs X Leopard

As of today, the first of the 1.3 versions of MercurialEclipse is released: 1.3.1019. Since we heard you like bugs fixed, we did some bug fixing, but also added some new features. The changelog looks like this:

  • Enable remote compare for outgoing changesets (r1000-r1004).
    Outgoing changes can now be shown in the Eclipse compare editor.

    Outgoing changes can now be shown in the Eclipse compare editor.

  • Fix multi-threading issues (e.g. r997).
  • Use hgattic extension for shelving/unshelving if it is available (r1012).
    If the HgAttic extension is installed, shelve and unshelve will use it.

    If the HgAttic extension is installed, shelve and unshelve will use it.

  • Support aliases for repositories
  • Beginnings of a project property page (r1016).
    A property page shows associated repositories.

    A property page shows associated repositories.

  • Bumped default timeout (r1017).
  • Saved commit messages are now configurable (r955).
  • Added option to choose color and font for decoration of changed, unknown, removed, added, ignored and conflicting files (r957).
    20090215_20090214_bild_61

    Colors and fonts of decorations can now freely be chosen.

  • Fixed massive performance bug in status decoration. Big projects will see major speed-ups when an incremental build is triggered, as builds don’t trigger status updates anymore (r981).
  • Fix for username caching in repository location.
  • Allow ignoring resources that are not in the status unknown.
  • Chinese translation, fix log parsing, add Options page for Import/Export of patches.
  • Added commit message dropdown in commit dialog #83 (r952).
    The commit dialog now allows to select a previously used commit message.

    The commit dialog now allows to select a previously used commit message.

    After selection of a previous commit message, it is automatically pasted into the message area.

    After selection of a previous commit message, it is automatically pasted into the message area.


VN:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.11_1134]
Rating: +1 (from 1 vote)

Verwandte Artikel:

  1. New commit dialog in MercurialEclipse
  2. MercurialEclipse 1.4.1280 released
  3. Another commit dialog post…

Comments (10)

Michele MauroFebruar 17th, 2009 at 17:45

Any support for bundle/unbundle? Where I work we use bundles a lot to spread changes around in a serverless way. Is any support for these commands included/planned in the plugin?

Thanks in advance,

Michele Mauro

VA:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)
VA:F [1.9.11_1134]
Rating: 0 (from 0 votes)
BastianFebruar 17th, 2009 at 19:24

It is neither planned nor included, but if you file an enhancement in our trac, it should be easy to implement. Please include a preferred workflow – this way we can ensure we don’t design a crappy GUI for your needs :).

VN:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.11_1134]
Rating: 0 (from 0 votes)
BrunoFebruar 18th, 2009 at 17:53

Great work so far, thumbs up.

VA:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)
VA:F [1.9.11_1134]
Rating: 0 (from 0 votes)
BastianFebruar 18th, 2009 at 18:41

Thanks :)

VN:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.11_1134]
Rating: 0 (from 0 votes)
pachiFebruar 25th, 2009 at 11:52

The plugin looks really great!. I’m giving it a try on windows, using Eclipse ganymede and the latest plugin release 1.3.1019. So far I can import an existing project and files get decorated following their status, but I can’t get the history view to work. It doesn’t error out, but just displays a white window. Is there any component dependency for eclipse I need to install to make it work?. I thought it could have to do with the lack of a working hgtk, but now I have tried with it and it doesn’t work either.
Any ideas?

VA:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)
VA:F [1.9.11_1134]
Rating: 0 (from 0 votes)
BastianFebruar 25th, 2009 at 17:26

Hm. You don’t need any special components. What do you see in the Mercurial console? I seem to remember a few people had that issue, but it was resolved. Please file a bug in our trac at http://assembla.com/spaces/mercurialeclipse. Did you try to right-click on the project and select Team -> Show History from there? Another option would be to delete all style files from …/yourworkspace/.metadata/.plugins/com.vectrace…./ and then restart Eclipse and try it again.

VN:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.11_1134]
Rating: 0 (from 0 votes)
pachiFebruar 25th, 2009 at 18:53

Bastian, I’ve tried to file a ticket but couldn’t as trac is giving me a traceback :(. I’ve tried to delete the style files and restarted eclipse as well as using the project context menu instead of the file or editor views ones, without any success.

The console output show a normal session:
C:\winp\Mercurial\hg.exe paths
Done in 0:00.043 min.

C:\winp\Mercurial\hg.exe debuginstall
Done in 0:00.001 min.

C:\winp\Mercurial\hg.exe status -marduc
Done in 0:00.086 min.

C:\winp\Mercurial\hg.exe identify -i –debug
Done in 0:00.145 min.

C:\winp\Mercurial\hg.exe log –debug –style D:\programa\eclipse\.metadata\.plugins\com.vectrace.MercurialEclipse\log_style –rev 949f2a42340cde13e1cf67590e4adbaa3eb376e4
Done in 0:00.138 min.

and these commands work fine when issued in a system console.

You can find me at the #mercurial IRC channel (pachi) and could provide more help or try other things to find the culprit.

Thanks!

VA:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)
VA:F [1.9.11_1134]
Rating: 0 (from 0 votes)
BastianFebruar 26th, 2009 at 08:00

I get the traceback as well. Seems to be something special with your ticket as other tickets still work :). As for IRC, I’ll see what I can do, but currently, I have a lot of stuff to organize in my spare time, so my visits in #mercurial are rather seldom…

VN:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.11_1134]
Rating: 0 (from 0 votes)
pachiFebruar 26th, 2009 at 14:29

With the tip you gave me about other ticket reporting a similar problems I found it (ticket #100) and could make it work fine after running eclipse -clean

Yay!

I received a mail after the ticket report (#132) but can’t open it to add the previous comment. I have replied to that mail just in case it gets added to the ticket.

Thanks!

VA:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)
VA:F [1.9.11_1134]
Rating: 0 (from 0 votes)
BastianFebruar 26th, 2009 at 19:15

Ah cool. Then I can only hope you enjoy using the plugin now in all its glory ;-)!

VN:F [1.9.11_1134]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.11_1134]
Rating: 0 (from 0 votes)