[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Migrating your automated tests to use p2's /dropins/ folder


Cool, thanks for tracking it down that far. We'll look into it...

John




Ed Merks/Toronto/IBM@IBMCA
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

03/26/2008 05:32 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>, cross-project-issues-dev-bounces@xxxxxxxxxxx
Subject
Re: [cross-project-issues-dev] Migrating your        automated        tests        to        use        p2's /dropins/ folder





John,

I've reduced the problem I'm having to a single plugin and opened
https://bugs.eclipse.org/bugs/show_bug.cgi?id=224213.  For me this is a
blocker, I can't develop EMF without completing the bootstrap steps.  I
suspect that problem is simply that a lack of a version range is
interpretted the same as having specified 0.0.0.0 and is then failing to
find a match.

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %pluginName
Bundle-SymbolicName: org.eclipse.emf.common;singleton:=true
Bundle-Version: 2.4.0.qualifier
Bundle-ClassPath: common.jar
Bundle-Activator: org.eclipse.emf.common.CommonPlugin$Implementation
Bundle-Vendor: %providerName
Bundle-Localization: plugin
Bundle-RequiredExecutionEnvironment: J2SE-1.5
Export-Package: org.eclipse.emf.common,
org.eclipse.emf.common.archive,
org.eclipse.emf.common.command,
org.eclipse.emf.common.notify,
org.eclipse.emf.common.notify.impl,
org.eclipse.emf.common.util
Require-Bundle: org.eclipse.core.runtime
Eclipse-LazyStart: true
Bundle-ActivationPolicy: lazy



!SESSION 2008-03-26 17:13:11.500
-----------------------------------------------
eclipse.buildId=I20080325-2233
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32
j9vmwi3223-20060919 (JIT enabled)
J9VM - 20060915_08260_lHdSMR
JIT  - 20060908_1811_r8
GC   - 20060906_AA
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86 -consolelog -data
dropins/eclipse/plugins -clean

!ENTRY org.eclipse.equinox.p2.director 2 0 2008-03-26 17:13:15.718
!MESSAGE Problems resolving provisioning plan.
!SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-03-26 17:13:15.718
!MESSAGE No IU found to satisfy dependency of org.eclipse.emf.common
2.4.0.qualifier on req requiredCapability:
osgi.bundle/org.eclipse.core.runtime/0.0.0

!ENTRY org.eclipse.equinox.p2.director 2 0 2008-03-26 17:13:16.031
!MESSAGE Problems resolving provisioning plan.
!SUBENTRY 1 org.eclipse.equinox.p2.director 2 0 2008-03-26 17:13:16.031
!MESSAGE No IU found to satisfy dependency of org.eclipse.emf.common
2.4.0.qualifier req requiredCapability:
osgi.bundle/org.eclipse.core.runtime/0.0.0
!STACK 0
java.lang.IllegalStateException: No IU found to satisfy dependency of
org.eclipse.emf.common 2.4.0.qualifier req requiredCapability:
osgi.bundle/org.eclipse.core.runtime/0.0.0
     at
org.eclipse.equinox.internal.p2.director.Projector.expandRequirement(Projector.java:309)
     at
org.eclipse.equinox.internal.p2.director.Projector.processIU(Projector.java:218)
     at
org.eclipse.equinox.internal.p2.director.Projector.encode(Projector.java:81)
     at
org.eclipse.equinox.internal.p2.director.SimplePlanner.getProvisioningPlan(SimplePlanner.java:345)
     at
org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.createProvisioningPlan(ProfileSynchronizer.java:275)
     at
org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.synchronize(ProfileSynchronizer.java:80)
     at
org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.synchronize(Activator.java:143)
     at
org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Activator.java:113)
     at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009)
     at
java.security.AccessController.doPrivileged(AccessController.java:242)
     at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003)
     at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
     at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
     at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355)
     at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074)
     at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:632)
     at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:506)
     at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:280)
     at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:466)
     at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:209)
     at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:319)


I'll monitor the bugzilla and will immediately test whatever new version
comes out that fixes this problem.

Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265  (t/l 313)




                                                                         
            John                                                          
            Arthorne/Ottawa/I                                            
            BM@IBMCA                                                   To
            Sent by:                  Cross project issues                
            cross-project-iss         <cross-project-issues-dev@xxxxxxxxx
            ues-dev-bounces@e         rg>                                
            clipse.org                                                 cc
                                                                         
                                                                  Subject
            03/26/2008 05:21          Re: [cross-project-issues-dev]      
            PM                        Migrating your automated      tests
                                      to    use   p2's /dropins/ folder  
                                                                         
            Please respond to                                            
              Cross project                                              
                 issues                                                  
            <cross-project-is                                            
            sues-dev@eclipse.                                            
                  org>                                                    
                                                                         
                                                                         





Ed wrote on 03/26/2008 01:26:24 PM:

> This is really helpful!  The information about the dropins directory
> structure has been well-fleshed out and it looks like such nice flexible
> mechanism.   The instructions don't say anything about needing to take
> explicit action to actually install the plugins that you've dropped into
> the dropins folder.  Such an explicit step is required, right?

Just a restart. As mentioned in the wiki doc, the dropins folder is
reconciled on startup and newly discovered content is immediately
installed. Just like the plugins directory in Eclipse 3.3.

> I've been trying to bootstrap EMF following the steps in
> http://wiki.eclipse.org/EMF/Getting_Source but have so far been
> unsuccessful (using the 0324 build).

Yeah, the 0324 build was pretty badly broken. Amusingly, p2 itself is only
optionally part of the Eclipse SDK, and the p2 resolver optimized it out
during the build process (bug 223825). This was fixed in the 0325 build.
We're working on further improvements today to make p2 adoption even
easier, so there will likely be more updates tomorrow.

John _______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev