Bug 71591 - Output folder is forced to be inside the project
Summary: Output folder is forced to be inside the project
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1.2   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: 3.1 M1   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-06 14:44 EDT by noway CLA
Modified: 2004-08-11 08:19 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description noway CLA 2004-08-06 14:44:29 EDT 
Some high-end SCM's (including the one we're using at the moment - vesta)
require that you do NOT checkin binaries.

Eclipse forces you to dump binaries into your project folder.

There is no justification given in the docs for WHY eclipse does this, and I
cannot think of a rationale for forcing it - why should eclipse think it is
cleverer than I, the programmer, and force me not to do an entirely sensible
(and, in this case, entirely necessary) thing?

The SCM will not let you checkin with a non-source directory of binaries present
, unless you check in the entire binaries, and eclipse refuses to behave nicely
and just do the decent thing - let the programmer decide where to output to!
Comment 1 Olivier Thomann CLA 2004-08-06 14:50:52 EDT 
Eclipse is simply forcing a linked folder to be within the project, but that
linked folder can point whereever you want.
So you can create a linked folder to a folder outside the project and you set
this linked folder to be the output folder.
Does this solve your issue?
Comment 2 Kent Johnson CLA 2004-08-11 08:19:17 EDT 
Please reopen if linked folders do not solve your problem.