|
|
Re: Unable to find feature.xml in directory... [message #461670 is a reply to message #461668] |
Tue, 16 January 2007 06:15 |
Alexander NyÃ?en Messages: 38 Registered: July 2009 |
Member |
|
|
Hallo,
yes, the feature jars do of course contain the feature.xml files (I forgot
to mention). The problem does not seem to be Windows specific, because the
same problems occur when trying to executing my JUnit Tests for the headless
build on my Linux GTK build machine. I would expect them to be directories
and I think this is the root cause, the unpacking of the plugins seems to be
a following mistake. Is there an easy way to force the unpacking of the
features for my headless build?
Alexander
"Alex Blewitt" <alex_blewitt@yahoo.com> schrieb im Newsbeitrag
news:18147955.1168927169378.JavaMail.root@cp1.javalobby.org...
> The features are expected to be directories, rather than compressed Jars.
> Is that the case? And do the feature.xml files exist?
>
> The other thing is that Windows has a limit of 256 characters for file
> names, which frequently gets blown when having features with qualifiers
> and installed into a documents and settings directory. There was work done
> recently to use the UNC paths to enable it, but this may not have been
> done for the feature stuff.
>
> If you install it into c:, does it work then? If so, I'd suspect the path
> limit. Getting rid of the feature qualifier might also help.
>
> You might want to consider raising a bug at https://bugs.eclipse.org with
> respect to the feature; it's quite possible that the feature code just
> uses java.io.File instead of the UNC mechanism.
>
> Alex.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03680 seconds