Irrelevant Meta 0.1 dependency in SourceHgWeb

[Amenel]

SourceHgWeb has a dependency to Meta 0.1. But there's no link to the Meta plugin nor any mentions of it in mantisbt-plugins.

According to a March 2013 e-mail message by John Reese ( http://comments.gmane.org/gmane.comp.bug-tracking.mantis.general/3434 ) that I found after a Web serch, "The original Meta plugin was rolled into the Source Integration framework a long time ago."

Can we consider then that he Meta 0.1 dependency is a remnant of old times?
Is it safe to simply edit the SourceHgWeb.php file and remove the Meta 0.1 dependency?

[dregad]

I added the SourceHgWeb plugin to the repository exactly as it was given to me by its author (@davidhicks), without testing or anything (I don't use Mercurial at all).

Can we consider then that he Meta 0.1 dependency is a remnant of old times?

Probably yes.

Is it safe to simply edit the SourceHgWeb.php file and remove the Meta 0.1 dependency?

I believe that's exactly what @jreese suggested. Did you actually test this ? If yes, please confirm that it works and I'll update the plugin.

[Amenel]

I have removed the Meta dependency and installed both plugins (Source integration and HgWeb integration).

I can't report any progress yet because I haven't made any: I am stuck at the repository creation and configuration step. My root repository is in a subdomain and access is htdigest-protected. Among my projects, one is called Oblivion and stored in vcs.domain.tld/oblivion-oo/

Upon entering that address in a browser, I have to authenticate before I can see the source control history. Via Eclipse, I also have to provide user credentials. Import Lastest Data yields nothing, which isn't surprising since I haven't indicated any user credentials.

Moreover, I believe the fields in the "Manage repository" form could use some explanatory text. From the Mercurial point of view, I have one repository and several projects in it. From what I understand of the Source integration plugin's POV, I should create several "repositories", one for each project.

On another point, I wonder why there are URL, HgWeb Root URL and HgWeb project in the repository configuration form (Update Repository). Put differently, http://vcs.domain.tld/oblivion-oo/ in the "URL" fields feels redundant when I have http://vcs.domain.tld/ in "HgWeb Root URL" and "oblivion-oo" in "HgWeb project".

To sum it all up, I have to determine whether password-protected repositories can be configured and to make concepts match. I believe I'll have to delve into the source code. But I have other tasks to push forward first. It might take some time (weeks) before a further report here.

PS: I have read Chris Dornfeld's post at http://www.unitz.com/u-notez/2009/10/subversion-svn-integration-mantisbt/ . It clarifies some points and leads me to believe that SourceHgWeb does not yet support authentication-protected repos. To be confirmed.

[dregad]

I have removed the Meta dependency and installed both plugins

OK, I'll update the code accordingly, and then close this issue.

With regards to the other setup problems you're facing, I am afraid I can't help you much as I do not have any experience with Mercurial and how it works. Just a couple comments

the fields in the "Manage repository" form could use some explanatory text

Documentation is a long-standing issue that noone found the time to address so far (see #18)

leads me to believe that SourceHgWeb does not yet support authentication-protected repos

Your assumption is probably correct.

You might be able to get some help and support from other users (see http://mantisbt.org/support.php), mainly on the mailing lists and forums; also, even though he does not actively contribute to Mantis or this plugin anymore, you may be able to catch John Reese on IRC.

Feel free open other issues to track other individual problems, or even better if you do end up delving into the code and fixing/improving things, submit pull requests.