Bug 27783

Summary:	Build output folder should not always be in the project subdirectories
Product:	[Eclipse Project] JDT	Reporter:	Ludovic Claude <ludovic_claude>
Component:	Core	Assignee:	Philipe Mulet <philippe_mulet>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3
Version:	2.1
Target Milestone:	2.1 M4
Hardware:	PC
OS:	Windows NT
Whiteboard:

Description Ludovic Claude

2002-12-05 13:00:37 EST

Please add support for output folders that are in a different directory (or 
drive) than the project working directory. Building a project on a network 
drive or Clearcase takes too much time, especially as the Scrubbing operation 
is slow.

Comment 1 Philipe Mulet

2002-12-06 05:28:47 EST

Linked resources allow you to achieve this in latest integration build.
Once a UI allows you to define these, you could basically mount an external 
location (external to this project) and have it be monitored by Eclipse. Then 
you can use it as your output folder, as you would do it already, and have 
actual classfiles generated to whatever location you need.

Also note, that once latest enhancements are surfaced in UI, you will also be 
able to associate each source folder with an individual output folder, and you 
can also add some exclusion filters to avoid building portions of a source tree.

Last, we will allow source folders to be nested in each other (as long as outer 
excludes the inner one).

This should provide you with good flexibility. UI isn't ready yet, but it 
should be available by milestone 4.

Comment 2 Philipe Mulet

2002-12-08 15:11:37 EST

Is it ok to close?

Comment 3 Ludovic Claude

2002-12-08 15:45:22 EST

Ok to close. So i have to wait for M4 then...

Comment 4 Philipe Mulet

2002-12-09 11:03:03 EST

There are ways to manually touch the .project or .classpath files to enable 
these features, but by M4 an official UI will be available.

Closing