[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-update-dev] Using pde to build a feature and the associated branding plugin
|
Actually, it is Java Tooling that brings it back. The feature project has a
Java nature, and output folder for Java build is set to the 'bin'
directory. Feature project has a Java nature for two reasons:
1) To allow you to build custom install handlers and other Java classes
that you may desire to ship as 'data' archives
2) To allow the feature project to be seen in Package Explorer view
alongside your plug-ins (otherwise you would have to go back and forth
between Navigator and Package Explorer views all the time).
Regards,
Dejan Glozic, Ph.D.
Application Development
D2/MY7/8200/MKM
IBM Canada Ltd.
Tel. 905 413-2745 T/L 969-2745
Fax. 905 413-4854
Pat
McCarthy/Raleigh/IBM@IBMUS To: platform-update-dev@xxxxxxxxxxx
Sent by: cc:
platform-update-dev-admin@ Subject: Re: [platform-update-dev] Using pde to build a feature and the
eclipse.org associated branding plugin
08/07/2002 08:47 PM
Please respond to
platform-update-dev
What is the role of the bin dir in a feature project? I see it collecting
copies of any file in the feature project that gets modified (edit or
generate via a build process or other action).
And... I see that the feature manifest builder keeps bringing it back if I
try to delete it - but I'm not sure why - or why it brings back two when
deleted (bin>bin).
Pat McCarthy
_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev
