Eclipse Community Forums: Equinox » weird behavior by director

Help

Home

Home » Eclipse Projects » Equinox » weird behavior by director

Show: Today's Messages :: Show Polls :: Message Navigator

weird behavior by director [message #547911]

Tue, 20 July 2010 07:32

David

Messages: 88
Registered: July 2009

Member

I use the director in headless mode to get an eclipse product i build.

The product is built and exported via the PDE. It creates an P2 repository and an product directory (win32/win32/X86). Testing the product all looks ok, all preferences set. I patch 2 plugins from the eclipse release (org.eclipse.core.net and org.eclipse.ui.net) to disable proxy support. These settings are also ok.

I test to aquire the product from the local repository i.e ( director -i se.rsv.zz.eclipse.helios.product -r file:/c:/ws/eclipse_product/helios3/eclipse3.6 -d C:\Program\Eclipse\eclipse3.6)

i once again start the product all looks ok all prefs set and imported including the patched proxy settings.

I upload the repository to our http server. I install the product via the director is fine no problems. Starting no problem, but now the org.eclipse.ui.net and org.eclipse.core.net defaulted back to the original instead of my patched ones.

how is that possible? its the same repository! install from locally its my patched org.eclipse.core.net/ui.net install from http:// its the original..

can any logging be done to help track down where this problem occurs?

The plugins use the same version that is required by org.eclipse.platform..

Report message to a moderator

Re: weird behavior by director [message #548074 is a reply to message #547911]

Tue, 20 July 2010 15:02

Andrew Niefer

Messages: 990
Registered: July 2009

Senior Member

Did you increment the version of your patched core.net/ui.net bundles?

There is an assumption in p2 that 1 version == 1 set of bytes. If the
original bundles are around somewhere else that the director knows about
and they have the same version, there is no particular reason for the
director to use one over the other.

-Andrew

David wrote:

> I use the director in headless mode to get an eclipse product i build.
>
> The product is built and exported via the PDE. It creates an P2 repository
> and an product directory (win32/win32/X86). Testing the product all looks
> ok, all preferences set. I patch 2 plugins from the eclipse release
> (org.eclipse.core.net and org.eclipse.ui.net) to disable proxy support.
> These settings are also ok.
>
> I test to aquire the product from the local repository i.e ( director -i
> se.rsv.zz.eclipse.helios.product -r
> file:/c:/ws/eclipse_product/helios3/eclipse3.6 -d
> C:\Program\Eclipse\eclipse3.6)
>
> i once again start the product all looks ok all prefs set and imported
> including the patched proxy settings.
>
> I upload the repository to our http server. I install the product via the
> director is fine no problems. Starting no problem, but now the
> org.eclipse.ui.net and org.eclipse.core.net defaulted back to the original
> instead of my patched ones.
>
> how is that possible? its the same repository! install from locally its my
> patched org.eclipse.core.net/ui.net install from http:// its the
> original..
>
> can any logging be done to help track down where this problem occurs?
>
> The plugins use the same version that is required by
> org.eclipse.platform..

Report message to a moderator

Re: weird behavior by director [message #548213 is a reply to message #547911]

Wed, 21 July 2010 06:50

David

Messages: 88
Registered: July 2009

Member

i didn't increment the versions in the plugin.xml if i do that org.eclipse.platform cant find its dependency.

Processing inclusion from feature org.eclipse.platform: Unable to find plug-in: org.eclipse.core.net_1.2.100.I20100511-0800. Please check the error log for more details.

When i incremented my versions seems org.eclipse.platform feature has explicit dependency on that version?

I removed the two plugins from the target platform. (*.target file) so it shouldn't be able to pick it.

The target platform is an p2 repo made via the aggregator, and i just exclude the two bundles i don't want in my target (via the target file) but have in my workspace.

I tried to build the two bundles separately with the versions org.eclipse.platform wants, then include them in the target repo. Didn't suceed here either - signing issues, md5 hashes etc. Should have guessed that from start.

But this doesn't explain the behavior of the director though in my opinion.

Why did it behave differently if installing from file:/ then from http:// ? it was the same repository just local or over http?

From where did it fetch the org.eclipse.(core|ui).net over http?

Why did it fetch (in my eyes) the correct ones when installing over file:/?

Why was the original org.eclipse.(core|ui).net available in http but not when using file:/?

most importantly maybe, how do i do this correctly? Smile

Report message to a moderator

Previous Topic:	Message Passing across OSGi bundles
Next Topic:	Director can't handle proxy if it's used programmatically in own headless plugin

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 12:51:23 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter