Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Issue with UNC file path for composite P2 repo in 0.17.0

If it should be a correct file URI for a UNC path, then it's actually five, but there are MANY tools, programs and libraries that interpret them wrong. UNC paths as URIs are difficult to say the least.




On 5 April 2013 07:23, Justin Georgeson <JGeorgeson@xxxxxxx> wrote:

The p2.repo.root property in the POM is defaulted to ////servername/share. Did you mean to have five slashes at the start, or four? On the command line I’ve tried

 

//servername/share

\\servername\share

\\\\servername\share

\\\\servername\\share

 

From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Andreas Magnusson
Sent: Thursday, April 04, 2013 11:42 PM
To: Tycho user list
Subject: Re: [tycho-user] Issue with UNC file path for composite P2 repo in 0.17.0

 

It seems that UNC paths as file:// URIs are very difficult. What formats have you tried? This is supposed to be the correct one: file://///servername/share/file.txt but that is no guarantee that its interpreted correctly by p2. 

/Andreas

On 5 apr 2013, at 00:43, Justin Georgeson <JGeorgeson@xxxxxxx> wrote:

I didn’t hit this testing the staged RCs. I’m seeing the “URI has authority component” error for repositories with a file: URI that goes over a UNC path

 

 

                <repository>

                    <id>rm</id>

                    <layout>p2</layout>

                    <url>file:${p2.repo.root}/repo/</url>

                </repository>

 

On Windows this fails with -Dp2.repo.root=\\server.example.com\p2 but I can open Windows Explorer, browse to that folder, copy it locally, then run successfully with -Dp2.repo.root=\mycopy\p2. I’ve tried multiple variations of forward and backward slashes for the UNC. It starts working again if I change from pointing to the composite URI to a specific child repo (the repos haven’t changed) or if I change tycho-version to 0.15.0. We didn’t take 0.16.0 because of [1] and [2] and I’m not sure if that would be related to what I’m seeing now. It makes no difference if I have a settings.xml <server> for this repo id. But like I said I didn’t run into this issue testing the staged RCs of 0.17.0. We have an http protocol version of the UNC path and that is working (confirming that [1] and [2] are fixed as reported), but it’s slower so I’d like to be able to use the UNC path for my automated builds. The staged build doesn’t seem to be there anymore so I can’t retest with it.

 

 


This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user


_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user



Back to the top