Re: [equinox-dev] debug ouptut with new resolver

[Thomas Watson <tjwatson@xxxxxxxxxx>]

A new build has been published that
addresses some of Jeff's concerns.  Please see http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/equinox-home/downloads.html
for details.  

The preferred way to get the equinox
build is to use Eclipse 3.1 M3 and then use the equinox layering update
site at http://download.eclipse.org/technology/equinox/update-site/.  Update
will ensure that the platform is updated correctly and will disable the
old 3.1 plugins that the equinox build replaces.  Please respond to
this mailing list with any questions or comments.

Thanks.

Tom

Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>
Sent by: equinox-dev-admin@xxxxxxxxxxx

11/16/2004 09:18 PM

Please respond to
equinox-dev

To	equinox-dev@xxxxxxxxxxx
cc
Subject	[equinox-dev] debug ouptut with new resolver

I got the equinox download and unziped it over m3.  When I run I get
reams of debug/scary looking output in the console.  Below is a random
sampling.  Some comments: 

- this sort of output should only be given when asked for.  Users
are generally freaked out but spew.  I did have -debug on and the
org.eclipse.core.runtime/debug=true flag set but that should not trigger
this level of output. 

- there was alot (alot) of output the first time I ran (with -clean)

- there was some more output when I *exited* from that first run.  This
surprised me since I did not expect any resolver activity at that time.

- a reduced (though still considerable) spew was had when I ran the *second*
time (without -clean and after a successful run).  This is quite unexpected.
 The second run should not involve any resolution or other "work"

- running a third time (after two successful runs) yielded a still smaller
amount of spew.  This may have been related to PDE's use of the resolver
as some of the bundles mentioned in the ouptut were definitely only in
the workspace.   

- Curious that the output should be different on the third run. I would
have expected things to have settled down. 

- I thought that PDE was caching its info 

- it would be good to distinguish between the framework uses of the resolver
and other (PDE) uses.  In the past users have found that the errors
logged as a result of ill-configured workspaces to be quite distracting
as they appeared to be related to their dev environment.  I seem to
remember that we did something like mark them as coming from PDE or some
such. 

Jeff 

=========== sample output ============== 

!ENTRY org.eclipse.osgi 2004-11-16 21:50:06.355 
!MESSAGE Bundle update@/d:/3.1m3/eclipse/plugins/org.eclipse.core.runtime.compatibility_3.0.0/
[14] was not resolved. 
!SUBENTRY 1 org.eclipse.osgi 2004-11-16 21:50:06.355
!MESSAGE Bundle <null> was picked instead. 

!ENTRY org.eclipse.osgi 2004-11-16 21:50:06.395 
!MESSAGE Bundle update@/d:/3.1m3/eclipse/plugins/org.eclipse.core.runtime_3.1.0/
[16] was not resolved. 
!SUBENTRY 1 org.eclipse.osgi 2004-11-16 21:50:06.395
!MESSAGE Bundle <null> was picked instead. 

!ENTRY org.eclipse.osgi 2004-11-16 21:50:06.415 
!MESSAGE Bundle update@/d:/3.1m3/eclipse/plugins/org.eclipse.osgi_3.1.0/
[44] was not resolved. 
!SUBENTRY 1 org.eclipse.osgi 2004-11-16 21:50:06.415
!MESSAGE Bundle <null> was picked instead. 

!ENTRY org.eclipse.osgi 2004-11-16 21:50:06.425 
!MESSAGE Bundle update@/d:/3.1m3/eclipse/plugins/org.eclipse.pde.core_3.1.0/
[48] was not resolved. 
!SUBENTRY 1 org.eclipse.osgi 2004-11-16 21:50:06.425
!MESSAGE Bundle <null> was picked instead. 

!ENTRY org.eclipse.osgi 2004-11-16 21:50:06.425 
!MESSAGE Bundle update@/d:/3.1m3/eclipse/plugins/org.eclipse.update.core_3.0.0/
[89] was not resolved. 
!SUBENTRY 1 org.eclipse.osgi 2004-11-16 21:50:06.425
!MESSAGE Bundle <null> was picked instead. 
Starting application: 2063 
*** BEGIN *** 
** RESOLVING [org.eclipse.core.expressions_3.1.0] **
Trying to resolve: [org.eclipse.core.expressions_3.1.0], Require-Bundle:
org.eclipse.core.runtime - version: 0.0.0 
CHECKING: org.eclipse.core.runtime_3.1.0 
Trying to resolve: [org.eclipse.core.runtime_3.1.0], Require-Bundle: org.eclipse.osgi
- version: 0.0.0 
CHECKING: org.eclipse.osgi_3.1.0 
Trying to resolve: [org.eclipse.osgi_3.1.0], org.osgi.util.tracker
CHECKING: org.eclipse.osgi_3.1.0, org.osgi.util.tracker
Trying to resolve: [org.eclipse.osgi_3.1.0], org.osgi.framework
CHECKING: org.eclipse.osgi_3.1.0, org.osgi.framework
Trying to resolve: [org.eclipse.osgi_3.1.0], org.osgi.service.packageadmin
CHECKING: org.eclipse.osgi_3.1.0, org.osgi.service.packageadmin
Trying to resolve: [org.eclipse.osgi_3.1.0], org.osgi.service.permissionadmin
CHECKING: org.eclipse.osgi_3.1.0, org.osgi.service.permissionadmin
Trying to resolve: [org.eclipse.osgi_3.1.0], org.osgi.service.url
CHECKING: org.eclipse.osgi_3.1.0, org.osgi.service.url
Trying to resolve: [org.eclipse.osgi_3.1.0], org.osgi.service.startlevel
CHECKING: org.eclipse.osgi_3.1.0, org.osgi.service.startlevel
Trying to resolve: [org.eclipse.osgi_3.1.0], org.eclipse.osgi.framework.eventmgr
CHECKING: org.eclipse.osgi_3.1.0, org.eclipse.osgi.framework.eventmgr
Trying to resolve: [org.eclipse.osgi_3.1.0], org.eclipse.osgi.framework.msg
CHECKING: org.eclipse.osgi_3.1.0, org.eclipse.osgi.framework.msg
Trying to resolve: [org.eclipse.osgi_3.1.0], org.eclipse.osgi.service.debug
CHECKING: org.eclipse.osgi_3.1.0, org.eclipse.osgi.service.debug
Trying to resolve: [org.eclipse.osgi_3.1.0], org.eclipse.osgi.service.resolver
CHECKING: org.eclipse.osgi_3.1.0, org.eclipse.osgi.service.resolver
Trying to resolve: [org.eclipse.osgi_3.1.0], org.eclipse.osgi.service.systembundle
CHECKING: org.eclipse.osgi_3.1.0, org.eclipse.osgi.service.systembundle
Trying to resolve: [org.eclipse.osgi_3.1.0], org.eclipse.osgi.util
CHECKING: org.eclipse.osgi_3.1.0, org.eclipse.osgi.util
[org.eclipse.osgi_3.1.0] RESOLVED 
Found match: org.eclipse.osgi_3.1.0. Wiring 
Trying to resolve: [org.eclipse.core.runtime_3.1.0], org.osgi.service.prefs
CHECKING: org.eclipse.core.runtime_3.1.0, org.osgi.service.prefs
Trying to resolve: [org.eclipse.core.runtime_3.1.0], org.eclipse.core.runtime.preferences
CHECKING: org.eclipse.core.runtime_3.1.0, org.eclipse.core.runtime.preferences
[org.eclipse.core.runtime_3.1.0] RESOLVED 
Found match: org.eclipse.core.runtime_3.1.0. Wiring
[org.eclipse.core.expressions_3.1.0] RESOLVED 
** RESOLVING [org.eclipse.core.runtime_3.1.0] ** 
  - [org.eclipse.core.runtime_3.1.0] already resolved
** RESOLVING [org.eclipse.help_3.0.0] ** 
Trying to resolve: [org.eclipse.help_3.0.0], Require-Bundle: org.eclipse.core.runtime
- version: 0.0.0 
CHECKING: org.eclipse.core.runtime_3.1.0 
Found match: org.eclipse.core.runtime_3.1.0. Wiring
[org.eclipse.help_3.0.0] RESOLVED 
** RESOLVING [org.eclipse.jface_3.1.0] ** 
Trying to resolve: [org.eclipse.jface_3.1.0], Require-Bundle: org.eclipse.swt
- version: 0.0.0 
CHECKING: org.eclipse.swt_3.1.0 
[org.eclipse.swt_3.1.0] RESOLVED 
Found match: org.eclipse.swt_3.1.0. Wiring 
Trying to resolve: [org.eclipse.jface_3.1.0], Require-Bundle: org.eclipse.core.runtime
- version: 0.0.0 
CHECKING: org.eclipse.core.runtime_3.1.0 
Found match: org.eclipse.core.runtime_3.1.0. Wiring
[org.eclipse.jface_3.1.0] RESOLVED 
** RESOLVING [org.eclipse.osgi_3.1.0] ** 
  - [org.eclipse.osgi_3.1.0] already resolved