no support for linkedResources / "linked URIs"

[Charles Duffy (M1)]

Project 'yourproject' contains linked URIs but the 'org.vcs.bazaar.eclipse.core.repository.BazaarTeamProvider' repository provider does not supported them.

Contained in my .project is the following:

        <linkedResources>
                <link>
                        <name>WebContent/WEB-INF/lib/gwt-servlet.jar</name>
                        <type>1</type>
                        <locationURI>GWT_HOME/gwt-servlet.jar</locationURI>
                </link>
        </linkedResources>

See http://home.zingo.org/trac/mercurialeclipse/changeset/79 for a diff adding linked URI support to the Mercurial Eclipse plugin.

[Jamie Maher (jmaher-guser)]

This happened to me as well.. luckily it was an out of date linked resource that I just deleted the link to.

However, if this isn't going to be supported you should consider catching the TeamException and displaying an error message informing the user instead of just hiding the status window immediately..

org.eclipse.team.core.TeamException: Project 'My Project' contains linked URIs but the'org.vcs.bazaar.eclipse.core.repository.BazaarTeamProvider' repository provider does not supported them.
 at org.eclipse.team.core.RepositoryProvider$1.visit(RepositoryProvider.java:176)
 at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:58)
 at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:81)
..

[Guillermo Gonzalez (verterok)]

I plan to add support for liked resources.
It's targeted to 0.2 in the roadmap. I don't use linked resources, so I'm not aware of the impact of not supporting them. if this is considered a critical/blocking issue please let me know, and I 'll try to move it up in the roadmap.

Regards,

[Guillermo Gonzalez (verterok)]

Just a follow up.
liked resources are now supported (experimental), if you want to test it, it's available in the latest development snapshot build.

Regards.

[Jason Grey (jgrey-oco)]

This is critical/blocking for my team - I see you say above it's available in the latest development snapshot build - I just installed the latest from the snapshot update site (1.1.1.191), and it doesn't seem to be working yet. Is there a newer version that I can be testing?

Here's the behaviour I see:

1) create a new project in eclipse
2) populate it with some files (including linked resources)
3) file->team->share
4) choose bazar
5) click finish (using project root)
6) I see "executing: init myproject" in my eclipse console, but the bazaar configuration dialog has not gone away.
7) I click cancel in the bazaar configuration wizard
8) I refresh my project in eclipse, and I get the linked uri error.

Thanks for any help you can provide

[Guillermo Gonzalez (verterok)]

Thanks for the details to reproduce the problem.

There isn't a new version, what I tested (and it was working at that time) was to add a linked resource in a already shared project.

I'll work on this bug, hope I can get this done during the weekend.

Regards

[Guillermo Gonzalez (verterok)]

I just uploaded a new build (revno: 205).
Using this version I successfully completed the steps Jason detailed previously.

Cheers!

[Pablo Gil (pgilmon)]

Hi,

I'm using BzrEclipse 1.1.0 and bzr-xmloutput 0.8.3.

Project A has a dependency on project B and also son external folders linked. Project B has no dependencies. I can checkout project B without any problem, but when checking out project A, I get an error message saying that linked URIs are not supported. However, if I accept the error and click cancel the project is already on the workspace. Perhaps project dependencies are already supported but external linked folders are not?

[Guillermo Gonzalez (verterok)]

Hi Pablo,
Apologize the delay.
Thanks for the detailed description of how it breaks. I'll debug it using the same layout as I might missed some places when a check for link is needed.
Do you have a stacktrace with the cause of the errors? (take a look at the Error Log View)

Thanks a lot,

Regards.

[xaav (xaav)]

Changing this back to confirmed; this is obviously not being worked on.