Bug 17444 - Assumption: output is in /bin folder
Summary: Assumption: output is in /bin folder
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Wassim Melhem CLA
QA Contact:
URL:
Whiteboard:
Keywords: readme
Depends on:
Blocks:
 
Reported: 2002-05-23 14:39 EDT by DJ Houghton CLA
Modified: 2002-10-19 13:58 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description DJ Houghton CLA 2002-05-23 14:39:12 EDT
build F1 on WinXP.
IBM JRE 1.3.1

PDE assumes that a plugin's output is in the /bin folder.
I created a new plugin and set the source folder to be /src and the output 
folder to be /output and it could not find my classes to load.

Presumably this is because we are automatically running "-dev bin". 
Should we be adding the output folders from each project?
Comment 1 Dejan Glozic CLA 2002-05-23 18:13:54 EDT
Is it even possible? I know we are making a simplifying assumption here, but I 
would not like to complicate matters here if not needed. If you have 
heterogeneous situation (some plug-ins use 'out', some 'output', some who knows 
what), what would the argument look like?
Comment 2 DJ Houghton CLA 2002-05-24 10:00:03 EDT
I believe that the argument for the -dev command line parameter is a comma-
separated list of paths.

It should be in that running.html document...if I can find it. :-)
Comment 3 Dejan Glozic CLA 2002-05-24 10:08:47 EDT
OK, not too hard to scan the projects and collect a list of unique output 
directories.
Comment 4 Wassim Melhem CLA 2002-08-13 16:12:46 EDT
Fixed.  
Code has been released in HEAD.
Also, the new plug-in project creation wizard allows you now to name the build 
output folder anything you want.
Comment 5 Vincent Massol CLA 2002-10-19 13:58:21 EDT
Hi,

I'm using build 200210150832 of Eclipse 2.1 and I had my output folder set to 
target/ and it was not working. Took me quite a long time to reach this bug 
report ...

I have not used the plugin wizard to create my plugin (is that a requirement?).

It doesn't seem this bug is fixed in CVS head or there is something I don't 
understand.

Thanks
-Vincent