This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 127441 - Mercurial plugin does not work in clean build
Summary: Mercurial plugin does not work in clean build
Status: RESOLVED INVALID
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Mercurial (show other bugs)
Version: 6.x
Hardware: Macintosh Mac OS X
: P1 blocker (vote)
Assignee: issues@versioncontrol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-15 05:20 UTC by David Vancouvering
Modified: 2008-02-15 23:55 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Vancouvering 2008-02-15 05:20:53 UTC 
If you do a clean build of NetBeans, the Mercurial plugin complains as soon as you try to do something (like "status")
saying that it does not support the version of Mercurial (some-hex-code).  

The workaround is to manually build the NBM, uninstall the Mercurial plugin, and install the local NBM.

This is a fairly big annoyance.
Comment 1 David Vancouvering 2008-02-15 05:31:25 UTC 
Hm, I just tried to rebuild and install the NBM, and it didn't work.  I also tried this with a clean userdir.  So I at
present have no workaround - Mercurial plugin is no longer working for me.

Product Version: NetBeans IDE Dev (Build 080214)
Java: 1.5.0_13; Java HotSpot(TM) Client VM 1.5.0_13-121
System: Mac OS X version 10.4.11 running on i386; MacRoman; en_US (nb)

Based on parent 66f083d3536b
Comment 2 Padraig Obriain 2008-02-15 08:25:17 UTC 
I am not sure I understand what you are doing.

Have you cloned from http://hg.netbeans.org/main?

What exactly have you done then?
Comment 3 David Vancouvering 2008-02-15 16:54:09 UTC 
I did a clean clone from hg.netbeans.org, ant clean, ant -Dcluster.config=basic, and then bring up NetBeans under a
clean userdir, and I get this situation.
Comment 4 John Rice 2008-02-15 17:32:57 UTC 
What version of Mercurial do you have installed? 

We only support offiical 0.9.3, 0.9.4 and 0.9.5 builds, not development builds or other unofficial build bundles. We
test against 0.9.5. When you get the dialog, telling you you have an unsupported version, you just have to say yes and
you can run with this unsupported version of Mercurial. You may have some issues we haven't seen, particularly if any of
the command line output is changing, error messages or error codes are changing in head.
Comment 5 David Vancouvering 2008-02-15 19:55:51 UTC 
Note that I'm on a Mac.  When I do 'hg --version' I get

Mercurial Distributed SCM (version bc475d1f74ca)

Copyright (C) 2005-2007 Matt Mackall <mpm@selenic.com> and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

The version number matches the one printed out in the error message.

I will try to say it's OK to use the unsupported version.  If memory suits me, this didn't work.  But if it does, I'll
close this bug, although we need to know how to work with Mac versions of hg without popping up this error message, IMHO.
Comment 6 David Vancouvering 2008-02-15 19:57:33 UTC 
Accepting the mercurial version seems to work.  I'll close, and will re-open if I encounter issues again where I have to
build the NBM to be able to use mercurial.
Comment 7 John Rice 2008-02-15 23:55:14 UTC 
David - you have a point if we are on the Mac we should not warn the user if they are using the official 0.9.5 Mac build. 
With the version below I do not get any warning as expected and hg version gives us back the 0.9.5 version string we are
expecting. If you try this version and still get a warning then its a bug.

http://mercurial.berkwood.com/binaries/Mercurial-0.9.5-py2.5-macosx10.5.zip