Jump to: navigation, search

Difference between revisions of "Resource Deltas for External Folders"

(Problem Summary)
Line 3: Line 3:
 
The resources plug-in broadcasts resource change events for files and folders in the workspace. This allows clients to react to changes that occur in those resources, and in the underlying file system.  There is no way to receive resource change events for files and folders in the file system that do not belong to the workspace.
 
The resources plug-in broadcasts resource change events for files and folders in the workspace. This allows clients to react to changes that occur in those resources, and in the underlying file system.  There is no way to receive resource change events for files and folders in the file system that do not belong to the workspace.
  
In the Java development tools, it would be useful to be able to add folders outside the workspace to a build path of a Java project.
+
In the Java development tools, it would be useful to be able to add folders outside the workspace to a build path of a Java project. This is not currently supported because there is no way to incrementally track changes to those external folders during a build. This is acceptable if the contents of the external folders never change, but will not be acceptable for end users when the folders are modified. The expectation is that the Java builder will do the right thing, and react to changes in the external folders.
  
 +
One notable example of this requirement comes from plug-in developers using EMF-generated
 +
 +
 +
== Potential Solutions ==
 +
 +
== Plan of Action ==
  
 
== References ==
 
== References ==
  
 +
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=8655 Bug 8655 DCR - Support for external class folders]
 
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=77113 Bug 77113 - Adding a directory-pointing variable to the project build path]
 
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=77113 Bug 77113 - Adding a directory-pointing variable to the project build path]
 +
 
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=81402 Bug 81402 - Allow external classfolders from a container]
 
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=81402 Bug 81402 - Allow external classfolders from a container]
 +
 
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=109137 Bug 109137 - Support compiling runtime workspace plugins against the launching workspace]
 
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=109137 Bug 109137 - Support compiling runtime workspace plugins against the launching workspace]
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=182537 Bug 182537 - Enhance classpath container to support external class folders]
 
  
== Potential Solutions ==
+
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=182537 Bug 182537 - Enhance classpath container to support external class folders]
 
+
== Plan of Action ==
+

Revision as of 09:46, 4 October 2007

Problem Summary

The resources plug-in broadcasts resource change events for files and folders in the workspace. This allows clients to react to changes that occur in those resources, and in the underlying file system. There is no way to receive resource change events for files and folders in the file system that do not belong to the workspace.

In the Java development tools, it would be useful to be able to add folders outside the workspace to a build path of a Java project. This is not currently supported because there is no way to incrementally track changes to those external folders during a build. This is acceptable if the contents of the external folders never change, but will not be acceptable for end users when the folders are modified. The expectation is that the Java builder will do the right thing, and react to changes in the external folders.

One notable example of this requirement comes from plug-in developers using EMF-generated


Potential Solutions

Plan of Action

References

Bug 8655 DCR - Support for external class folders Bug 77113 - Adding a directory-pointing variable to the project build path

Bug 81402 - Allow external classfolders from a container

Bug 109137 - Support compiling runtime workspace plugins against the launching workspace

Bug 182537 - Enhance classpath container to support external class folders