|
| Re: Determining the dependency tree for a given jar? [message #205871 is a reply to message #205766] |
Wed, 18 April 2007 22:57   |
Eclipse User |
|
|
|
Originally posted by: irbull.cs.uvic.ca
Hi Ric,
I'm actually working on a view that can do this as part of the PDE.
Currently there is a plug-in dependency view available, but it lists
everything as a tree, and if A depends on B and C, and B also depends on
C, C will show up twice. So therefore in this view, org.eclipse.osgi
shows up everywhere :).
In your case you just want the list of all required plug-ins I guess.
If you can open a bug against Eclipse, PDE (incubator), I will see what
I can do.
cheers,
ian
Ric Wright wrote:
> I have developed a plugin that, among other things, allows one to edit
> XML files of various types. I am using the XML editor that is part of
> the WST project which is in org.eclipse.wst.sse.ui jar. I can tell
> people who want to use my plugin to install WST, but that is a lot of
> stuff, most of which is NOT needed. Is there an easy way to determine
> the set of jars that are really needed? I could obviously do it by
> creating a fresh Eclipse without WST and install my plugin and
> org.eclipse.wst.sse.ui and find out what it complains about. Or spelunk
> through the sse.ui jar's manifest, etc. But surely there should be an
> easier way, something that walks the manifests. TIA.
|
|
|
| Re: Determining the dependency tree for a given jar? [message #206081 is a reply to message #205871] |
Thu, 19 April 2007 14:00 |
| Eclipse User |
|
|
|
Originally posted by: irbull.cs.uvic.ca
Actually Ric, I think PDE supports what you need. If you open the
Plug-in Dependency view, right click and "focus" on your particular
plug-in. Then select "Set Flat Layout" which is an action in the
toolbar you get a list of all required plug-ins.
cheers,
ian
Ian Bull wrote:
> Hi Ric,
>
> I'm actually working on a view that can do this as part of the PDE.
> Currently there is a plug-in dependency view available, but it lists
> everything as a tree, and if A depends on B and C, and B also depends on
> C, C will show up twice. So therefore in this view, org.eclipse.osgi
> shows up everywhere :).
>
> In your case you just want the list of all required plug-ins I guess.
>
> If you can open a bug against Eclipse, PDE (incubator), I will see what
> I can do.
>
> cheers,
> ian
>
> Ric Wright wrote:
>> I have developed a plugin that, among other things, allows one to edit
>> XML files of various types. I am using the XML editor that is part of
>> the WST project which is in org.eclipse.wst.sse.ui jar. I can tell
>> people who want to use my plugin to install WST, but that is a lot of
>> stuff, most of which is NOT needed. Is there an easy way to determine
>> the set of jars that are really needed? I could obviously do it by
>> creating a fresh Eclipse without WST and install my plugin and
>> org.eclipse.wst.sse.ui and find out what it complains about. Or
>> spelunk through the sse.ui jar's manifest, etc. But surely there
>> should be an easier way, something that walks the manifests. TIA.
|
|
|
Powered by
FUDForum. Page generated in 0.07758 seconds
] 
Search
Help
Register
Login
Home
