Pascal Rapicault | 1 Feb 03:15 2008
Picon

Re: [prov] p2 provisioned eclipse missing companion library

You should be able to find good p2 data at
http://update.eclipse.org/eclipse/testUpdates/

                                                                                                                                             
  From:       Timothy Webb <tim@...>                                                                                                  

  To:         Equinox development mailing list <equinox-dev@...>                                                                     

  Date:       01/31/2008 04:44 PM                                                                                                            

  Subject:    Re: [equinox-dev] [prov] p2 provisioned eclipse missing     companion   library                                                

Pascal,

Thanks for the pointers.  The eclipse.ini as well as other files are
indeed being dropped down by p2.  Perhaps this is an issue that
relates to the metadata generator producing output that is not
expected.  How and when did you last generate the p2 metadata you are
running against?

Here's what I see for the toolingorg.eclipse.launcher...'s touchpoints:

<touchpoint id="native" version="1.0.0"/>
<touchpointData size="1">
   <instructions size="2">
     <instruction key="uninstall">
             cleanupzip(source: <at> artifact, target:${installFolder});
     </instruction>
     <instruction key="install">
             unzip(source: <at> artifact, target:${installFolder});
(Continue reading)

Susan Franklin McCourt | 1 Feb 04:20 2008
Picon

p2 test repo working?

Am I the only one seeing this when I try to use the URL below?
I haven't been able to connect to the test updates URL since it was repopulated....

!ENTRY org.eclipse.equinox.p2.ui 4 0 2008-01-31 19:21:01.156
!MESSAGE Error loading repository http://update.eclipse.org/eclipse/testUpdates/
!STACK 1
org.eclipse.equinox.p2.core.ProvisionException: No repository found at http://update.eclipse.org/eclipse/testUpdates/
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.fail(MetadataRepositoryManager.java:160)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:292)
at org.eclipse.equinox.p2.ui.operations.ProvisioningUtil.loadMetadataRepository(ProvisioningUtil.java:57)
at org.eclipse.equinox.p2.ui.model.MetadataRepositoryElement.getMetadataRepository(MetadataRepositoryElement.java:83)
at org.eclipse.equinox.p2.ui.model.MetadataRepositoryElement.getQueryable(MetadataRepositoryElement.java:72)
at org.eclipse.equinox.internal.p2.ui.sdk.ProvSDKQueryProvider.getQueryDescriptor(ProvSDKQueryProvider.java:60)
at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchChildren(RemoteQueriedElement.java:44)
at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchDeferredChildren(RemoteQueriedElement.java:33)
at org.eclipse.equinox.internal.p2.ui.viewers.AvailableIUContentProvider$2.run(AvailableIUContentProvider.java:159)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

<div>
<p>Am I the only one seeing this when I try to use the URL below?<br>
I haven't been able to connect to the test updates URL since it was repopulated....<br><br>!ENTRY org.eclipse.equinox.p2.ui 4 0 2008-01-31 19:21:01.156<br>!MESSAGE Error loading repository <a href="http://update.eclipse.org/eclipse/testUpdates/">http://update.eclipse.org/eclipse/testUpdates/</a><br>!STACK 1<br>org.eclipse.equinox.p2.core.ProvisionException: No repository found at <a href="http://update.eclipse.org/eclipse/testUpdates/">http://update.eclipse.org/eclipse/testUpdates/</a><br>	at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.fail(MetadataRepositoryManager.java:160)<br>	at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:292)<br>	at org.eclipse.equinox.p2.ui.operations.ProvisioningUtil.loadMetadataRepository(ProvisioningUtil.java:57)<br>	at org.eclipse.equinox.p2.ui.model.MetadataRepositoryElement.getMetadataRepository(MetadataRepositoryElement.java:83)<br>	at org.eclipse.equinox.p2.ui.model.MetadataRepositoryElement.getQueryable(MetadataRepositoryElement.java:72)<br>	at org.eclipse.equinox.internal.p2.ui.sdk.ProvSDKQueryProvider.getQueryDescriptor(ProvSDKQueryProvider.java:60)<br>	at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchChildren(RemoteQueriedElement.java:44)<br>	at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchDeferredChildren(RemoteQueriedElement.java:33)<br>	at org.eclipse.equinox.internal.p2.ui.viewers.AvailableIUContentProvider$2.run(AvailableIUContentProvider.java:159)<br>	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
</p>
</div>
Timothy Webb | 1 Feb 04:21 2008

Re: p2 test repo working?

I'm seeing the same thing.  When I access the URLs directly, I see a 404 error.


Neither work for me.

Tim

On Jan 31, 2008, at 9:20 PM, Susan Franklin McCourt wrote:

Am I the only one seeing this when I try to use the URL below?
I haven't been able to connect to the test updates URL since it was repopulated....

!ENTRY org.eclipse.equinox.p2.ui 4 0 2008-01-31 19:21:01.156
!MESSAGE Error loading repository http://update.eclipse.org/eclipse/testUpdates/
!STACK 1
org.eclipse.equinox.p2.core.ProvisionException: No repository found at http://update.eclipse.org/eclipse/testUpdates/
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.fail(MetadataRepositoryManager.java:160)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:292)
at org.eclipse.equinox.p2.ui.operations.ProvisioningUtil.loadMetadataRepository(ProvisioningUtil.java:57)
at org.eclipse.equinox.p2.ui.model.MetadataRepositoryElement.getMetadataRepository(MetadataRepositoryElement.java:83)
at org.eclipse.equinox.p2.ui.model.MetadataRepositoryElement.getQueryable(MetadataRepositoryElement.java:72)
at org.eclipse.equinox.internal.p2.ui.sdk.ProvSDKQueryProvider.getQueryDescriptor(ProvSDKQueryProvider.java:60)
at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchChildren(RemoteQueriedElement.java:44)
at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchDeferredChildren(RemoteQueriedElement.java:33)
at org.eclipse.equinox.internal.p2.ui.viewers.AvailableIUContentProvider$2.run(AvailableIUContentProvider.java:159)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

<div>I'm seeing the same thing. &nbsp;When I access the URLs directly, I see a 404 error.<div><br class="webkit-block-placeholder"></div>
<div><a href="http://update.eclipse.org/eclipse/testUpdates/content.jar">http://update.eclipse.org/eclipse/testUpdates/content.jar</a></div>
<div><a href="http://update.eclipse.org/eclipse/testUpdates/content.xml">http://update.eclipse.org/eclipse/testUpdates/content.xml</a></div>
<div><br class="webkit-block-placeholder"></div>
<div>Neither work for me.</div>
<div><br class="webkit-block-placeholder"></div>
<div>Tim</div>
<div>
<br><div>
<div>On Jan 31, 2008, at 9:20 PM, Susan Franklin McCourt wrote:</div>
<br class="Apple-interchange-newline"><blockquote type="cite">
<div><p>Am I the only one seeing this when I try to use the URL below?<br> I haven't been able to connect to the test updates URL since it was repopulated....<br><br>!ENTRY org.eclipse.equinox.p2.ui 4 0 2008-01-31 19:21:01.156<br>!MESSAGE Error loading repository <a href="http://update.eclipse.org/eclipse/testUpdates/">http://update.eclipse.org/eclipse/testUpdates/</a><br>!STACK 1<br>org.eclipse.equinox.p2.core.ProvisionException: No repository found at <a href="http://update.eclipse.org/eclipse/testUpdates/">http://update.eclipse.org/eclipse/testUpdates/</a><br>	at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.fail(MetadataRepositoryManager.java:160)<br>	at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:292)<br>	at org.eclipse.equinox.p2.ui.operations.ProvisioningUtil.loadMetadataRepository(ProvisioningUtil.java:57)<br>	at org.eclipse.equinox.p2.ui.model.MetadataRepositoryElement.getMetadataRepository(MetadataRepositoryElement.java:83)<br>	at org.eclipse.equinox.p2.ui.model.MetadataRepositoryElement.getQueryable(MetadataRepositoryElement.java:72)<br>	at org.eclipse.equinox.internal.p2.ui.sdk.ProvSDKQueryProvider.getQueryDescriptor(ProvSDKQueryProvider.java:60)<br>	at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchChildren(RemoteQueriedElement.java:44)<br>	at org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchDeferredChildren(RemoteQueriedElement.java:33)<br>	at org.eclipse.equinox.internal.p2.ui.viewers.AvailableIUContentProvider$2.run(AvailableIUContentProvider.java:159)<br>	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) </p></div>_______________________________________________<br>equinox-dev mailing list<br><a href="mailto:equinox-dev@...">equinox-dev@...</a><br>https://dev.eclipse.org/mailman/listinfo/equinox-dev<br>
</blockquote>
</div>
<br>
</div>
</div>
Timothy Webb | 1 Feb 04:26 2008

Re: [prov] p2 provisioned eclipse missing companion library

Pascal,

I'm close now but after a number of hours in the debugger, I'm finding  
that the resolver isn't correctly finding the IU fragments for some of  
the bundles.  Are others attempting to do installation of things other  
than the SDK or other pre-configured line-ups?

All my meta data now looks correct but it still am having issues  
having the install of IUs work.

Tim

On Jan 31, 2008, at 3:14 PM, Pascal Rapicault wrote:

> John and I have been doing that since M3 (some hickups of course  
> occured)
> and that worked and I confirm that yesterday's build works as well.
> However we are deploying a 3.4 eclipse and not a 3.3.
> Normally when p2 installs the SDK, a -startup and -launcher.library
> arguments are being set to point ot the jar.
>
> You say: In our eclipse.ini file we drop down next to the exe,
> Do you actually drop the ini file? If so this is the pb. The ini  
> files are
> no longer file that you lay down. Instead they result from the  
> installation
> of some IUs (for example, see the  
> toolingorg.eclipse.equinox.launcher IU)
>
> HTH,
>
> PaScaL
>
>
> |------------>
> | From:      |
> |------------>
>> --------------------------------------------------------------------------------------------------------------------------------------------------|
>  |Timothy Webb  
> < 
> tim 
>  <at> trwebb 
> .com 
> > 
>                                                                                                                      |
>> --------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | To:        |
> |------------>
>> --------------------------------------------------------------------------------------------------------------------------------------------------|
>  |Equinox development mailing list <equinox- 
> dev 
>  <at> eclipse 
> .org 
> > 
>                                                                                         |
>> --------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Date:      |
> |------------>
>> --------------------------------------------------------------------------------------------------------------------------------------------------|
>  |01/31/2008 03:47  
> PM 
>                                                                                                                                |
>> --------------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Subject:   |
> |------------>
>> --------------------------------------------------------------------------------------------------------------------------------------------------|
>  |[equinox-dev] [prov] p2 provisioned eclipse missing companion      
> library 
>                                                                          |
>> --------------------------------------------------------------------------------------------------------------------------------------------------|
>
>
>
>
>
> Are others having success using p2 to provision an Eclipse where the
> cache directory is not collocated with the eclipse exe?
>
> I'm running into an issue where despite having what appears to be the
> right set of software downloaded in the cache, configured in the
> platform.xml / config.ini, etc., each time I try to run the
> eclipse.exe, I receive "The eclipse executable launcher was unable to
> locate its companion launcher jar."  In looking through the C code for
> the launcher, it looks like Eclipse is designed to search for the
> companion library in the plugins area, located near the exe, or by
> specifying --launcher.library on the command line.  In our eclipse.ini
> file we drop down next to the exe, I don't see a --launcher.library
> argument configured.  Is this something that should be setup by
> default in the normal touchpoints?  Or, is there a branch of the
> Eclipse.exe that is designed to work better with p2-style deployments?
>
> Thanks,
> Tim
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@...
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@...
> https://dev.eclipse.org/mailman/listinfo/equinox-dev

Pascal Rapicault | 1 Feb 05:59 2008
Picon

Re: [prov] p2 provisioned eclipse missing companion library

When I read your note I went testing with a local copy of the data that was
supposed to be on the test update site and it seems to work (see steps
below).
 What I usually find not easy to get right is the metadata generation. The
way the generator is setup into the launch config is to generate a top
level IU refering to all the IUs that are generated by this invocation of
the generator. As you can imagine this is an aweful hack that will soon be
discarded. So my recommendation is to generate metadata piece meal and be
sure that the folder only contains the bits and pieces you really wnat
(e.g. if you want to generate MD for EMF, create a folder containing only
EMF).
As for creating an IU allowing the installation of multiple configurations
(like we do today with the SDK), that requires some magic that you can find
in our build files (see eclipse project org.eclipse.releng.eclipsebuild,
folder /equinox/equinox.prov/run.xml). In short we overlay the launcher
feature over the SDK and massage it at gen time. The real path forward on
that space is to derive most / all of the information from a .product file
thus allowing the creation of the metadata in one call and then do the
creation of the artifacts on another one. This is still be to defined but
Andrew N is actively working on it.

HTH,

PaScaL

Steps I tried:
- install 3.4 I build from next week using the admin ui
- start
- install releng tools
- install
- install agent.feature.featureGroup
- install user.ui.feature.featureGroup
- starts (then I can't see the user ui but that's an implementation detail
:-))

                                                                                                                                             
  From:       Timothy Webb <tim@...>                                                                                                  

  To:         Equinox development mailing list <equinox-dev@...>                                                                     

  Date:       01/31/2008 10:27 PM                                                                                                            

  Subject:    Re: [equinox-dev] [prov] p2 provisioned eclipse missing     companion   library                                                

Pascal,

I'm close now but after a number of hours in the debugger, I'm finding
that the resolver isn't correctly finding the IU fragments for some of
the bundles.  Are others attempting to do installation of things other
than the SDK or other pre-configured line-ups?

All my meta data now looks correct but it still am having issues
having the install of IUs work.

Tim

On Jan 31, 2008, at 3:14 PM, Pascal Rapicault wrote:

> John and I have been doing that since M3 (some hickups of course
> occured)
> and that worked and I confirm that yesterday's build works as well.
> However we are deploying a 3.4 eclipse and not a 3.3.
> Normally when p2 installs the SDK, a -startup and -launcher.library
> arguments are being set to point ot the jar.
>
> You say: In our eclipse.ini file we drop down next to the exe,
> Do you actually drop the ini file? If so this is the pb. The ini
> files are
> no longer file that you lay down. Instead they result from the
> installation
> of some IUs (for example, see the
> toolingorg.eclipse.equinox.launcher IU)
>
> HTH,
>
> PaScaL
>
>
> |------------>
> | From:      |
> |------------>
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|

>  |Timothy Webb
> <
> tim
>  <at> trwebb
> .com
> >
>
|
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|

> |------------>
> | To:        |
> |------------>
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|

>  |Equinox development mailing list <equinox-
> dev
>  <at> eclipse
> .org
> >
>
|
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|

> |------------>
> | Date:      |
> |------------>
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|

>  |01/31/2008 03:47
> PM
>
|
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|

> |------------>
> | Subject:   |
> |------------>
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|

>  |[equinox-dev] [prov] p2 provisioned eclipse missing companion
> library
>
|
>>
--------------------------------------------------------------------------------------------------------------------------------------------------|

>
>
>
>
>
> Are others having success using p2 to provision an Eclipse where the
> cache directory is not collocated with the eclipse exe?
>
> I'm running into an issue where despite having what appears to be the
> right set of software downloaded in the cache, configured in the
> platform.xml / config.ini, etc., each time I try to run the
> eclipse.exe, I receive "The eclipse executable launcher was unable to
> locate its companion launcher jar."  In looking through the C code for
> the launcher, it looks like Eclipse is designed to search for the
> companion library in the plugins area, located near the exe, or by
> specifying --launcher.library on the command line.  In our eclipse.ini
> file we drop down next to the exe, I don't see a --launcher.library
> argument configured.  Is this something that should be setup by
> default in the normal touchpoints?  Or, is there a branch of the
> Eclipse.exe that is designed to work better with p2-style deployments?
>
> Thanks,
> Tim
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@...
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@...
> https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@...
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Pascal Rapicault | 1 Feb 05:12 2008
Picon

Re: p2 test repo working?

So am I... I have the feeling that things have been cleared out ... sigh...
But I swear that earlier today I went there and it worked :-)

                                                                                                                                             
  From:       Timothy Webb <tim@...>                                                                                                  

  To:         Equinox development mailing list <equinox-dev@...>                                                                     

  Date:       01/31/2008 10:22 PM                                                                                                            

  Subject:    Re: [equinox-dev] p2 test repo working?                                                                                        

I'm seeing the same thing.  When I access the URLs directly, I see a 404
error.

http://update.eclipse.org/eclipse/testUpdates/content.jar
http://update.eclipse.org/eclipse/testUpdates/content.xml

Neither work for me.

Tim

On Jan 31, 2008, at 9:20 PM, Susan Franklin McCourt wrote:

      Am I the only one seeing this when I try to use the URL below?
      I haven't been able to connect to the test updates URL since it was
      repopulated....

      !ENTRY org.eclipse.equinox.p2.ui 4 0 2008-01-31 19:21:01.156
      !MESSAGE Error loading repository
      http://update.eclipse.org/eclipse/testUpdates/
      !STACK 1
      org.eclipse.equinox.p2.core.ProvisionException: No repository found
      at http://update.eclipse.org/eclipse/testUpdates/
      at
      org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.fail(
      MetadataRepositoryManager.java:160)
      at
      org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(
      MetadataRepositoryManager.java:292)
      at
      org.eclipse.equinox.p2.ui.operations.ProvisioningUtil.loadMetadataRepository(
      ProvisioningUtil.java:57)
      at
      org.eclipse.equinox.p2.ui.model.MetadataRepositoryElement.getMetadataRepository(
      MetadataRepositoryElement.java:83)
      at
      org.eclipse.equinox.p2.ui.model.MetadataRepositoryElement.getQueryable(
      MetadataRepositoryElement.java:72)
      at
      org.eclipse.equinox.internal.p2.ui.sdk.ProvSDKQueryProvider.getQueryDescriptor(
      ProvSDKQueryProvider.java:60)
      at
      org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchChildren(
      RemoteQueriedElement.java:44)
      at
      org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchDeferredChildren(
      RemoteQueriedElement.java:33)
      at
      org.eclipse.equinox.internal.p2.ui.viewers.AvailableIUContentProvider$2.run(
      AvailableIUContentProvider.java:159)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

      _______________________________________________
      equinox-dev mailing list
      equinox-dev@...
      https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@...
https://dev.eclipse.org/mailman/listinfo/equinox-dev

DJ Houghton | 1 Feb 11:43 2008
Picon

Re: p2 test repo working?

There must have been something temporarily wrong with the server because it
seems to be corrected now... the content is there.

                                                                           
             Pascal                                                        
             Rapicault/Ottawa/                                             
             IBM <at> IBMCA                                                  To 
             Sent by:                  Equinox development mailing list    
             equinox-dev-bounc         <equinox-dev@...>           
             es@...                                             cc 

                                                                   Subject 
             01/31/2008 11:12          Re: [equinox-dev] p2 test repo      
             PM                        working?                            

                                                                           
             Please respond to                                             
                  Equinox                                                  
                development                                                
               mailing list                                                
             <equinox-dev <at> ecli                                             
                 pse.org>                                                  

So am I... I have the feeling that things have been cleared out ... sigh...
But I swear that earlier today I went there and it worked :-)

  From:       Timothy Webb <tim@...>

  To:         Equinox development mailing list <equinox-dev@...>

  Date:       01/31/2008 10:22 PM

  Subject:    Re: [equinox-dev] p2 test repo working?

I'm seeing the same thing.  When I access the URLs directly, I see a 404
error.

http://update.eclipse.org/eclipse/testUpdates/content.jar
http://update.eclipse.org/eclipse/testUpdates/content.xml

Neither work for me.

Tim

On Jan 31, 2008, at 9:20 PM, Susan Franklin McCourt wrote:

      Am I the only one seeing this when I try to use the URL below?
      I haven't been able to connect to the test updates URL since it was
      repopulated....

      !ENTRY org.eclipse.equinox.p2.ui 4 0 2008-01-31 19:21:01.156
      !MESSAGE Error loading repository
      http://update.eclipse.org/eclipse/testUpdates/
      !STACK 1
      org.eclipse.equinox.p2.core.ProvisionException: No repository found
      at http://update.eclipse.org/eclipse/testUpdates/
      at

org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.fail(

      MetadataRepositoryManager.java:160)
      at

org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(

      MetadataRepositoryManager.java:292)
      at

org.eclipse.equinox.p2.ui.operations.ProvisioningUtil.loadMetadataRepository(

      ProvisioningUtil.java:57)
      at

org.eclipse.equinox.p2.ui.model.MetadataRepositoryElement.getMetadataRepository(

      MetadataRepositoryElement.java:83)
      at

org.eclipse.equinox.p2.ui.model.MetadataRepositoryElement.getQueryable(
      MetadataRepositoryElement.java:72)
      at

org.eclipse.equinox.internal.p2.ui.sdk.ProvSDKQueryProvider.getQueryDescriptor(

      ProvSDKQueryProvider.java:60)
      at

org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchChildren(

      RemoteQueriedElement.java:44)
      at

org.eclipse.equinox.internal.p2.ui.model.RemoteQueriedElement.fetchDeferredChildren(

      RemoteQueriedElement.java:33)
      at

org.eclipse.equinox.internal.p2.ui.viewers.AvailableIUContentProvider$2.run(

      AvailableIUContentProvider.java:159)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

      _______________________________________________
      equinox-dev mailing list
      equinox-dev@...
      https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@...
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@...
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Timothy Webb | 1 Feb 14:23 2008

Re: p2 test repo working?

Can you confirm what URL you are using to connect?  I receive 404  
accessing the following URLs for a browser:

http://update.eclipse.org/eclipse/testUpdates/content.jar
http://update.eclipse.org/eclipse/testUpdates/content.xml
http://update.eclipse.org/eclipse/testUpdates/site.xml

Or is p2 caching what was the last known good configuration for these  
sites?

Tim

On Feb 1, 2008, at 4:43 AM, DJ Houghton wrote:

> There must have been something temporarily wrong with the server  
> because it
> seems to be corrected now... the content is there.

DJ Houghton | 1 Feb 14:36 2008
Picon

Re: p2 test repo working?

In the ProvAdminUI I used both
http://update.eclipse.org/eclipse/testUpdates and
http://download.eclipse.org/eclipse/testUpdates. (I believe they resolve to
the same place)

I also tried accessing the site.xml and content.jar in a web browser for
both URLs and it worked correctly. (the content.xml is obsolete and will
give you a 404)

You can also try putting the
"http://update.eclipse.org/eclipse/testUpdates" URL into a web browser and
it should be resolved to your local mirror and then try that in the UI.

I'm not sure about the caching thing...

                                                                           
             Timothy Webb                                                  
             <tim@...>                                              
             Sent by:                                                   To 
             equinox-dev-bounc         Equinox development mailing list    
             es@...           
<equinox-dev@...>           
                                                                        cc 

             02/01/2008 08:23                                      Subject 
             AM                        Re: [equinox-dev] p2 test repo      
                                       working?                            

             Please respond to                                             
                  Equinox                                                  
                development                                                
               mailing list                                                
             <equinox-dev <at> ecli                                             
                 pse.org>                                                  

Can you confirm what URL you are using to connect?  I receive 404
accessing the following URLs for a browser:

http://update.eclipse.org/eclipse/testUpdates/content.jar
http://update.eclipse.org/eclipse/testUpdates/content.xml
http://update.eclipse.org/eclipse/testUpdates/site.xml

Or is p2 caching what was the last known good configuration for these
sites?

Tim

On Feb 1, 2008, at 4:43 AM, DJ Houghton wrote:

> There must have been something temporarily wrong with the server
> because it
> seems to be corrected now... the content is there.

_______________________________________________
equinox-dev mailing list
equinox-dev@...
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Andrew Overholt | 1 Feb 14:58 2008
Picon

Re: p2 test repo working?

On Fri, 2008-02-01 at 08:36 -0500, DJ Houghton wrote:
> http://update.eclipse.org/eclipse/testUpdates and
> http://download.eclipse.org/eclipse/testUpdates. (I believe they resolve to
> the same place)

The download.eclipse.org URL is the only one that doesn't give me a 404.

Andrew


Gmane