| Plug-in Project Problems [message #301093] |
Thu, 23 March 2006 12:15  |
Eclipse User |
|
|
|
Originally posted by: barlock.usDOT.ibmDOT.com
With Eclipse 3.1, I've been trying to convert an existing Java project to a
plug-in project. Two problems:
(1) I used the PDE tools to convert the project (which we'll call "project
A"). It created a MANIFEST.MF. In project B, I tried to add project A as a
required plug-in on the Dependencies page of the plug-in editor. Project A
did not show up in the list -- until I added an extension to project A.
This created a plugin.xml -- and made project A visible on the list of
available plug-ins for project B's dependencies. I deleted the extension,
leaving behind an "empty" plugin.xml -- and I can still see project A as a
possible required plug-in for project B. This seems like an Eclipse bug to
me. Yes?
(2) IIRC, with Eclipse 3.0, all packages in a plug-in defaulted to being
visible to other plug-ins -- with the click of one radio button. With 3.1,
it looks like I have to enumerate all of the visible packages on the Runtime
page of the plug-in editor and select their visibility. This seems like a
maintenance problem -- add a new package and you have to remember to update
the manifest. Is this the way 3.1 works? Any way to get the old behavior?
Chris
|
|
|
|
| Re: Plug-in Project Problems [message #301103 is a reply to message #301094] |
Thu, 23 March 2006 14:35  |
| Eclipse User |
|
|
|
Originally posted by: barlock.usDOT.ibmDOT.com
> I create plugins with MANIFEST only all of the time, and they show up in
> the required-plugin list.
>
> Maybe you hadn't saved the manifest, or maybe the change wasn't being
> caught by a PDE resource listener so it could update the plugin
> information (that would be a bug).
>
>>
>> (2) IIRC, with Eclipse 3.0, all packages in a plug-in defaulted to being
>> visible to other plug-ins -- with the click of one radio button. With
>> 3.1, it looks like I have to enumerate all of the visible packages on the
>> Runtime page of the plug-in editor and select their visibility. This
>> seems like a maintenance problem -- add a new package and you have to
>> remember to update the manifest. Is this the way 3.1 works? Any way to
>> get the old behavior?
>
> no, the old behaviour is gone. With the manifests, you have to
> deliberatly list packages that you want visible.
>
> In 3.2 I think they added to the PDE Tools something that would "clean up"
> the manifest ... i.e. it'll add any new packages for you.
Thanks, Paul!
|
|
|
Powered by
FUDForum. Page generated in 0.03535 seconds
Home