| How can I find out, which plugin/feature refers to a missing feature? [message #323815] |
Wed, 09 January 2008 08:40  |
Eclipse User |
|
|
|
I want to install a new plugin but whenever I select the desired feature
from the list of available features on the update site the top of the
dialog signals a configuration error:
--------------------------
The current configuration contains errors and this operation can have
unpredictable results.
Java Persistence API Tools (1.0.0.v200706250000-77--CYQCCz-CuNPCCCF)
requires feature "org.eclipse.datatools.connectivity.feature".
--------------------------
and the Next and the Finish button are grayed out, i.e. I can not
continue and I can not install the desired feature.
If I double check on the Help => SW Updates => Manage Configuration =>
Product Configuration page all the plugins listed see fine, enabled and
none indicates any error. The log file only lists a couple of entries
that all read somethings like:
-----------------------
Could not install bundle plugins/<foo>.jar Bundle "<foo>" version
"<bar>" has already been installed from: <somwhere else>.jar
-----------------------
None of these entries look harmful. The jarfile version suffixes always
matches, so these should be just duplicates added by different .jars.
How can I figure out, why eclipse considers my configuration
inconsistent and which plugin refers to that apparently missing
"org.eclipse.datatools.connectivity.feature"?
Michael
|
|
|
|
|
| Re: How can I find out, which plugin/feature refers to a missing [message #323905 is a reply to message #323903] |
Fri, 11 January 2008 15:06  |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"Jim Bethancourt" <automatic@javalobby.org> wrote in message
news:4765434.3371200078616975.JavaMail.root@cp1.dzone.com...
> I'm having the same problems.
> Doing a quick search I found this thread, but installing the whole DTP
> seems a little much.
In general, although Eclipse expresses dependencies at a bundle level
(because it is an OSGi implementation), the Eclipse development teams work
at a feature level (because we're humans).
Realistically, what that means is that if a plug-in from one feature 'A'
(say, WTP) depends on a plug-in from another feature 'B' (say, JDT), then
the A developers are assuming that anyone installing 'A' has also installed
'B'; and that's how the testing will work. You might technically be able to
run A without having all of B's plug-ins installed, but no one will have
tested that scenario. I'm under the vague impression that the update
manager is supposed to ensure these component-level dependencies, but I'm
not expert on that. In any event, what I'm saying is that it's usually not
a good idea to try to just install a single plug-in; you really should
install features, even if it seems wasteful.
That said, I don't know anything about the particular DTP dependency that
spawned this thread. I'd suggest posting on a newsgroup that is better
targeted at the Java Persistence API implementation.
|
|
|
|
Powered by
FUDForum. Page generated in 0.04941 seconds
Home