| Can't get 3.4 to pick-up newly added plug-ins [message #330018] |
Sun, 13 July 2008 10:59  |
Eclipse User |
|
|
|
Originally posted by: jonatan.hager.mailto.no
Hello all,
I have been using Eclipse for some years now and I just upgraded to 3.4
But I have found something that really confuses me. I understand that this
has something to do with the new P2 upgrade mechanism, but I still have to
ask.
I added some new plug-ins that I simply dropped into the plugin directory.
But Eclipse does not install them (no errors in the logfile).
I always start with -clean and I tryed to delete all the contents in the
configuration directory (except config.ini), but after that Eclipse did not
even start.
So can anyone tell me what I have done wrong? Or even better what is the
correct way to install plug-ins that does not have a update site.
BR
J
|
|
|
|
| Re: Can't get 3.4 to pick-up newly added plug-ins [message #330051 is a reply to message #330020] |
Mon, 14 July 2008 08:57  |
 Dani Megert
Messages: 3802
Registered: July 2009 |
Senior Member |
|
|
Ed Merks wrote:
> Jonatan,
>
> Comments below.
>
> Jonatan H wrote:
>> Hello all,
>>
>> I have been using Eclipse for some years now and I just upgraded to 3.4
>> But I have found something that really confuses me. I understand that
>> this has something to do with the new P2 upgrade mechanism, but I
>> still have to ask.
>> I added some new plug-ins that I simply dropped into the plugin
>> directory.
> It should still recognized when pluginis get added there. It's better
> with 3.4 to put them in the dropins folder.
>> But Eclipse does not install them (no errors in the logfile).
>>
> Using -debug can be quite helpful because it prints much more
> detailed messages about the efforts to resolve the plugins.
>> I always start with -clean and I tryed to delete all the contents in
>> the configuration directory (except config.ini), but after that
>> Eclipse did not even start.
>>
> Yes, I ran into a weird problem where I changed the version of a
> plugin from 2.4.0 to 2.4.1 and it caused the plugins to fail to
> resolve for mysterious reasons and my efforts to clear the
> configuration made a mess; eclipse would start, but Java projects
> weren't recognized as Java projects anymore. I'm not sure what the
> proper way to force a clean revisiting of all the dependencies. I've
> heard someone say -clean does nothing for p2, but that might just be
> an ugly rumor.
>> So can anyone tell me what I have done wrong? Or even better what is
>> the correct way to install plug-ins that does not have a update site.
>>
> It really should work putting it into the plugins folder, but using
> the dropins folder is better.
Nope, this no longer works with p2 as the 'plugins' folder is now
locked. You have to use the 'dropins' folder.
Dani
> The -debug flag is helpful for getting extra details that might be
> useful.
>> BR
>>
>> J
>>
>>
>>
>>
>>
>>
>>
|
|
|
| Re: Can't get 3.4 to pick-up newly added plug-ins [message #330066 is a reply to message #330051] |
Mon, 14 July 2008 10:41 |
Ed Merks
Messages: 33179
Registered: July 2009 |
Senior Member |
|
|
Dani,
I unzip my vi plugins into the plugins folder and they still work. I'm
pretty sure that Pascal and company changed p2 to support the old
plugins way of doing things as well, although that's not a best practice
anymore for sure.
Daniel Megert wrote:
> Ed Merks wrote:
>> Jonatan,
>>
>> Comments below.
>>
>> Jonatan H wrote:
>>> Hello all,
>>>
>>> I have been using Eclipse for some years now and I just upgraded to 3.4
>>> But I have found something that really confuses me. I understand
>>> that this has something to do with the new P2 upgrade mechanism, but
>>> I still have to ask.
>>> I added some new plug-ins that I simply dropped into the plugin
>>> directory.
>> It should still recognized when pluginis get added there. It's
>> better with 3.4 to put them in the dropins folder.
>>> But Eclipse does not install them (no errors in the logfile).
>>>
>> Using -debug can be quite helpful because it prints much more
>> detailed messages about the efforts to resolve the plugins.
>>> I always start with -clean and I tryed to delete all the contents in
>>> the configuration directory (except config.ini), but after that
>>> Eclipse did not even start.
>>>
>> Yes, I ran into a weird problem where I changed the version of a
>> plugin from 2.4.0 to 2.4.1 and it caused the plugins to fail to
>> resolve for mysterious reasons and my efforts to clear the
>> configuration made a mess; eclipse would start, but Java projects
>> weren't recognized as Java projects anymore. I'm not sure what the
>> proper way to force a clean revisiting of all the dependencies. I've
>> heard someone say -clean does nothing for p2, but that might just be
>> an ugly rumor.
>>> So can anyone tell me what I have done wrong? Or even better what is
>>> the correct way to install plug-ins that does not have a update site.
>>>
>> It really should work putting it into the plugins folder, but using
>> the dropins folder is better.
> Nope, this no longer works with p2 as the 'plugins' folder is now
> locked. You have to use the 'dropins' folder.
>
> Dani
>> The -debug flag is helpful for getting extra details that might be
>> useful.
>>> BR
>>>
>>> J
>>>
>>>
>>>
>>>
>>>
>>>
>>>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Can't get 3.4 to pick-up newly added plug-ins [message #330074 is a reply to message #330066] |
Mon, 14 July 2008 14:10 |
Jakub Jurkiewicz
Messages: 38
Registered: July 2009 |
Member |
|
|
Ed Merks pisze:
> Dani,
>
> I unzip my vi plugins into the plugins folder and they still work. I'm
> pretty sure that Pascal and company changed p2 to support the old
> plugins way of doing things as well, although that's not a best practice
> anymore for sure.
>
>
> Daniel Megert wrote:
>> Ed Merks wrote:
>>> Jonatan,
>>>
>>> Comments below.
>>>
>>> Jonatan H wrote:
>>>> Hello all,
>>>>
>>>> I have been using Eclipse for some years now and I just upgraded to 3.4
>>>> But I have found something that really confuses me. I understand
>>>> that this has something to do with the new P2 upgrade mechanism, but
>>>> I still have to ask.
>>>> I added some new plug-ins that I simply dropped into the plugin
>>>> directory.
>>> It should still recognized when pluginis get added there. It's
>>> better with 3.4 to put them in the dropins folder.
>>>> But Eclipse does not install them (no errors in the logfile).
>>>>
>>> Using -debug can be quite helpful because it prints much more
>>> detailed messages about the efforts to resolve the plugins.
>>>> I always start with -clean and I tryed to delete all the contents in
>>>> the configuration directory (except config.ini), but after that
>>>> Eclipse did not even start.
>>>>
>>> Yes, I ran into a weird problem where I changed the version of a
>>> plugin from 2.4.0 to 2.4.1 and it caused the plugins to fail to
>>> resolve for mysterious reasons and my efforts to clear the
>>> configuration made a mess; eclipse would start, but Java projects
>>> weren't recognized as Java projects anymore. I'm not sure what the
>>> proper way to force a clean revisiting of all the dependencies. I've
>>> heard someone say -clean does nothing for p2, but that might just be
>>> an ugly rumor.
>>>> So can anyone tell me what I have done wrong? Or even better what is
>>>> the correct way to install plug-ins that does not have a update site.
>>>>
>>> It really should work putting it into the plugins folder, but using
>>> the dropins folder is better.
>> Nope, this no longer works with p2 as the 'plugins' folder is now
>> locked. You have to use the 'dropins' folder.
>>
>> Dani
>>> The -debug flag is helpful for getting extra details that might be
>>> useful.
>>>> BR
>>>>
>>>> J
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
Ed is right. As stated here:
http://wiki.eclipse.org/Equinox_p2_Getting_Started
"Although p2 will detect plug-ins added directly to the plugins folder
(with an associated startup performance cost), alterations to plug-ins
installed by p2 in this directory is not supported."
--
kind regards,
Jakub
http://eclipser-blog.blogspot.com/
http://eclipse-po-polsku.blogspot.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03288 seconds
] 
Search
Help
Register
Login
Home
