Re: [tycho-user] Pathproblems with tycho-p2-extras PublishFeaturesAndBun

["Sievers, Jan" <jan.sievers@xxxxxxx>]

https://bugs.eclipse.org/bugs/show_bug.cgi?id=352755  

From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Markward Schubert
Sent: Donnerstag, 10. November 2011 19:13
To: tycho-user@xxxxxxxxxxx
Subject: [tycho-user] Pathproblems with tycho-p2-extras PublishFeaturesAndBundleMojo

Hello everybody!

I am experiencing some problems with the tycho-p2-extras-plugin.
After setting up a scenario pretty much like it is described in this little howto: https://docs.sonatype.org/display/TYCHO/Tycho-extras+-+FeaturesAndBundlesPublisher,

I found, that the commandline statet, that the call to FeaturesAndBundlesPublisher was ok, but I was missing the constructed repository. After experimenting with some pathes, i finally managed to get it working with a simple path, not containing any whispaces. 

Then looking into the code i found, the following:

(Taken from the code: https://github.com/sonatype/tycho-extras/blob/master/tycho-p2-extras-plugin/src/main/java/org/eclipse/tycho/plugins/p2/extras/PublishFeaturesAndBundlesMojo.java#L113)

contentArgs.add(sourceRepositoryDir.toString());
[...]
launcher.addArguments("-artifactRepository", artifactRepositoryDir.toURI().toString(),"-metadataRepository", metadataRepositoryDir.toURI().toString());

I guess, that FeaturesAndBundlesPublisher also supports publishing to destinations with other protocols than file:/, so I would not call the code above a bug. But what happens on my WindowsXP machine is, that "C:\Dokumente und Einstellungen" is transformed to "C:\Dokumente%20und%20Einstellungen", which is then passed to the commandline-call. 

Then a folder named exactly "C:\Dokumente%20und%20Einstellungen" is created, with my published repository in it, thus explaining, why no FileNotFound type of Exception was thrown. It simply read from the correct folder and published to the new, wrong folder.

Actually I don't have enough insight into the requirements of P2ApplicationLauncher and the FeaturesAndBundlesPublisher of eclipse to create a concious patch, so I just report this behaviour to the group here. Maybe even this is not a bug and there is a nice workaround, other than forcing everybody in the team to never ever use a folder with whitespaces.

Any hints about, proper escaping or something similar are very welcome.

Regards, 

Markward