Home » Eclipse Projects » Equinox » Dropins on Galileo not working?
Dropins on Galileo not working? [message #134770] |
Wed, 08 July 2009 07:08  |
Eclipse User |
|
|
|
Originally posted by: david.roamware.co.uk
Hi,
My experience with the dropins directory has never been good. I am
trying to deploy the latest EMF Teneo update in the dropins directory.
It uses the dropins/eclipse/plugins and dropins/eclipse/features layout.
It simply does not deploy it. Running with eclipse -clean - debug gives
me nothing about why it does not deploy. In desperation I put the
plugins directly in eclipse/plugins and similarly for features and start
with ecliuspe -clean -debug. The newer version of the plugin does not
appear as a plugin, so cannot include it as a dependency on my project.
So I am stopped dead,
Ideas?
David
|
|
| |
Re: Dropins on Galileo not working? [message #134827 is a reply to message #134814] |
Wed, 08 July 2009 09:24   |
Eclipse User |
|
|
|
Originally posted by: david.roamware.co.uk
Hi,
"Install new software" tells me that current version 1.1.0 is already
installed and nothing to do. I am trying to update to V1.1.1 as it
solves a problem with 1.1.0
At one point I tried manually deleting the old version of the jars and
features and leaving the newer version there, 1.1.1. Since that
operation Eclipse thinks it has no Teneo plugin. When I added back the
original jars and feature (1.1.0) it still thinks there is no Teneo
plugin there, when looking at "About Eclipse Features" for modelling.
Where does p2 store information about what plugins are installed and how
do you refresh it?
I also ran with "eclipse -debug -clean -console", the "Interactive
console" does not take any input at the prompt?
David
Paul Webster wrote:
> David Wynter wrote:
>> Hi,
>>
>> My experience with the dropins directory has never been good. I am
>> trying to deploy the latest EMF Teneo update in the dropins directory.
>> It uses the dropins/eclipse/plugins and dropins/eclipse/features
>> layout. It simply does not deploy it. Running with eclipse -clean -
>> debug gives me nothing about why it does not deploy. In desperation I
>> put the plugins directly in eclipse/plugins and similarly for features
>> and start with ecliuspe -clean -debug. The newer version of the plugin
>> does not appear as a plugin, so cannot include it as a dependency on
>> my project. So I am stopped dead,
>
> There doesn't seem to be anything out of the ordinary in what you are
> doing. Are there any errors in your error log with the dropins config
> you are using? If you start eclipse with -console to get the OSGi
> console, can you see the new plugins using 'ss'?
>
> But if you're stuck, why not use Install New Software to install it
> instead of dropins? Installing the galileo EMF Teneo into Galileo
> eclipse should definitely be supported :-)
>
> PW
>
|
|
| |
Re: Dropins on Galileo not working? [message #134861 is a reply to message #134827] |
Wed, 08 July 2009 10:16   |
Eclipse User |
|
|
|
Originally posted by: david.roamware.co.uk
This gets worse and worse. I used "Installation Details" to uninstall
Teneo for EclipseLink and for Hibernate. It fails to delete these fully
saying there are some components that are relied on by other plugins (
what these are I cannot think, nor does it tell me).
So now they are not listed in "Installed Software", but all of the jars
appear to still be in plugins directory....
When I go to reinstall the original V1.1.0 of Teneo for Hibernate, it
tells me it is already installed... What a pile of crap....
It looks like my only way out of this is a fresh install of Galileo in a
new location. I could not find information on where Eclipse stores
information about which plugins are installed. This needs to be directly
accessible until p2 works correctly.
Thx.
David
David Wynter wrote:
> Hi,
>
> "Install new software" tells me that current version 1.1.0 is already
> installed and nothing to do. I am trying to update to V1.1.1 as it
> solves a problem with 1.1.0
>
> At one point I tried manually deleting the old version of the jars and
> features and leaving the newer version there, 1.1.1. Since that
> operation Eclipse thinks it has no Teneo plugin. When I added back the
> original jars and feature (1.1.0) it still thinks there is no Teneo
> plugin there, when looking at "About Eclipse Features" for modelling.
> Where does p2 store information about what plugins are installed and how
> do you refresh it?
>
> I also ran with "eclipse -debug -clean -console", the "Interactive
> console" does not take any input at the prompt?
>
> David
>
>
>
> Paul Webster wrote:
>> David Wynter wrote:
>>> Hi,
>>>
>>> My experience with the dropins directory has never been good. I am
>>> trying to deploy the latest EMF Teneo update in the dropins
>>> directory. It uses the dropins/eclipse/plugins and
>>> dropins/eclipse/features layout. It simply does not deploy it.
>>> Running with eclipse -clean - debug gives me nothing about why it
>>> does not deploy. In desperation I put the plugins directly in
>>> eclipse/plugins and similarly for features and start with ecliuspe
>>> -clean -debug. The newer version of the plugin does not appear as a
>>> plugin, so cannot include it as a dependency on my project. So I am
>>> stopped dead,
>>
>> There doesn't seem to be anything out of the ordinary in what you are
>> doing. Are there any errors in your error log with the dropins config
>> you are using? If you start eclipse with -console to get the OSGi
>> console, can you see the new plugins using 'ss'?
>>
>> But if you're stuck, why not use Install New Software to install it
>> instead of dropins? Installing the galileo EMF Teneo into Galileo
>> eclipse should definitely be supported :-)
>>
>> PW
>>
|
|
| | |
Re: Dropins on Galileo not working? [message #134906 is a reply to message #134827] |
Wed, 08 July 2009 11:18   |
Eclipse User |
|
|
|
"David Wynter" <david@roamware.co.uk> wrote in message
news:4A549E15.3000204@roamware.co.uk...
> Hi,
>
> "Install new software" tells me that current version 1.1.0 is already
> installed and nothing to do. I am trying to update to V1.1.1 as it solves
> a problem with 1.1.0
>
How was Teneo 1.1.0 installed? From the update site? as part of a
pre-existing product?
If Teneo was installed using the p2 UI you will need to update it with the
p2 UI as the platform will view it as part of the "managed" install.
One way to think of this is that eclipse consists of "managed" pieces
installed via the p2 UI (or p2 director) application and "unmanaged" pieces
installed by placing arbitrary bundles in dropins. If there is a dependency
discrepency, the managed pieces always take priority so this is why updating
an existing "managed" component by using dropins generally won' work.
> At one point I tried manually deleting the old version of the jars and
> features and leaving the newer version there, 1.1.1. Since that operation
> Eclipse thinks it has no Teneo plugin. When I added back the original jars
> and feature (1.1.0) it still thinks there is no Teneo plugin there, when
> looking at "About Eclipse Features" for modelling. Where does p2 store
> information about what plugins are installed and how do you refresh it?
>
p2 stores the information on what's installed in the profileRegistry.
(p2/org.eclipse.equinox.p2.engine/profileRegistry/{profileNa me}.profile).
This folder holds the history of what's been installed so the current
profile contents are contained in the latest profile file. Manually deleting
plugins from the bundle pool (e.g. eclipse/plugins and eclipse/features) as
you've found out is fraught with disaster. If you arbitrarily remove the
bundles for a product you can easily end up in a situation where the profile
registry believes a feature is installed although many of the bundles are no
longer present.
The "unmanaged" portion of the install e.g. dropins is self-healing as it is
scanned each time at startup however the "managed" chunk are not, so if it
becomes corrupt or damaged in some way you're in trouble. We have a GSOC
student looking at how we might handle recovery of the "managed" install
however that work is not complete or in the main trunk right now. This tool
is like a reset button and would restore the base platform and what ever
top-level pieces it can validate as complete and is really a last resort to
bring a broken install back to life. I don't really think it's applicable to
what you're doing but am just mentioning it as work in progress on improving
our recovery story.
> I also ran with "eclipse -debug -clean -console", the "Interactive
> console" does not take any input at the prompt?
>
> David
>
>
>
> Paul Webster wrote:
>> David Wynter wrote:
>>> Hi,
>>>
>>> My experience with the dropins directory has never been good. I am
>>> trying to deploy the latest EMF Teneo update in the dropins directory.
>>> It uses the dropins/eclipse/plugins and dropins/eclipse/features layout.
>>> It simply does not deploy it. Running with eclipse -clean - debug gives
>>> me nothing about why it does not deploy. In desperation I put the
>>> plugins directly in eclipse/plugins and similarly for features and start
>>> with ecliuspe -clean -debug. The newer version of the plugin does not
>>> appear as a plugin, so cannot include it as a dependency on my project.
>>> So I am stopped dead,
>>
>> There doesn't seem to be anything out of the ordinary in what you are
>> doing. Are there any errors in your error log with the dropins config
>> you are using? If you start eclipse with -console to get the OSGi
>> console, can you see the new plugins using 'ss'?
>>
>> But if you're stuck, why not use Install New Software to install it
>> instead of dropins? Installing the galileo EMF Teneo into Galileo
>> eclipse should definitely be supported :-)
>>
>> PW
>>
|
|
|
Re: Dropins on Galileo not working? [message #134932 is a reply to message #134906] |
Wed, 08 July 2009 11:36   |
Eclipse User |
|
|
|
Originally posted by: david.roamware.co.uk
Hi,
That explains everything except the weird thing with the Back and Next
keys changing the detected dependencies preventing a full uninstall. It
even explains that when I did eventually uninstall the std Teneo plugin
it no longer appears installed, but Update tells you it is installed.
What a mess.
So, when Martin releases a new version of his managed Teneo plugin, how
do we install it? It is not on an Update site anywhere...
Looks like I am going to have to reinstal Galileo.
David
Simon Kaegi wrote:
> "David Wynter" <david@roamware.co.uk> wrote in message
> news:4A549E15.3000204@roamware.co.uk...
>> Hi,
>>
>> "Install new software" tells me that current version 1.1.0 is already
>> installed and nothing to do. I am trying to update to V1.1.1 as it solves
>> a problem with 1.1.0
>>
> How was Teneo 1.1.0 installed? From the update site? as part of a
> pre-existing product?
> If Teneo was installed using the p2 UI you will need to update it with the
> p2 UI as the platform will view it as part of the "managed" install.
>
> One way to think of this is that eclipse consists of "managed" pieces
> installed via the p2 UI (or p2 director) application and "unmanaged" pieces
> installed by placing arbitrary bundles in dropins. If there is a dependency
> discrepency, the managed pieces always take priority so this is why updating
> an existing "managed" component by using dropins generally won' work.
>
>> At one point I tried manually deleting the old version of the jars and
>> features and leaving the newer version there, 1.1.1. Since that operation
>> Eclipse thinks it has no Teneo plugin. When I added back the original jars
>> and feature (1.1.0) it still thinks there is no Teneo plugin there, when
>> looking at "About Eclipse Features" for modelling. Where does p2 store
>> information about what plugins are installed and how do you refresh it?
>>
>
> p2 stores the information on what's installed in the profileRegistry.
> (p2/org.eclipse.equinox.p2.engine/profileRegistry/{profileNa me}.profile).
> This folder holds the history of what's been installed so the current
> profile contents are contained in the latest profile file. Manually deleting
> plugins from the bundle pool (e.g. eclipse/plugins and eclipse/features) as
> you've found out is fraught with disaster. If you arbitrarily remove the
> bundles for a product you can easily end up in a situation where the profile
> registry believes a feature is installed although many of the bundles are no
> longer present.
>
> The "unmanaged" portion of the install e.g. dropins is self-healing as it is
> scanned each time at startup however the "managed" chunk are not, so if it
> becomes corrupt or damaged in some way you're in trouble. We have a GSOC
> student looking at how we might handle recovery of the "managed" install
> however that work is not complete or in the main trunk right now. This tool
> is like a reset button and would restore the base platform and what ever
> top-level pieces it can validate as complete and is really a last resort to
> bring a broken install back to life. I don't really think it's applicable to
> what you're doing but am just mentioning it as work in progress on improving
> our recovery story.
>
>> I also ran with "eclipse -debug -clean -console", the "Interactive
>> console" does not take any input at the prompt?
>>
>> David
>>
>>
>>
>> Paul Webster wrote:
>>> David Wynter wrote:
>>>> Hi,
>>>>
>>>> My experience with the dropins directory has never been good. I am
>>>> trying to deploy the latest EMF Teneo update in the dropins directory.
>>>> It uses the dropins/eclipse/plugins and dropins/eclipse/features layout.
>>>> It simply does not deploy it. Running with eclipse -clean - debug gives
>>>> me nothing about why it does not deploy. In desperation I put the
>>>> plugins directly in eclipse/plugins and similarly for features and start
>>>> with ecliuspe -clean -debug. The newer version of the plugin does not
>>>> appear as a plugin, so cannot include it as a dependency on my project.
>>>> So I am stopped dead,
>>> There doesn't seem to be anything out of the ordinary in what you are
>>> doing. Are there any errors in your error log with the dropins config
>>> you are using? If you start eclipse with -console to get the OSGi
>>> console, can you see the new plugins using 'ss'?
>>>
>>> But if you're stuck, why not use Install New Software to install it
>>> instead of dropins? Installing the galileo EMF Teneo into Galileo
>>> eclipse should definitely be supported :-)
>>>
>>> PW
>>>
>
>
|
|
|
Re: Dropins on Galileo not working? [message #134946 is a reply to message #134932] |
Wed, 08 July 2009 11:49   |
Eclipse User |
|
|
|
"David Wynter" <david@roamware.co.uk> wrote in message
news:4A54BCFC.6000201@roamware.co.uk...
> Hi,
>
> That explains everything except the weird thing with the Back and Next
> keys changing the detected dependencies preventing a full uninstall. It
> even explains that when I did eventually uninstall the std Teneo plugin it
> no longer appears installed, but Update tells you it is installed. What a
> mess.
Agrred. The weird back and next stuff is bizarre. I will try that out and
see if I can duplicate it or if you manage to refine your technique that
would be good.
That said the UI is not really in control and director/planner should
prevent anything illegal from a dependency perspective from occuring.
>
> So, when Martin releases a new version of his managed Teneo plugin, how do
> we install it? It is not on an Update site anywhere...
>
That's a pity as I really wish people would take the time and use the
eclipse web site to distribute this stuff. It looks like you can download
the zipped update site. You should be able to unzip it and add it as Local
repository and then install from it.
> Looks like I am going to have to reinstal Galileo.
>
> David
>
> Simon Kaegi wrote:
>> "David Wynter" <david@roamware.co.uk> wrote in message
>> news:4A549E15.3000204@roamware.co.uk...
>>> Hi,
>>>
>>> "Install new software" tells me that current version 1.1.0 is already
>>> installed and nothing to do. I am trying to update to V1.1.1 as it
>>> solves a problem with 1.1.0
>>>
>> How was Teneo 1.1.0 installed? From the update site? as part of a
>> pre-existing product?
>> If Teneo was installed using the p2 UI you will need to update it with
>> the p2 UI as the platform will view it as part of the "managed" install.
>>
>> One way to think of this is that eclipse consists of "managed" pieces
>> installed via the p2 UI (or p2 director) application and "unmanaged"
>> pieces installed by placing arbitrary bundles in dropins. If there is a
>> dependency discrepency, the managed pieces always take priority so this
>> is why updating an existing "managed" component by using dropins
>> generally won' work.
>>
>>> At one point I tried manually deleting the old version of the jars and
>>> features and leaving the newer version there, 1.1.1. Since that
>>> operation Eclipse thinks it has no Teneo plugin. When I added back the
>>> original jars and feature (1.1.0) it still thinks there is no Teneo
>>> plugin there, when looking at "About Eclipse Features" for modelling.
>>> Where does p2 store information about what plugins are installed and how
>>> do you refresh it?
>>>
>>
>> p2 stores the information on what's installed in the profileRegistry.
>> (p2/org.eclipse.equinox.p2.engine/profileRegistry/{profileNa me}.profile).
>> This folder holds the history of what's been installed so the current
>> profile contents are contained in the latest profile file. Manually
>> deleting plugins from the bundle pool (e.g. eclipse/plugins and
>> eclipse/features) as you've found out is fraught with disaster. If you
>> arbitrarily remove the bundles for a product you can easily end up in a
>> situation where the profile registry believes a feature is installed
>> although many of the bundles are no longer present.
>>
>> The "unmanaged" portion of the install e.g. dropins is self-healing as it
>> is scanned each time at startup however the "managed" chunk are not, so
>> if it becomes corrupt or damaged in some way you're in trouble. We have a
>> GSOC student looking at how we might handle recovery of the "managed"
>> install however that work is not complete or in the main trunk right now.
>> This tool is like a reset button and would restore the base platform and
>> what ever top-level pieces it can validate as complete and is really a
>> last resort to bring a broken install back to life. I don't really think
>> it's applicable to what you're doing but am just mentioning it as work in
>> progress on improving our recovery story.
>>
>>> I also ran with "eclipse -debug -clean -console", the "Interactive
>>> console" does not take any input at the prompt?
>>>
>>> David
>>>
>>>
>>>
>>> Paul Webster wrote:
>>>> David Wynter wrote:
>>>>> Hi,
>>>>>
>>>>> My experience with the dropins directory has never been good. I am
>>>>> trying to deploy the latest EMF Teneo update in the dropins directory.
>>>>> It uses the dropins/eclipse/plugins and dropins/eclipse/features
>>>>> layout. It simply does not deploy it. Running with eclipse -clean -
>>>>> debug gives me nothing about why it does not deploy. In desperation I
>>>>> put the plugins directly in eclipse/plugins and similarly for features
>>>>> and start with ecliuspe -clean -debug. The newer version of the plugin
>>>>> does not appear as a plugin, so cannot include it as a dependency on
>>>>> my project. So I am stopped dead,
>>>> There doesn't seem to be anything out of the ordinary in what you are
>>>> doing. Are there any errors in your error log with the dropins config
>>>> you are using? If you start eclipse with -console to get the OSGi
>>>> console, can you see the new plugins using 'ss'?
>>>>
>>>> But if you're stuck, why not use Install New Software to install it
>>>> instead of dropins? Installing the galileo EMF Teneo into Galileo
>>>> eclipse should definitely be supported :-)
>>>>
>>>> PW
>>>>
>>
|
|
|
Re: Dropins on Galileo not working? [message #134960 is a reply to message #134906] |
Wed, 08 July 2009 11:53   |
Eclipse User |
|
|
|
Originally posted by: david.roamware.co.uk
Hi,
Another question for you. Given I am stuck with a managed instal of
Teneo and the only problem I need to solve is one of visibility of a
package, can I - Unpack the
org.eclipse.emf.teneo.hibernate_1.1.0.v200906180911.jar into a directory
of the same name and the extras jar currently inside it fully expanding
all of the directories and then removing the original jar file without
breaking anything in the managed package?
David
Simon Kaegi wrote:
> "David Wynter" <david@roamware.co.uk> wrote in message
> news:4A549E15.3000204@roamware.co.uk...
>> Hi,
>>
>> "Install new software" tells me that current version 1.1.0 is already
>> installed and nothing to do. I am trying to update to V1.1.1 as it solves
>> a problem with 1.1.0
>>
> How was Teneo 1.1.0 installed? From the update site? as part of a
> pre-existing product?
> If Teneo was installed using the p2 UI you will need to update it with the
> p2 UI as the platform will view it as part of the "managed" install.
>
> One way to think of this is that eclipse consists of "managed" pieces
> installed via the p2 UI (or p2 director) application and "unmanaged" pieces
> installed by placing arbitrary bundles in dropins. If there is a dependency
> discrepency, the managed pieces always take priority so this is why updating
> an existing "managed" component by using dropins generally won' work.
>
>> At one point I tried manually deleting the old version of the jars and
>> features and leaving the newer version there, 1.1.1. Since that operation
>> Eclipse thinks it has no Teneo plugin. When I added back the original jars
>> and feature (1.1.0) it still thinks there is no Teneo plugin there, when
>> looking at "About Eclipse Features" for modelling. Where does p2 store
>> information about what plugins are installed and how do you refresh it?
>>
>
> p2 stores the information on what's installed in the profileRegistry.
> (p2/org.eclipse.equinox.p2.engine/profileRegistry/{profileNa me}.profile).
> This folder holds the history of what's been installed so the current
> profile contents are contained in the latest profile file. Manually deleting
> plugins from the bundle pool (e.g. eclipse/plugins and eclipse/features) as
> you've found out is fraught with disaster. If you arbitrarily remove the
> bundles for a product you can easily end up in a situation where the profile
> registry believes a feature is installed although many of the bundles are no
> longer present.
>
> The "unmanaged" portion of the install e.g. dropins is self-healing as it is
> scanned each time at startup however the "managed" chunk are not, so if it
> becomes corrupt or damaged in some way you're in trouble. We have a GSOC
> student looking at how we might handle recovery of the "managed" install
> however that work is not complete or in the main trunk right now. This tool
> is like a reset button and would restore the base platform and what ever
> top-level pieces it can validate as complete and is really a last resort to
> bring a broken install back to life. I don't really think it's applicable to
> what you're doing but am just mentioning it as work in progress on improving
> our recovery story.
>
>> I also ran with "eclipse -debug -clean -console", the "Interactive
>> console" does not take any input at the prompt?
>>
>> David
>>
>>
>>
>> Paul Webster wrote:
>>> David Wynter wrote:
>>>> Hi,
>>>>
>>>> My experience with the dropins directory has never been good. I am
>>>> trying to deploy the latest EMF Teneo update in the dropins directory.
>>>> It uses the dropins/eclipse/plugins and dropins/eclipse/features layout.
>>>> It simply does not deploy it. Running with eclipse -clean - debug gives
>>>> me nothing about why it does not deploy. In desperation I put the
>>>> plugins directly in eclipse/plugins and similarly for features and start
>>>> with ecliuspe -clean -debug. The newer version of the plugin does not
>>>> appear as a plugin, so cannot include it as a dependency on my project.
>>>> So I am stopped dead,
>>> There doesn't seem to be anything out of the ordinary in what you are
>>> doing. Are there any errors in your error log with the dropins config
>>> you are using? If you start eclipse with -console to get the OSGi
>>> console, can you see the new plugins using 'ss'?
>>>
>>> But if you're stuck, why not use Install New Software to install it
>>> instead of dropins? Installing the galileo EMF Teneo into Galileo
>>> eclipse should definitely be supported :-)
>>>
>>> PW
>>>
>
>
|
|
|
Re: Dropins on Galileo not working? [message #134972 is a reply to message #134946] |
Wed, 08 July 2009 12:03   |
Eclipse User |
|
|
|
Originally posted by: david.roamware.co.uk
Hi,
Actually it is V1.1.0 that you can download as a Update site, that is
the version released with Galileo. To be fair to Martin this release
that fixes a problem was only made a few hours ago. So the obvious next
question is - can you create a Update site download locally given and
earlier Update site and a set of update jar files?
Thx.
David
Simon Kaegi wrote:
> "David Wynter" <david@roamware.co.uk> wrote in message
> news:4A54BCFC.6000201@roamware.co.uk...
>> Hi,
>>
>> That explains everything except the weird thing with the Back and Next
>> keys changing the detected dependencies preventing a full uninstall. It
>> even explains that when I did eventually uninstall the std Teneo plugin it
>> no longer appears installed, but Update tells you it is installed. What a
>> mess.
>
> Agrred. The weird back and next stuff is bizarre. I will try that out and
> see if I can duplicate it or if you manage to refine your technique that
> would be good.
> That said the UI is not really in control and director/planner should
> prevent anything illegal from a dependency perspective from occuring.
>
>> So, when Martin releases a new version of his managed Teneo plugin, how do
>> we install it? It is not on an Update site anywhere...
>>
> That's a pity as I really wish people would take the time and use the
> eclipse web site to distribute this stuff. It looks like you can download
> the zipped update site. You should be able to unzip it and add it as Local
> repository and then install from it.
>
>> Looks like I am going to have to reinstal Galileo.
>>
>> David
>>
>> Simon Kaegi wrote:
>>> "David Wynter" <david@roamware.co.uk> wrote in message
>>> news:4A549E15.3000204@roamware.co.uk...
>>>> Hi,
>>>>
>>>> "Install new software" tells me that current version 1.1.0 is already
>>>> installed and nothing to do. I am trying to update to V1.1.1 as it
>>>> solves a problem with 1.1.0
>>>>
>>> How was Teneo 1.1.0 installed? From the update site? as part of a
>>> pre-existing product?
>>> If Teneo was installed using the p2 UI you will need to update it with
>>> the p2 UI as the platform will view it as part of the "managed" install.
>>>
>>> One way to think of this is that eclipse consists of "managed" pieces
>>> installed via the p2 UI (or p2 director) application and "unmanaged"
>>> pieces installed by placing arbitrary bundles in dropins. If there is a
>>> dependency discrepency, the managed pieces always take priority so this
>>> is why updating an existing "managed" component by using dropins
>>> generally won' work.
>>>
>>>> At one point I tried manually deleting the old version of the jars and
>>>> features and leaving the newer version there, 1.1.1. Since that
>>>> operation Eclipse thinks it has no Teneo plugin. When I added back the
>>>> original jars and feature (1.1.0) it still thinks there is no Teneo
>>>> plugin there, when looking at "About Eclipse Features" for modelling.
>>>> Where does p2 store information about what plugins are installed and how
>>>> do you refresh it?
>>>>
>>> p2 stores the information on what's installed in the profileRegistry.
>>> (p2/org.eclipse.equinox.p2.engine/profileRegistry/{profileNa me}.profile).
>>> This folder holds the history of what's been installed so the current
>>> profile contents are contained in the latest profile file. Manually
>>> deleting plugins from the bundle pool (e.g. eclipse/plugins and
>>> eclipse/features) as you've found out is fraught with disaster. If you
>>> arbitrarily remove the bundles for a product you can easily end up in a
>>> situation where the profile registry believes a feature is installed
>>> although many of the bundles are no longer present.
>>>
>>> The "unmanaged" portion of the install e.g. dropins is self-healing as it
>>> is scanned each time at startup however the "managed" chunk are not, so
>>> if it becomes corrupt or damaged in some way you're in trouble. We have a
>>> GSOC student looking at how we might handle recovery of the "managed"
>>> install however that work is not complete or in the main trunk right now.
>>> This tool is like a reset button and would restore the base platform and
>>> what ever top-level pieces it can validate as complete and is really a
>>> last resort to bring a broken install back to life. I don't really think
>>> it's applicable to what you're doing but am just mentioning it as work in
>>> progress on improving our recovery story.
>>>
>>>> I also ran with "eclipse -debug -clean -console", the "Interactive
>>>> console" does not take any input at the prompt?
>>>>
>>>> David
>>>>
>>>>
>>>>
>>>> Paul Webster wrote:
>>>>> David Wynter wrote:
>>>>>> Hi,
>>>>>>
>>>>>> My experience with the dropins directory has never been good. I am
>>>>>> trying to deploy the latest EMF Teneo update in the dropins directory.
>>>>>> It uses the dropins/eclipse/plugins and dropins/eclipse/features
>>>>>> layout. It simply does not deploy it. Running with eclipse -clean -
>>>>>> debug gives me nothing about why it does not deploy. In desperation I
>>>>>> put the plugins directly in eclipse/plugins and similarly for features
>>>>>> and start with ecliuspe -clean -debug. The newer version of the plugin
>>>>>> does not appear as a plugin, so cannot include it as a dependency on
>>>>>> my project. So I am stopped dead,
>>>>> There doesn't seem to be anything out of the ordinary in what you are
>>>>> doing. Are there any errors in your error log with the dropins config
>>>>> you are using? If you start eclipse with -console to get the OSGi
>>>>> console, can you see the new plugins using 'ss'?
>>>>>
>>>>> But if you're stuck, why not use Install New Software to install it
>>>>> instead of dropins? Installing the galileo EMF Teneo into Galileo
>>>>> eclipse should definitely be supported :-)
>>>>>
>>>>> PW
>>>>>
>
|
|
|
Re: Dropins on Galileo not working? [message #134983 is a reply to message #134972] |
Wed, 08 July 2009 12:09   |
Eclipse User |
|
|
|
Originally posted by: david.roamware.co.uk
In answer to my own question, having now discovered artifacts.xml,
site.xml and content.xml, only with a lot of painstaking effort could
you update an existing Update site to use a set of about 7 new jars.
There may be some signing in there too, in which case probably not possible.
so my other question still stands, can I expand the teneo.hibernate jar
into a directory and delete the original jar without upsetting a managed
set of bundles like teneo?
David
David Wynter wrote:
> Hi,
>
> Actually it is V1.1.0 that you can download as a Update site, that is
> the version released with Galileo. To be fair to Martin this release
> that fixes a problem was only made a few hours ago. So the obvious next
> question is - can you create a Update site download locally given and
> earlier Update site and a set of update jar files?
>
> Thx.
>
> David
>
> Simon Kaegi wrote:
>> "David Wynter" <david@roamware.co.uk> wrote in message
>> news:4A54BCFC.6000201@roamware.co.uk...
>>> Hi,
>>>
>>> That explains everything except the weird thing with the Back and
>>> Next keys changing the detected dependencies preventing a full
>>> uninstall. It even explains that when I did eventually uninstall the
>>> std Teneo plugin it no longer appears installed, but Update tells you
>>> it is installed. What a mess.
>>
>> Agrred. The weird back and next stuff is bizarre. I will try that out
>> and see if I can duplicate it or if you manage to refine your
>> technique that would be good.
>> That said the UI is not really in control and director/planner should
>> prevent anything illegal from a dependency perspective from occuring.
>>
>>> So, when Martin releases a new version of his managed Teneo plugin,
>>> how do we install it? It is not on an Update site anywhere...
>>>
>> That's a pity as I really wish people would take the time and use the
>> eclipse web site to distribute this stuff. It looks like you can
>> download the zipped update site. You should be able to unzip it and
>> add it as Local repository and then install from it.
>>
>>> Looks like I am going to have to reinstal Galileo.
>>>
>>> David
>>>
>>> Simon Kaegi wrote:
>>>> "David Wynter" <david@roamware.co.uk> wrote in message
>>>> news:4A549E15.3000204@roamware.co.uk...
>>>>> Hi,
>>>>>
>>>>> "Install new software" tells me that current version 1.1.0 is
>>>>> already installed and nothing to do. I am trying to update to
>>>>> V1.1.1 as it solves a problem with 1.1.0
>>>>>
>>>> How was Teneo 1.1.0 installed? From the update site? as part of a
>>>> pre-existing product?
>>>> If Teneo was installed using the p2 UI you will need to update it
>>>> with the p2 UI as the platform will view it as part of the "managed"
>>>> install.
>>>>
>>>> One way to think of this is that eclipse consists of "managed"
>>>> pieces installed via the p2 UI (or p2 director) application and
>>>> "unmanaged" pieces installed by placing arbitrary bundles in
>>>> dropins. If there is a dependency discrepency, the managed pieces
>>>> always take priority so this is why updating an existing "managed"
>>>> component by using dropins generally won' work.
>>>>
>>>>> At one point I tried manually deleting the old version of the jars
>>>>> and features and leaving the newer version there, 1.1.1. Since that
>>>>> operation Eclipse thinks it has no Teneo plugin. When I added back
>>>>> the original jars and feature (1.1.0) it still thinks there is no
>>>>> Teneo plugin there, when looking at "About Eclipse Features" for
>>>>> modelling. Where does p2 store information about what plugins are
>>>>> installed and how do you refresh it?
>>>>>
>>>> p2 stores the information on what's installed in the
>>>> profileRegistry.
>>>> (p2/org.eclipse.equinox.p2.engine/profileRegistry/{profileNa me}.profile).
>>>> This folder holds the history of what's been installed so the
>>>> current profile contents are contained in the latest profile file.
>>>> Manually deleting plugins from the bundle pool (e.g. eclipse/plugins
>>>> and eclipse/features) as you've found out is fraught with disaster.
>>>> If you arbitrarily remove the bundles for a product you can easily
>>>> end up in a situation where the profile registry believes a feature
>>>> is installed although many of the bundles are no longer present.
>>>>
>>>> The "unmanaged" portion of the install e.g. dropins is self-healing
>>>> as it is scanned each time at startup however the "managed" chunk
>>>> are not, so if it becomes corrupt or damaged in some way you're in
>>>> trouble. We have a GSOC student looking at how we might handle
>>>> recovery of the "managed" install however that work is not complete
>>>> or in the main trunk right now. This tool is like a reset button and
>>>> would restore the base platform and what ever top-level pieces it
>>>> can validate as complete and is really a last resort to bring a
>>>> broken install back to life. I don't really think it's applicable to
>>>> what you're doing but am just mentioning it as work in progress on
>>>> improving our recovery story.
>>>>
>>>>> I also ran with "eclipse -debug -clean -console", the "Interactive
>>>>> console" does not take any input at the prompt?
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>>
>>>>> Paul Webster wrote:
>>>>>> David Wynter wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> My experience with the dropins directory has never been good. I
>>>>>>> am trying to deploy the latest EMF Teneo update in the dropins
>>>>>>> directory. It uses the dropins/eclipse/plugins and
>>>>>>> dropins/eclipse/features layout. It simply does not deploy it.
>>>>>>> Running with eclipse -clean - debug gives me nothing about why it
>>>>>>> does not deploy. In desperation I put the plugins directly in
>>>>>>> eclipse/plugins and similarly for features and start with
>>>>>>> ecliuspe -clean -debug. The newer version of the plugin does not
>>>>>>> appear as a plugin, so cannot include it as a dependency on my
>>>>>>> project. So I am stopped dead,
>>>>>> There doesn't seem to be anything out of the ordinary in what you
>>>>>> are doing. Are there any errors in your error log with the
>>>>>> dropins config you are using? If you start eclipse with -console
>>>>>> to get the OSGi console, can you see the new plugins using 'ss'?
>>>>>>
>>>>>> But if you're stuck, why not use Install New Software to install
>>>>>> it instead of dropins? Installing the galileo EMF Teneo into
>>>>>> Galileo eclipse should definitely be supported :-)
>>>>>>
>>>>>> PW
>>>>>>
>>
|
|
|
Re: Dropins on Galileo not working? [message #134996 is a reply to message #134983] |
Wed, 08 July 2009 12:16   |
Eclipse User |
|
|
|
That should be ok so long as teneo.hibernate.jar is an internal detail of
the bundle.
"David Wynter" <david@roamware.co.uk> wrote in message
news:4A54C4D1.8080503@roamware.co.uk...
> In answer to my own question, having now discovered artifacts.xml,
> site.xml and content.xml, only with a lot of painstaking effort could you
> update an existing Update site to use a set of about 7 new jars. There may
> be some signing in there too, in which case probably not possible.
>
> so my other question still stands, can I expand the teneo.hibernate jar
> into a directory and delete the original jar without upsetting a managed
> set of bundles like teneo?
>
> David
>
> David Wynter wrote:
>> Hi,
>>
>> Actually it is V1.1.0 that you can download as a Update site, that is the
>> version released with Galileo. To be fair to Martin this release that
>> fixes a problem was only made a few hours ago. So the obvious next
>> question is - can you create a Update site download locally given and
>> earlier Update site and a set of update jar files?
>>
>> Thx.
>>
>> David
>>
>> Simon Kaegi wrote:
>>> "David Wynter" <david@roamware.co.uk> wrote in message
>>> news:4A54BCFC.6000201@roamware.co.uk...
>>>> Hi,
>>>>
>>>> That explains everything except the weird thing with the Back and Next
>>>> keys changing the detected dependencies preventing a full uninstall. It
>>>> even explains that when I did eventually uninstall the std Teneo plugin
>>>> it no longer appears installed, but Update tells you it is installed.
>>>> What a mess.
>>>
>>> Agrred. The weird back and next stuff is bizarre. I will try that out
>>> and see if I can duplicate it or if you manage to refine your technique
>>> that would be good.
>>> That said the UI is not really in control and director/planner should
>>> prevent anything illegal from a dependency perspective from occuring.
>>>
>>>> So, when Martin releases a new version of his managed Teneo plugin, how
>>>> do we install it? It is not on an Update site anywhere...
>>>>
>>> That's a pity as I really wish people would take the time and use the
>>> eclipse web site to distribute this stuff. It looks like you can
>>> download the zipped update site. You should be able to unzip it and add
>>> it as Local repository and then install from it.
>>>
>>>> Looks like I am going to have to reinstal Galileo.
>>>>
>>>> David
>>>>
>>>> Simon Kaegi wrote:
>>>>> "David Wynter" <david@roamware.co.uk> wrote in message
>>>>> news:4A549E15.3000204@roamware.co.uk...
>>>>>> Hi,
>>>>>>
>>>>>> "Install new software" tells me that current version 1.1.0 is already
>>>>>> installed and nothing to do. I am trying to update to V1.1.1 as it
>>>>>> solves a problem with 1.1.0
>>>>>>
>>>>> How was Teneo 1.1.0 installed? From the update site? as part of a
>>>>> pre-existing product?
>>>>> If Teneo was installed using the p2 UI you will need to update it with
>>>>> the p2 UI as the platform will view it as part of the "managed"
>>>>> install.
>>>>>
>>>>> One way to think of this is that eclipse consists of "managed" pieces
>>>>> installed via the p2 UI (or p2 director) application and "unmanaged"
>>>>> pieces installed by placing arbitrary bundles in dropins. If there is
>>>>> a dependency discrepency, the managed pieces always take priority so
>>>>> this is why updating an existing "managed" component by using dropins
>>>>> generally won' work.
>>>>>
>>>>>> At one point I tried manually deleting the old version of the jars
>>>>>> and features and leaving the newer version there, 1.1.1. Since that
>>>>>> operation Eclipse thinks it has no Teneo plugin. When I added back
>>>>>> the original jars and feature (1.1.0) it still thinks there is no
>>>>>> Teneo plugin there, when looking at "About Eclipse Features" for
>>>>>> modelling. Where does p2 store information about what plugins are
>>>>>> installed and how do you refresh it?
>>>>>>
>>>>> p2 stores the information on what's installed in the profileRegistry.
>>>>> (p2/org.eclipse.equinox.p2.engine/profileRegistry/{profileNa me}.profile).
>>>>> This folder holds the history of what's been installed so the current
>>>>> profile contents are contained in the latest profile file. Manually
>>>>> deleting plugins from the bundle pool (e.g. eclipse/plugins and
>>>>> eclipse/features) as you've found out is fraught with disaster. If you
>>>>> arbitrarily remove the bundles for a product you can easily end up in
>>>>> a situation where the profile registry believes a feature is installed
>>>>> although many of the bundles are no longer present.
>>>>>
>>>>> The "unmanaged" portion of the install e.g. dropins is self-healing as
>>>>> it is scanned each time at startup however the "managed" chunk are
>>>>> not, so if it becomes corrupt or damaged in some way you're in
>>>>> trouble. We have a GSOC student looking at how we might handle
>>>>> recovery of the "managed" install however that work is not complete or
>>>>> in the main trunk right now. This tool is like a reset button and
>>>>> would restore the base platform and what ever top-level pieces it can
>>>>> validate as complete and is really a last resort to bring a broken
>>>>> install back to life. I don't really think it's applicable to what
>>>>> you're doing but am just mentioning it as work in progress on
>>>>> improving our recovery story.
>>>>>
>>>>>> I also ran with "eclipse -debug -clean -console", the "Interactive
>>>>>> console" does not take any input at the prompt?
>>>>>>
>>>>>> David
>>>>>>
>>>>>>
>>>>>>
>>>>>> Paul Webster wrote:
>>>>>>> David Wynter wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> My experience with the dropins directory has never been good. I am
>>>>>>>> trying to deploy the latest EMF Teneo update in the dropins
>>>>>>>> directory. It uses the dropins/eclipse/plugins and
>>>>>>>> dropins/eclipse/features layout. It simply does not deploy it.
>>>>>>>> Running with eclipse -clean - debug gives me nothing about why it
>>>>>>>> does not deploy. In desperation I put the plugins directly in
>>>>>>>> eclipse/plugins and similarly for features and start with
>>>>>>>> ecliuspe -clean -debug. The newer version of the plugin does not
>>>>>>>> appear as a plugin, so cannot include it as a dependency on my
>>>>>>>> project. So I am stopped dead,
>>>>>>> There doesn't seem to be anything out of the ordinary in what you
>>>>>>> are doing. Are there any errors in your error log with the dropins
>>>>>>> config you are using? If you start eclipse with -console to get the
>>>>>>> OSGi console, can you see the new plugins using 'ss'?
>>>>>>>
>>>>>>> But if you're stuck, why not use Install New Software to install it
>>>>>>> instead of dropins? Installing the galileo EMF Teneo into Galileo
>>>>>>> eclipse should definitely be supported :-)
>>>>>>>
>>>>>>> PW
>>>>>>>
>>>
|
|
|
Re: Dropins on Galileo not working? [message #135061 is a reply to message #134996] |
Thu, 09 July 2009 04:11  |
Eclipse User |
|
|
|
Originally posted by: david.roamware.co.uk
Hi,
As it turns out the expansion of the jar did not work, lots of different
exceptions instead. I have to revert to Ganymede.
Where exactly does it explain to both commiters to the 'managed' bundles
and to the average punter that the 'managed' bundles are not to be
deployed via dropins? It just lost me 2 days of messing about, it should
state it somewhere in the Help content for dropins at the very least.
David
Simon Kaegi wrote:
> That should be ok so long as teneo.hibernate.jar is an internal detail of
> the bundle.
>
> "David Wynter" <david@roamware.co.uk> wrote in message
> news:4A54C4D1.8080503@roamware.co.uk...
>> In answer to my own question, having now discovered artifacts.xml,
>> site.xml and content.xml, only with a lot of painstaking effort could you
>> update an existing Update site to use a set of about 7 new jars. There may
>> be some signing in there too, in which case probably not possible.
>>
>> so my other question still stands, can I expand the teneo.hibernate jar
>> into a directory and delete the original jar without upsetting a managed
>> set of bundles like teneo?
>>
>> David
>>
>> David Wynter wrote:
>>> Hi,
>>>
>>> Actually it is V1.1.0 that you can download as a Update site, that is the
>>> version released with Galileo. To be fair to Martin this release that
>>> fixes a problem was only made a few hours ago. So the obvious next
>>> question is - can you create a Update site download locally given and
>>> earlier Update site and a set of update jar files?
>>>
>>> Thx.
>>>
>>> David
>>>
>>> Simon Kaegi wrote:
>>>> "David Wynter" <david@roamware.co.uk> wrote in message
>>>> news:4A54BCFC.6000201@roamware.co.uk...
>>>>> Hi,
>>>>>
>>>>> That explains everything except the weird thing with the Back and Next
>>>>> keys changing the detected dependencies preventing a full uninstall. It
>>>>> even explains that when I did eventually uninstall the std Teneo plugin
>>>>> it no longer appears installed, but Update tells you it is installed.
>>>>> What a mess.
>>>> Agrred. The weird back and next stuff is bizarre. I will try that out
>>>> and see if I can duplicate it or if you manage to refine your technique
>>>> that would be good.
>>>> That said the UI is not really in control and director/planner should
>>>> prevent anything illegal from a dependency perspective from occuring.
>>>>
>>>>> So, when Martin releases a new version of his managed Teneo plugin, how
>>>>> do we install it? It is not on an Update site anywhere...
>>>>>
>>>> That's a pity as I really wish people would take the time and use the
>>>> eclipse web site to distribute this stuff. It looks like you can
>>>> download the zipped update site. You should be able to unzip it and add
>>>> it as Local repository and then install from it.
>>>>
>>>>> Looks like I am going to have to reinstal Galileo.
>>>>>
>>>>> David
>>>>>
>>>>> Simon Kaegi wrote:
>>>>>> "David Wynter" <david@roamware.co.uk> wrote in message
>>>>>> news:4A549E15.3000204@roamware.co.uk...
>>>>>>> Hi,
>>>>>>>
>>>>>>> "Install new software" tells me that current version 1.1.0 is already
>>>>>>> installed and nothing to do. I am trying to update to V1.1.1 as it
>>>>>>> solves a problem with 1.1.0
>>>>>>>
>>>>>> How was Teneo 1.1.0 installed? From the update site? as part of a
>>>>>> pre-existing product?
>>>>>> If Teneo was installed using the p2 UI you will need to update it with
>>>>>> the p2 UI as the platform will view it as part of the "managed"
>>>>>> install.
>>>>>>
>>>>>> One way to think of this is that eclipse consists of "managed" pieces
>>>>>> installed via the p2 UI (or p2 director) application and "unmanaged"
>>>>>> pieces installed by placing arbitrary bundles in dropins. If there is
>>>>>> a dependency discrepency, the managed pieces always take priority so
>>>>>> this is why updating an existing "managed" component by using dropins
>>>>>> generally won' work.
>>>>>>
>>>>>>> At one point I tried manually deleting the old version of the jars
>>>>>>> and features and leaving the newer version there, 1.1.1. Since that
>>>>>>> operation Eclipse thinks it has no Teneo plugin. When I added back
>>>>>>> the original jars and feature (1.1.0) it still thinks there is no
>>>>>>> Teneo plugin there, when looking at "About Eclipse Features" for
>>>>>>> modelling. Where does p2 store information about what plugins are
>>>>>>> installed and how do you refresh it?
>>>>>>>
>>>>>> p2 stores the information on what's installed in the profileRegistry.
>>>>>> (p2/org.eclipse.equinox.p2.engine/profileRegistry/{profileNa me}.profile).
>>>>>> This folder holds the history of what's been installed so the current
>>>>>> profile contents are contained in the latest profile file. Manually
>>>>>> deleting plugins from the bundle pool (e.g. eclipse/plugins and
>>>>>> eclipse/features) as you've found out is fraught with disaster. If you
>>>>>> arbitrarily remove the bundles for a product you can easily end up in
>>>>>> a situation where the profile registry believes a feature is installed
>>>>>> although many of the bundles are no longer present.
>>>>>>
>>>>>> The "unmanaged" portion of the install e.g. dropins is self-healing as
>>>>>> it is scanned each time at startup however the "managed" chunk are
>>>>>> not, so if it becomes corrupt or damaged in some way you're in
>>>>>> trouble. We have a GSOC student looking at how we might handle
>>>>>> recovery of the "managed" install however that work is not complete or
>>>>>> in the main trunk right now. This tool is like a reset button and
>>>>>> would restore the base platform and what ever top-level pieces it can
>>>>>> validate as complete and is really a last resort to bring a broken
>>>>>> install back to life. I don't really think it's applicable to what
>>>>>> you're doing but am just mentioning it as work in progress on
>>>>>> improving our recovery story.
>>>>>>
>>>>>>> I also ran with "eclipse -debug -clean -console", the "Interactive
>>>>>>> console" does not take any input at the prompt?
>>>>>>>
>>>>>>> David
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Paul Webster wrote:
>>>>>>>> David Wynter wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> My experience with the dropins directory has never been good. I am
>>>>>>>>> trying to deploy the latest EMF Teneo update in the dropins
>>>>>>>>> directory. It uses the dropins/eclipse/plugins and
>>>>>>>>> dropins/eclipse/features layout. It simply does not deploy it.
>>>>>>>>> Running with eclipse -clean - debug gives me nothing about why it
>>>>>>>>> does not deploy. In desperation I put the plugins directly in
>>>>>>>>> eclipse/plugins and similarly for features and start with
>>>>>>>>> ecliuspe -clean -debug. The newer version of the plugin does not
>>>>>>>>> appear as a plugin, so cannot include it as a dependency on my
>>>>>>>>> project. So I am stopped dead,
>>>>>>>> There doesn't seem to be anything out of the ordinary in what you
>>>>>>>> are doing. Are there any errors in your error log with the dropins
>>>>>>>> config you are using? If you start eclipse with -console to get the
>>>>>>>> OSGi console, can you see the new plugins using 'ss'?
>>>>>>>>
>>>>>>>> But if you're stuck, why not use Install New Software to install it
>>>>>>>> instead of dropins? Installing the galileo EMF Teneo into Galileo
>>>>>>>> eclipse should definitely be supported :-)
>>>>>>>>
>>>>>>>> PW
>>>>>>>>
>
>
|
|
|
Goto Forum:
Current Time: Fri May 09 00:05:35 EDT 2025
Powered by FUDForum. Page generated in 0.04445 seconds
|