Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 370505 - IResource setResourceAttributes does nothing on Linux ppc64 because libunixfile_1_0_0.so is missing
Summary: IResource setResourceAttributes does nothing on Linux ppc64 because libunixfi...
Status: CLOSED DUPLICATE of bug 350860
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.7.1   Edit
Hardware: Power PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-02 17:43 EST by Paul Allen CLA
Modified: 2012-02-03 10:34 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Allen CLA 2012-02-02 17:43:02 EST
Build Identifier: Version: 3.6.2 Build id: M20110210-1200

The IResource.setResourceAtrributes method no-ops because the libunixfile_1_0_0.so is not included in the Eclipse distribution on this platform.

My understanding is that the code should be falling back to use java.io interfaces on platforms where the native library is not available. But it does not appear to be using java.io and rather is simply returning without performing any function.




Reproducible: Always

Steps to Reproduce:
1. Using code like:

    IFile file = .... // Get an existing file from a project
    ResourceAttributes attrs = file.getResourceAttributes();
    attrs.setReadOnly(true);
    file.setResourceAttributes(attrs);

This always fails on the Linux ppc64 platform.
Comment 1 Szymon Brandys CLA 2012-02-03 08:44:14 EST
To what Java 1.5 API we should fall back for setting readonly attribute? I remember there was a guy who offered help in compiling natives on linux.ppc64, but he disappeared. Is there someone on your side who could compile the source on this platform?
Comment 2 Szymon Brandys CLA 2012-02-03 10:34:24 EST

*** This bug has been marked as a duplicate of bug 350860 ***