| PDE .product file only handles features **OR** plugins?? [message #321718] |
Thu, 25 October 2007 01:01  |
Eclipse User |
|
|
|
Originally posted by: none.ibm.com
The PDE product editor seems to suggest that a .product file can declare
*either* plugins *or* features. Is there any reason you can't declare both?
Also, if you choose plug-ins, the editor leaves declared features in the
file, and vice-versa. Shouldn't it remove them if they have no effect?
|
|
|
| Re: PDE .product file only handles features **OR** plugins?? [message #321723 is a reply to message #321718] |
Thu, 25 October 2007 03:52  |
| Eclipse User |
|
|
|
Originally posted by: zx.us.ibm.com
It's handles features OR plug-ins due to simplicity. If you want to
support both at the same time, feel free to file an enhancement request
and we'll review it. Note, that after 3.4, features will most likely
disappear which PDE will have to adapt too.
For leaving features in when you switch between plug-ins / features, you
should file a bug against PDE UI.
Cheers,
~ Chris
|
|
|
| Re: PDE .product file only handles features **OR** plugins?? [message #321748 is a reply to message #321723] |
Thu, 25 October 2007 16:04 |
| Eclipse User |
|
|
|
Originally posted by: none.ibm.com
This also affects building your product. If you don't have features
containing *every* plug-in needed in your packaged product, then you are
going to have a hard time using the productBuild scripts in PDE. What to
people normally do if they want the RCP platform with a handful of its
optional plug-ins, and then their own features on top of that?
"Chris Aniszczyk" <zx@us.ibm.com> wrote in message
news:ffp3ul$4bj$1@build.eclipse.org...
> It's handles features OR plug-ins due to simplicity. If you want to
> support both at the same time, feel free to file an enhancement request
> and we'll review it. Note, that after 3.4, features will most likely
> disappear which PDE will have to adapt too.
>
> For leaving features in when you switch between plug-ins / features, you
> should file a bug against PDE UI.
>
> Cheers,
>
> ~ Chris
|
|
|
| Re: PDE .product file only handles features **OR** plugins?? [message #321831 is a reply to message #321748] |
Mon, 29 October 2007 14:29 |
 Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
Behind the scenes, pde.build is building from features. When you use a .product
file, the build is just generating a feature for you.
I expect people generally provide their own feature that contains their plug-ins
and includes the org.eclipse.rcp feature to get the base platform. Providing
your own feature gives you more control over what is happening in the headless
build.
-Andrew
Randy Hudson wrote:
> This also affects building your product. If you don't have features
> containing *every* plug-in needed in your packaged product, then you are
> going to have a hard time using the productBuild scripts in PDE. What to
> people normally do if they want the RCP platform with a handful of its
> optional plug-ins, and then their own features on top of that?
>
> "Chris Aniszczyk" <zx@us.ibm.com> wrote in message
> news:ffp3ul$4bj$1@build.eclipse.org...
>> It's handles features OR plug-ins due to simplicity. If you want to
>> support both at the same time, feel free to file an enhancement request
>> and we'll review it. Note, that after 3.4, features will most likely
>> disappear which PDE will have to adapt too.
>>
>> For leaving features in when you switch between plug-ins / features, you
>> should file a bug against PDE UI.
>>
>> Cheers,
>>
>> ~ Chris
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03300 seconds
] 
Search
Help
Register
Login
Home
