Bug 15335 - Build output in phisical folder
Summary: Build output in phisical folder
Status: RESOLVED DUPLICATE of bug 6664
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: DJ Houghton CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-06 12:48 EDT by Ricardo de Lima CLA
Modified: 2002-05-15 19:00 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ricardo de Lima CLA 2002-05-06 12:48:19 EDT
Build output in phisical folder.
Out of 'Build output folder' configured on Properties of current project.
Option to choose phisical or relative folder to output my built classes.

ie.: output to 'c:\tomcat\webapps\mytest\web-inf\classes'.

Best regards,

Ricardo de Lima
lima@datran.com.br
Comment 1 DJ Houghton CLA 2002-05-06 14:49:03 EDT
Note that files living outside the project content area are not recognized by 
Eclipse.

Note that in the interm this can be accomplished by writing an Ant task which 
copies/moves the files to a different location on the file system.

Adding PM for comment on having the build output folder outside of the project 
content area.
Comment 2 John Arthorne CLA 2002-05-06 15:05:44 EDT
Looks like yet another duplicate of bug 6664.  The java builder could 
easily output to a location outside the project, but that would be a half-baked 
solution... if it's outside of the area that core knows about, there will be no 
resource deltas, and no way for dependent project builders & listeners to know 
what changed.  This can only be properly addressed by folders that can be mapped 
to arbitrary locations.
Comment 3 John Arthorne CLA 2002-05-15 19:00:53 EDT

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