Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 366328

Summary:

Semantic File System: WebDAV content provider improvements

Product:

[Eclipse Project] e4

Reporter:

Enrico Bacis <enrico.bacis>

Component:

Resources

Assignee:

Project Inbox <e4.resources-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

enhancement

Priority:

CC:

eduard.bartsch

Version:

unspecified

Target Milestone:

---

Hardware:

All

OS:

All

Whiteboard:

stalebug

Attachments:

Description	Flags
Patch for org.eclipse.core.resources.semantic.examples	none
Patch for org.eclipse.ui.resources.semantic.examples	none

Description Enrico Bacis

2011-12-11 06:28:19 EST

Build Identifier: Version: 3.7.1 Build id: M20110909-1335 (latest SFS plugin downloaded)

I've written a patch to improve WebDAV content provider for the Semantic File System.

Improvements List:
- Wizard follows permanently moved paths and warning of temporarily moved paths (useful when the user forget the final slash for a WebDAV collection path).
- Date was not correct (due to month count that start from 0 in WebDAV).
- Correctly manage and create WebDAV collections (directories).
- Added the ability to delete resources in repository (files and collections).
- Right management.
- Synchronization mechanism widely improved (works for collections too).
- Improved error messages for synchronization, lock, unlock, create and delete. It gives also helpful hints to resolve the problem.
- Some other corrections.

Reproducible: Always

Comment 1 Enrico Bacis

2011-12-11 06:30:06 EST

Created attachment 208222 [details]
Patch for org.eclipse.core.resources.semantic.examples

Comment 2 Enrico Bacis

2011-12-11 06:30:47 EST

Created attachment 208223 [details]
Patch for org.eclipse.ui.resources.semantic.examples

Comment 3 Enrico Bacis

2011-12-11 06:31:46 EST

*** Bug 364524 has been marked as a duplicate of this bug. ***

Comment 4 Lars Vogel

2019-09-04 03:12:12 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it and remove the stalebug whiteboard tag. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--