Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geclipse-dev] Unwanted UI dependencies

I reviewed EFS plugins and I choose solution #1, since it does not lead to bundled filesystem implementations.

It was done this way because we agreed on this year ago (that there is no sense to increase the number of plugins, esp. when new plugin will contain only 10 classes).

The removal of this dependencies is not trivial, I take care of it now.

Markus Knauer pisze:
I was waiting for several days now, but nothing happened here. No comments. Just nothing. Silence. Either this posting wasn't read by anybody, or it has been ignored.

Obviously no (well, almost no) changes made it into our M4 which would have been the perfect milestone to fix such dependency issues.

So, please, when you read this on Monday: Fix it as soon as possible. If your are not sure what to fix, and how to fix it, please ask Mathias or me. Many of this problems are caused by a dependency to org.eclipse.compare (which should be easy to remove), but some plug-ins contain both, UI and core classes mixed in one bundle. In that case I suggest 1) below. Again: If unsure, please ask.

On Wednesday 26 March 2008, Stuempert, Mathias IWR wrote:
Hi All,



I just got a user request to remove the UI dependencies from
eu.geclipse.core.filesystem and the eu.geclipse.efs.* plug-ins. Yes, you
got it right, there are indeed dependencies to the UI from these
plug-ins and even worse eu.geclipse.core itself depends on the UI. I can
fix eu.geclipse.core until the M4 release on Friday since this is just a
minor change. Nevertheless it will be more complicated to do the same
for the efs plug-ins since these plug-ins mix core functionality with ui
functionality like preference pages and actions. So we need a quick
decision here!



I see 2 possibilities:



1)       Create an extra ui plug-in for each efs plug-in, e.g.
eu.geclipse.efs.gridftp.ui, and move the ui functionality to these

2)       Incorporate the ui functionalities into the general middleware
ui plug-ins, e.g. eu.geclipse.globus.ui (BTW, I do not see a
eu.geclipse.glite.ui?!)



I would vote for solution 2 since we are doing something similar for the
core stuff. There we also have several non-ui plug-ins and one ui
plug-in. So what are the opinions? Especially Markus and Mateusz should
comment on this (but of course everybody is asked to join the
discussion). If somehow possible I would like to have these changes in
the M4!


Back to the top