Home » Eclipse Projects » Plugin Development Environment (PDE) » Plugin not loading from dropins directory
Plugin not loading from dropins directory [message #662513] |
Wed, 30 March 2011 21:25 |
Kevin Allen Messages: 3 Registered: March 2011 |
Junior Member |
|
|
Hi all,
I've written my first plugin, a custom classpath container, to help simplify the sharing of our project, which we're distributing to our developers to place in their /dropins directory. It seems to work in good order - mostly.
For one specific developer (my boss, ironically enough) the container doesn't show up. It's not available as an entry on the library list, it doesn't show up in the Installation Details/Configuration listing, no errors in the log, nothing... We've tried it with 3.5 (our standard) and 3.6 (which he upgraded to). So far, nobody else has had a problem.
He CAN see another classpath container we put in the /dropins, so I assume it's something with my plugin that's interacting with something in his system. But I'm at a loss - I get no problems from anyone else's installation, and absolutely no feedback from his system. It's like it just doesn't recognize that it's there.
Thanks in advance.
|
|
|
Re: Plugin not loading from dropins directory [message #662635 is a reply to message #662513] |
Thu, 31 March 2011 11:18 |
|
On 03/30/2011 05:25 PM, Kevin Allen wrote:
> He CAN see another classpath container we put in the /dropins, so I
> assume it's something with my plugin that's interacting with something
> in his system. But I'm at a loss - I get no problems from anyone else's
> installation, and absolutely no feedback from his system. It's like it
> just doesn't recognize that it's there.
Yes, dropins is an all optional install, silently failing, best effort
folder. It works OK for a small # of additions that don't interfere
with each other. But if they do (as appears to be the case here) there's
no explanation (I believe they were looking at allowing some logging,
but I don't know if that made it into 3.7 yet).
If you want to diagnose the problem, create a p2 repo with the plugin
that doesn't install and try and install it using the director (try on a
copy of a normal dev install, so you can prove it works) on your bosses
install. If it fails, it will spit out mucho information :-)
Creating the p2 repo: File>Export...>Deployable plug-ins and generate
the p2 metadata. Or add the p2 flags to your PDE build if that's what
you are using. Or use the publisher to generate data from some
plugins/features [1].
Then use the director [2] to install the plugin/feature you want. For a
plugin, for example:
bash$ eclipse/eclipse \
-application org.eclipse.equinox.p2.director \
-noSplash \
-repository \
file:///path/to/p2/repo \
-installIU \
org.example.my.plugin.id
[1]
http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/p2_publisher.html
[2]
http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/p2_director.html
--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Platform_Expression_Framework
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/workbench.htm
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
|
|
| | | | |
Re: Plugin not loading from dropins directory [message #662991 is a reply to message #662989] |
Fri, 01 April 2011 19:20 |
|
On 04/01/2011 02:34 PM, Kevin Allen wrote:
> Managed to get the P2 generated, and attempted to install.
> Unfortunately, it hangs during the install with no failure, errors or
> feedback of any kind.
That usually implies SAT4J is busy trying to find a solution to whatever
is in the installation. If it hasn't failed and hasn't succeeded it's
not hung, it's calculating.
Just as an aside, one thing you could still check is to make sure you
uncheck "contact all update sites" ... it's not relevant for what you
are doing (and that will eliminate any IO component). Also make sure
you don't also have a version of that plugin in your install dropins folder.
The dropins algorithm is to install all of dropins as optional. It then
tries to find the best solution. Then it tries 1000 more times to find
a better solution. If it can find a better solution, it resets the
counter and tries 1000 more times. The algorithm provides stability
and predictability not tied to the computers hardware ... but if you
have a large number of plugins in dropins (I've heard of installs with
thousands :-) a re-evaluation can take >10 minutes.
But yes, I can understand that's all the time you have to look at it and
it's time to move on :-)
Later,
PW
--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Platform_Expression_Framework
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/workbench.htm
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
|
|
| |
Goto Forum:
Current Time: Wed Apr 17 22:17:14 GMT 2024
Powered by FUDForum. Page generated in 0.02117 seconds
|