You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@tuscany.apache.org by Bryan Hunt <bh...@mac.com> on 2007/05/16 19:57:20 UTC

Re: sdo jars as eclipse plug-ins - problem solved - bad manifest

I've figured out the problem.  The generated MANIFEST.MF contains an  
invalid bundle version.

Changing

Bundle-Version: 1.0.incubating.SNAPSHOT

to

Bundle-Version: 1.0.0

fixes the problem.

Bryan

On May 16, 2007, at 11:12 AM, Bryan Hunt wrote:

> As I currently understand things, the sdo jars are built such they  
> can be used as OSGi bundles.  Is my understanding correct?
>
> I tried the following with a fresh download of Eclipse 3.3 M7:
>
> cp ~/.m2/repository/commonj/sdo-api-r2.1/1.0-incubating-SNAPSHOT/ 
> sdo-api-r2.1-1.0-incubating-SNAPSHOT.jar plugins/
> ./eclipse -clean
>
> Eclipse fails to start with the following log file:
>
> !SESSION 2007-05-16 11:05:44.227  
> -----------------------------------------------
> eclipse.buildId=I20070503-1400
> java.version=1.5.0_07
> java.vendor=Apple Computer, Inc.
> BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US
> Framework arguments:  -startup /Users/bhunt/Downloads/eclipse/ 
> Eclipse.app/Contents/MacOS/../../../plugins/ 
> org.eclipse.equinox.launcher_1.0.0.v20070502.jar
> Command-line arguments:  -os macosx -ws carbon -arch x86 -startup / 
> Users/bhunt/Downloads/eclipse/Eclipse.app/Contents/MacOS/../../../ 
> plugins/org.eclipse.equinox.launcher_1.0.0.v20070502.jar -clean
>
> !ENTRY org.eclipse.update.configurator 4 0 2007-05-16 11:05:46.407
> !MESSAGE
> !STACK 0
> org.osgi.framework.BundleException: Exception in  
> org.eclipse.update.internal.configurator.ConfigurationActivator.start( 
> ) of bundle org.eclipse.update.configurator.
>         at  
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiva 
> tor(BundleContextImpl.java:1018)
>         at  
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start 
> (BundleContextImpl.java:974)
>         at  
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker 
> (BundleHost.java:346)
>         at  
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume 
> (AbstractBundle.java:350)
>         at  
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle 
> (Framework.java:1118)
>         at  
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundl 
> es(StartLevelManager.java:634)
>         at  
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL 
> (StartLevelManager.java:508)
>         at  
> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartL 
> evel(StartLevelManager.java:282)
>         at  
> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEve 
> nt(StartLevelManager.java:468)
>         at  
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent 
> (EventManager.java:195)
>         at org.eclipse.osgi.framework.eventmgr.EventManager 
> $EventThread.run(EventManager.java:297)
> Caused by: org.eclipse.core.runtime.CoreException: Cannot create  
> configuration in file:/Users/bhunt/Downloads/eclipse/configuration/
>         at  
> org.eclipse.update.internal.configurator.Utils.newCoreException 
> (Utils.java:96)
>         at  
> org.eclipse.update.internal.configurator.ConfigurationActivator.initia 
> lize(ConfigurationActivator.java:111)
>         at  
> org.eclipse.update.internal.configurator.ConfigurationActivator.start( 
> ConfigurationActivator.java:69)
>         at  
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run 
> (BundleContextImpl.java:999)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at  
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiva 
> tor(BundleContextImpl.java:993)
>         ... 10 more
> Root exception:
> org.eclipse.core.runtime.CoreException: Cannot create configuration  
> in file:/Users/bhunt/Downloads/eclipse/configuration/
>         at  
> org.eclipse.update.internal.configurator.Utils.newCoreException 
> (Utils.java:96)
>         at  
> org.eclipse.update.internal.configurator.ConfigurationActivator.initia 
> lize(ConfigurationActivator.java:111)
>         at  
> org.eclipse.update.internal.configurator.ConfigurationActivator.start( 
> ConfigurationActivator.java:69)
>         at  
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run 
> (BundleContextImpl.java:999)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at  
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiva 
> tor(BundleContextImpl.java:993)
>         at  
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start 
> (BundleContextImpl.java:974)
>         at  
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker 
> (BundleHost.java:346)
>         at  
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume 
> (AbstractBundle.java:350)
>         at  
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle 
> (Framework.java:1118)
>         at  
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundl 
> es(StartLevelManager.java:634)
>         at  
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL 
> (StartLevelManager.java:508)
>         at  
> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartL 
> evel(StartLevelManager.java:282)
>         at  
> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEve 
> nt(StartLevelManager.java:468)
>         at  
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent 
> (EventManager.java:195)
>         at org.eclipse.osgi.framework.eventmgr.EventManager 
> $EventThread.run(EventManager.java:297)
>
> !ENTRY org.eclipse.core.runtime 4 0 2007-05-16 11:05:46.424
> !MESSAGE
> !STACK 0
> org.osgi.framework.BundleException: The bundle could not be  
> resolved. Reason: Missing Constraint: Require-Bundle:  
> org.eclipse.core.jobs; bundle-version="[3.2.0,4.0.0)"
>         at  
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker 
> (BundleHost.java:305)
>         at  
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume 
> (AbstractBundle.java:350)
>         at  
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle 
> (Framework.java:1118)
>         at  
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundl 
> es(StartLevelManager.java:634)
>         at  
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL 
> (StartLevelManager.java:508)
>         at  
> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartL 
> evel(StartLevelManager.java:282)
>         at  
> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEve 
> nt(StartLevelManager.java:468)
>         at  
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent 
> (EventManager.java:195)
>         at org.eclipse.osgi.framework.eventmgr.EventManager 
> $EventThread.run(EventManager.java:297)
>
> !ENTRY org.eclipse.osgi 4 0 2007-05-16 11:05:46.430
> !MESSAGE Bundle initial@reference:file:plugins/ 
> org.eclipse.update.configurator_3.2.100.v20070430.jar/ [2] is not  
> active.
>
> !ENTRY org.eclipse.osgi 4 0 2007-05-16 11:05:46.431
> !MESSAGE Bundle initial@reference:file:plugins/ 
> org.eclipse.core.runtime_3.3.100.v20070409.jar/ was not resolved.
>
> !ENTRY org.eclipse.osgi 4 0 2007-05-16 11:05:46.439
> !MESSAGE Application error
> !STACK 1
> java.lang.IllegalStateException: Unable to acquire application  
> service. Ensure that the org.eclipse.core.runtime bundle is  
> resolved and started (see config.ini).
>         at  
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start 
> (EclipseAppLauncher.java:72)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run 
> (EclipseStarter.java:363)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run 
> (EclipseStarter.java:176)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.eclipse.equinox.launcher.Main.invokeFramework 
> (Main.java:497)
>         at org.eclipse.equinox.launcher.Main.basicRun(Main.java:436)
>         at org.eclipse.equinox.launcher.Main.run(Main.java:1162)
>
> !ENTRY org.eclipse.osgi 2 0 2007-05-16 11:05:46.449
> !MESSAGE One or more bundles are not resolved because the following  
> root constraints are not resolved:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2007-05-16 11:05:46.450
> !MESSAGE Bundle initial@reference:file:plugins/ 
> org.eclipse.core.runtime_3.3.100.v20070409.jar/ was not resolved.
> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.450
> !MESSAGE Missing required bundle org.eclipse.equinox.app_ 
> [1.0.0,2.0.0).
> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.450
> !MESSAGE Missing required bundle org.eclipse.equinox.preferences_ 
> [3.2.0,4.0.0).
> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.450
> !MESSAGE Missing required bundle org.eclipse.core.contenttype_ 
> [3.2.0,4.0.0).
> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.451
> !MESSAGE Missing required bundle org.eclipse.core.jobs_[3.2.0,4.0.0).
> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.451
> !MESSAGE Missing required bundle org.eclipse.equinox.registry_ 
> [3.2.0,4.0.0).
>
> !ENTRY org.eclipse.osgi 2 0 2007-05-16 11:05:46.453
> !MESSAGE The following is a complete list of bundles which are not  
> resolved, see the prior log entry for the root cause if it exists:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2007-05-16 11:05:46.453
> !MESSAGE Bundle initial@reference:file:plugins/ 
> org.eclipse.core.runtime_3.3.100.v20070409.jar/ [3] was not resolved.
> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.453
> !MESSAGE Missing required bundle org.eclipse.core.jobs_[3.2.0,4.0.0).
> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.453
> !MESSAGE Missing required bundle org.eclipse.equinox.registry_ 
> [3.2.0,4.0.0).
> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.453
> !MESSAGE Missing required bundle org.eclipse.equinox.preferences_ 
> [3.2.0,4.0.0).
> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.454
> !MESSAGE Missing required bundle org.eclipse.core.contenttype_ 
> [3.2.0,4.0.0).
> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.454
> !MESSAGE Missing optionally required bundle  
> org.eclipse.core.runtime.compatibility.auth_[3.2.0,4.0.0).
> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.454
> !MESSAGE Missing required bundle org.eclipse.equinox.app_ 
> [1.0.0,2.0.0).
>

>

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org


Re: sdo jars as eclipse plug-ins - problem solved - bad manifest

Posted by Bryan Hunt <bh...@mac.com>.
Frank, I don't know a whole lot more than you, but yes, mvn is  
generating the MANIFEST.MF as specified in the pom.xml.  I originally  
made the change by hand, then figured out how to modify the pom.xml.

Here is the specification from the api pom.xml before my change:

             <plugin>
                 <groupId>org.apache.felix.plugins</groupId>
                 <artifactId>maven-osgi-plugin</artifactId>
                 <version>0.8.0-SNAPSHOT</version>
                 <extensions>true</extensions>
                 <configuration>
                     <osgiManifest>
                         <bundleName>${pom.name}</bundleName>
                         <bundleDescription>${pom.description}</ 
bundleDescription>
                         <bundleVendor>${pom.organization.name}</ 
bundleVendor>
                         <bundleLocalization>plugin</bundleLocalization>
                          
<bundleSymbolicName>org.apache.tuscany.sdo.spec</bundleSymbolicName>
                         <exportPackage>
                             commonj.sdo;version="${specVersion}",  
commonj.sdo.helper;version="${specVersion},
                             commonj.sdo.impl;version="${specVersion}"
                         </exportPackage>
                     </osgiManifest>
                 </configuration>
             </plugin>

Here is the specification with my change:

             <plugin>
                 <groupId>org.apache.felix.plugins</groupId>
                 <artifactId>maven-osgi-plugin</artifactId>
                 <version>0.8.0-SNAPSHOT</version>
                 <extensions>true</extensions>
                 <configuration>
                     <osgiManifest>
                         <bundleName>${pom.name}</bundleName>
                         <bundleDescription>${pom.description}</ 
bundleDescription>
                         <bundleVendor>${pom.organization.name}</ 
bundleVendor>
                         <bundleLocalization>plugin</bundleLocalization>
                         <bundleVersion>1.0.0</bundleVersion>
                          
<bundleSymbolicName>org.apache.tuscany.sdo.spec</bundleSymbolicName>
                         <exportPackage>
                             commonj.sdo;version="${specVersion}",  
commonj.sdo.helper;version="${specVersion},
                             commonj.sdo.impl;version="${specVersion}"
                         </exportPackage>
                     </osgiManifest>
                 </configuration>
             </plugin>

On May 16, 2007, at 1:08 PM, Frank Budinsky wrote:

> I don't know a lot about mvn or OSGi, but
> https://issues.apache.org/jira/browse/TUSCANY-1284 seems to imply  
> that the
> MANIFEST.MF file can be generated from the POM. Do I have it right?  
> Can
> anyone explain how it would all work? Where would the generated
> MANIFEST.MF file go?
>
> Thanks,
> Frank
>
> Bryan Hunt <bh...@mac.com> wrote on 05/16/2007 01:57:20 PM:
>
>> I've figured out the problem.  The generated MANIFEST.MF contains an
>> invalid bundle version.
>>
>> Changing
>>
>> Bundle-Version: 1.0.incubating.SNAPSHOT
>>
>> to
>>
>> Bundle-Version: 1.0.0
>>
>> fixes the problem.
>>
>> Bryan
>>
>> On May 16, 2007, at 11:12 AM, Bryan Hunt wrote:
>>
>>> As I currently understand things, the sdo jars are built such they
>>> can be used as OSGi bundles.  Is my understanding correct?
>>>
>>> I tried the following with a fresh download of Eclipse 3.3 M7:
>>>
>>> cp ~/.m2/repository/commonj/sdo-api-r2.1/1.0-incubating-SNAPSHOT/
>>> sdo-api-r2.1-1.0-incubating-SNAPSHOT.jar plugins/
>>> ./eclipse -clean
>>>
>>> Eclipse fails to start with the following log file:
>>>
>>> !SESSION 2007-05-16 11:05:44.227
>>> -----------------------------------------------
>>> eclipse.buildId=I20070503-1400
>>> java.version=1.5.0_07
>>> java.vendor=Apple Computer, Inc.
>>> BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US
>>> Framework arguments:  -startup /Users/bhunt/Downloads/eclipse/
>>> Eclipse.app/Contents/MacOS/../../../plugins/
>>> org.eclipse.equinox.launcher_1.0.0.v20070502.jar
>>> Command-line arguments:  -os macosx -ws carbon -arch x86 -startup /
>>> Users/bhunt/Downloads/eclipse/Eclipse.app/Contents/MacOS/../../../
>>> plugins/org.eclipse.equinox.launcher_1.0.0.v20070502.jar -clean
>>>
>>> !ENTRY org.eclipse.update.configurator 4 0 2007-05-16 11:05:46.407
>>> !MESSAGE
>>> !STACK 0
>>> org.osgi.framework.BundleException: Exception in
>>> org.eclipse.update.internal.configurator.ConfigurationActivator.star 
>>> t(
>
>>> ) of bundle org.eclipse.update.configurator.
>>>         at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActi 
>>> va
>
>>> tor(BundleContextImpl.java:1018)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start
>>> (BundleContextImpl.java:974)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker
>>> (BundleHost.java:346)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume
>>> (AbstractBundle.java:350)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle
>>> (Framework.java:1118)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBun 
>>> dl
>
>>> es(StartLevelManager.java:634)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL
>>> (StartLevelManager.java:508)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStar 
>>> tL
>
>>> evel(StartLevelManager.java:282)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchE 
>>> ve
>
>>> nt(StartLevelManager.java:468)
>>>         at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent
>>> (EventManager.java:195)
>>>         at org.eclipse.osgi.framework.eventmgr.EventManager
>>> $EventThread.run(EventManager.java:297)
>>> Caused by: org.eclipse.core.runtime.CoreException: Cannot create
>>> configuration in file:/Users/bhunt/Downloads/eclipse/configuration/
>>>         at
>>> org.eclipse.update.internal.configurator.Utils.newCoreException
>>> (Utils.java:96)
>>>         at
>>> org.eclipse.update.internal.configurator.ConfigurationActivator.init 
>>> ia
>
>>> lize(ConfigurationActivator.java:111)
>>>         at
>>> org.eclipse.update.internal.configurator.ConfigurationActivator.star 
>>> t(
>
>>> ConfigurationActivator.java:69)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run
>>> (BundleContextImpl.java:999)
>>>         at java.security.AccessController.doPrivileged(Native  
>>> Method)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActi 
>>> va
>
>>> tor(BundleContextImpl.java:993)
>>>         ... 10 more
>>> Root exception:
>>> org.eclipse.core.runtime.CoreException: Cannot create configuration
>>> in file:/Users/bhunt/Downloads/eclipse/configuration/
>>>         at
>>> org.eclipse.update.internal.configurator.Utils.newCoreException
>>> (Utils.java:96)
>>>         at
>>> org.eclipse.update.internal.configurator.ConfigurationActivator.init 
>>> ia
>
>>> lize(ConfigurationActivator.java:111)
>>>         at
>>> org.eclipse.update.internal.configurator.ConfigurationActivator.star 
>>> t(
>
>>> ConfigurationActivator.java:69)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run
>>> (BundleContextImpl.java:999)
>>>         at java.security.AccessController.doPrivileged(Native  
>>> Method)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActi 
>>> va
>
>>> tor(BundleContextImpl.java:993)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start
>>> (BundleContextImpl.java:974)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker
>>> (BundleHost.java:346)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume
>>> (AbstractBundle.java:350)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle
>>> (Framework.java:1118)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBun 
>>> dl
>
>>> es(StartLevelManager.java:634)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL
>>> (StartLevelManager.java:508)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStar 
>>> tL
>
>>> evel(StartLevelManager.java:282)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchE 
>>> ve
>
>>> nt(StartLevelManager.java:468)
>>>         at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent
>>> (EventManager.java:195)
>>>         at org.eclipse.osgi.framework.eventmgr.EventManager
>>> $EventThread.run(EventManager.java:297)
>>>
>>> !ENTRY org.eclipse.core.runtime 4 0 2007-05-16 11:05:46.424
>>> !MESSAGE
>>> !STACK 0
>>> org.osgi.framework.BundleException: The bundle could not be
>>> resolved. Reason: Missing Constraint: Require-Bundle:
>>> org.eclipse.core.jobs; bundle-version="[3.2.0,4.0.0)"
>>>         at
>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker
>>> (BundleHost.java:305)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume
>>> (AbstractBundle.java:350)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle
>>> (Framework.java:1118)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBun 
>>> dl
>
>>> es(StartLevelManager.java:634)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL
>>> (StartLevelManager.java:508)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStar 
>>> tL
>
>>> evel(StartLevelManager.java:282)
>>>         at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchE 
>>> ve
>
>>> nt(StartLevelManager.java:468)
>>>         at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent
>>> (EventManager.java:195)
>>>         at org.eclipse.osgi.framework.eventmgr.EventManager
>>> $EventThread.run(EventManager.java:297)
>>>
>>> !ENTRY org.eclipse.osgi 4 0 2007-05-16 11:05:46.430
>>> !MESSAGE Bundle initial@reference:file:plugins/
>>> org.eclipse.update.configurator_3.2.100.v20070430.jar/ [2] is not
>>> active.
>>>
>>> !ENTRY org.eclipse.osgi 4 0 2007-05-16 11:05:46.431
>>> !MESSAGE Bundle initial@reference:file:plugins/
>>> org.eclipse.core.runtime_3.3.100.v20070409.jar/ was not resolved.
>>>
>>> !ENTRY org.eclipse.osgi 4 0 2007-05-16 11:05:46.439
>>> !MESSAGE Application error
>>> !STACK 1
>>> java.lang.IllegalStateException: Unable to acquire application
>>> service. Ensure that the org.eclipse.core.runtime bundle is
>>> resolved and started (see config.ini).
>>>         at
>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start
>>> (EclipseAppLauncher.java:72)
>>>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run
>>> (EclipseStarter.java:363)
>>>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run
>>> (EclipseStarter.java:176)
>>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native  
>>> Method)
>>>         at sun.reflect.NativeMethodAccessorImpl.invoke
>>> (NativeMethodAccessorImpl.java:39)
>>>         at sun.reflect.DelegatingMethodAccessorImpl.invoke
>>> (DelegatingMethodAccessorImpl.java:25)
>>>         at java.lang.reflect.Method.invoke(Method.java:585)
>>>         at org.eclipse.equinox.launcher.Main.invokeFramework
>>> (Main.java:497)
>>>         at org.eclipse.equinox.launcher.Main.basicRun(Main.java:436)
>>>         at org.eclipse.equinox.launcher.Main.run(Main.java:1162)
>>>
>>> !ENTRY org.eclipse.osgi 2 0 2007-05-16 11:05:46.449
>>> !MESSAGE One or more bundles are not resolved because the following
>>> root constraints are not resolved:
>>> !SUBENTRY 1 org.eclipse.osgi 2 0 2007-05-16 11:05:46.450
>>> !MESSAGE Bundle initial@reference:file:plugins/
>>> org.eclipse.core.runtime_3.3.100.v20070409.jar/ was not resolved.
>>> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.450
>>> !MESSAGE Missing required bundle org.eclipse.equinox.app_
>>> [1.0.0,2.0.0).
>>> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.450
>>> !MESSAGE Missing required bundle org.eclipse.equinox.preferences_
>>> [3.2.0,4.0.0).
>>> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.450
>>> !MESSAGE Missing required bundle org.eclipse.core.contenttype_
>>> [3.2.0,4.0.0).
>>> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.451
>>> !MESSAGE Missing required bundle org.eclipse.core.jobs_ 
>>> [3.2.0,4.0.0).
>>> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.451
>>> !MESSAGE Missing required bundle org.eclipse.equinox.registry_
>>> [3.2.0,4.0.0).
>>>
>>> !ENTRY org.eclipse.osgi 2 0 2007-05-16 11:05:46.453
>>> !MESSAGE The following is a complete list of bundles which are not
>>> resolved, see the prior log entry for the root cause if it exists:
>>> !SUBENTRY 1 org.eclipse.osgi 2 0 2007-05-16 11:05:46.453
>>> !MESSAGE Bundle initial@reference:file:plugins/
>>> org.eclipse.core.runtime_3.3.100.v20070409.jar/ [3] was not  
>>> resolved.
>>> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.453
>>> !MESSAGE Missing required bundle org.eclipse.core.jobs_ 
>>> [3.2.0,4.0.0).
>>> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.453
>>> !MESSAGE Missing required bundle org.eclipse.equinox.registry_
>>> [3.2.0,4.0.0).
>>> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.453
>>> !MESSAGE Missing required bundle org.eclipse.equinox.preferences_
>>> [3.2.0,4.0.0).
>>> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.454
>>> !MESSAGE Missing required bundle org.eclipse.core.contenttype_
>>> [3.2.0,4.0.0).
>>> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.454
>>> !MESSAGE Missing optionally required bundle
>>> org.eclipse.core.runtime.compatibility.auth_[3.2.0,4.0.0).
>>> !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.454
>>> !MESSAGE Missing required bundle org.eclipse.equinox.app_
>>> [1.0.0,2.0.0).
>>>
>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org


Re: sdo jars as eclipse plug-ins - problem solved - bad manifest

Posted by Frank Budinsky <fr...@ca.ibm.com>.
I don't know a lot about mvn or OSGi, but 
https://issues.apache.org/jira/browse/TUSCANY-1284 seems to imply that the 
MANIFEST.MF file can be generated from the POM. Do I have it right? Can 
anyone explain how it would all work? Where would the generated 
MANIFEST.MF file go?

Thanks,
Frank

Bryan Hunt <bh...@mac.com> wrote on 05/16/2007 01:57:20 PM:

> I've figured out the problem.  The generated MANIFEST.MF contains an 
> invalid bundle version.
> 
> Changing
> 
> Bundle-Version: 1.0.incubating.SNAPSHOT
> 
> to
> 
> Bundle-Version: 1.0.0
> 
> fixes the problem.
> 
> Bryan
> 
> On May 16, 2007, at 11:12 AM, Bryan Hunt wrote:
> 
> > As I currently understand things, the sdo jars are built such they 
> > can be used as OSGi bundles.  Is my understanding correct?
> >
> > I tried the following with a fresh download of Eclipse 3.3 M7:
> >
> > cp ~/.m2/repository/commonj/sdo-api-r2.1/1.0-incubating-SNAPSHOT/ 
> > sdo-api-r2.1-1.0-incubating-SNAPSHOT.jar plugins/
> > ./eclipse -clean
> >
> > Eclipse fails to start with the following log file:
> >
> > !SESSION 2007-05-16 11:05:44.227 
> > -----------------------------------------------
> > eclipse.buildId=I20070503-1400
> > java.version=1.5.0_07
> > java.vendor=Apple Computer, Inc.
> > BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US
> > Framework arguments:  -startup /Users/bhunt/Downloads/eclipse/ 
> > Eclipse.app/Contents/MacOS/../../../plugins/ 
> > org.eclipse.equinox.launcher_1.0.0.v20070502.jar
> > Command-line arguments:  -os macosx -ws carbon -arch x86 -startup / 
> > Users/bhunt/Downloads/eclipse/Eclipse.app/Contents/MacOS/../../../ 
> > plugins/org.eclipse.equinox.launcher_1.0.0.v20070502.jar -clean
> >
> > !ENTRY org.eclipse.update.configurator 4 0 2007-05-16 11:05:46.407
> > !MESSAGE
> > !STACK 0
> > org.osgi.framework.BundleException: Exception in 
> > org.eclipse.update.internal.configurator.ConfigurationActivator.start( 

> > ) of bundle org.eclipse.update.configurator.
> >         at 
> > org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiva 

> > tor(BundleContextImpl.java:1018)
> >         at 
> > org.eclipse.osgi.framework.internal.core.BundleContextImpl.start 
> > (BundleContextImpl.java:974)
> >         at 
> > org.eclipse.osgi.framework.internal.core.BundleHost.startWorker 
> > (BundleHost.java:346)
> >         at 
> > org.eclipse.osgi.framework.internal.core.AbstractBundle.resume 
> > (AbstractBundle.java:350)
> >         at 
> > org.eclipse.osgi.framework.internal.core.Framework.resumeBundle 
> > (Framework.java:1118)
> >         at 
> > org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundl 

> > es(StartLevelManager.java:634)
> >         at 
> > org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL 
> > (StartLevelManager.java:508)
> >         at 
> > org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartL 

> > evel(StartLevelManager.java:282)
> >         at 
> > org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEve 

> > nt(StartLevelManager.java:468)
> >         at 
> > org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent 
> > (EventManager.java:195)
> >         at org.eclipse.osgi.framework.eventmgr.EventManager 
> > $EventThread.run(EventManager.java:297)
> > Caused by: org.eclipse.core.runtime.CoreException: Cannot create 
> > configuration in file:/Users/bhunt/Downloads/eclipse/configuration/
> >         at 
> > org.eclipse.update.internal.configurator.Utils.newCoreException 
> > (Utils.java:96)
> >         at 
> > org.eclipse.update.internal.configurator.ConfigurationActivator.initia 

> > lize(ConfigurationActivator.java:111)
> >         at 
> > org.eclipse.update.internal.configurator.ConfigurationActivator.start( 

> > ConfigurationActivator.java:69)
> >         at 
> > org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run 
> > (BundleContextImpl.java:999)
> >         at java.security.AccessController.doPrivileged(Native Method)
> >         at 
> > org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiva 

> > tor(BundleContextImpl.java:993)
> >         ... 10 more
> > Root exception:
> > org.eclipse.core.runtime.CoreException: Cannot create configuration 
> > in file:/Users/bhunt/Downloads/eclipse/configuration/
> >         at 
> > org.eclipse.update.internal.configurator.Utils.newCoreException 
> > (Utils.java:96)
> >         at 
> > org.eclipse.update.internal.configurator.ConfigurationActivator.initia 

> > lize(ConfigurationActivator.java:111)
> >         at 
> > org.eclipse.update.internal.configurator.ConfigurationActivator.start( 

> > ConfigurationActivator.java:69)
> >         at 
> > org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run 
> > (BundleContextImpl.java:999)
> >         at java.security.AccessController.doPrivileged(Native Method)
> >         at 
> > org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiva 

> > tor(BundleContextImpl.java:993)
> >         at 
> > org.eclipse.osgi.framework.internal.core.BundleContextImpl.start 
> > (BundleContextImpl.java:974)
> >         at 
> > org.eclipse.osgi.framework.internal.core.BundleHost.startWorker 
> > (BundleHost.java:346)
> >         at 
> > org.eclipse.osgi.framework.internal.core.AbstractBundle.resume 
> > (AbstractBundle.java:350)
> >         at 
> > org.eclipse.osgi.framework.internal.core.Framework.resumeBundle 
> > (Framework.java:1118)
> >         at 
> > org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundl 

> > es(StartLevelManager.java:634)
> >         at 
> > org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL 
> > (StartLevelManager.java:508)
> >         at 
> > org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartL 

> > evel(StartLevelManager.java:282)
> >         at 
> > org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEve 

> > nt(StartLevelManager.java:468)
> >         at 
> > org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent 
> > (EventManager.java:195)
> >         at org.eclipse.osgi.framework.eventmgr.EventManager 
> > $EventThread.run(EventManager.java:297)
> >
> > !ENTRY org.eclipse.core.runtime 4 0 2007-05-16 11:05:46.424
> > !MESSAGE
> > !STACK 0
> > org.osgi.framework.BundleException: The bundle could not be 
> > resolved. Reason: Missing Constraint: Require-Bundle: 
> > org.eclipse.core.jobs; bundle-version="[3.2.0,4.0.0)"
> >         at 
> > org.eclipse.osgi.framework.internal.core.BundleHost.startWorker 
> > (BundleHost.java:305)
> >         at 
> > org.eclipse.osgi.framework.internal.core.AbstractBundle.resume 
> > (AbstractBundle.java:350)
> >         at 
> > org.eclipse.osgi.framework.internal.core.Framework.resumeBundle 
> > (Framework.java:1118)
> >         at 
> > org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundl 

> > es(StartLevelManager.java:634)
> >         at 
> > org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL 
> > (StartLevelManager.java:508)
> >         at 
> > org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartL 

> > evel(StartLevelManager.java:282)
> >         at 
> > org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEve 

> > nt(StartLevelManager.java:468)
> >         at 
> > org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent 
> > (EventManager.java:195)
> >         at org.eclipse.osgi.framework.eventmgr.EventManager 
> > $EventThread.run(EventManager.java:297)
> >
> > !ENTRY org.eclipse.osgi 4 0 2007-05-16 11:05:46.430
> > !MESSAGE Bundle initial@reference:file:plugins/ 
> > org.eclipse.update.configurator_3.2.100.v20070430.jar/ [2] is not 
> > active.
> >
> > !ENTRY org.eclipse.osgi 4 0 2007-05-16 11:05:46.431
> > !MESSAGE Bundle initial@reference:file:plugins/ 
> > org.eclipse.core.runtime_3.3.100.v20070409.jar/ was not resolved.
> >
> > !ENTRY org.eclipse.osgi 4 0 2007-05-16 11:05:46.439
> > !MESSAGE Application error
> > !STACK 1
> > java.lang.IllegalStateException: Unable to acquire application 
> > service. Ensure that the org.eclipse.core.runtime bundle is 
> > resolved and started (see config.ini).
> >         at 
> > org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start 
> > (EclipseAppLauncher.java:72)
> >         at org.eclipse.core.runtime.adaptor.EclipseStarter.run 
> > (EclipseStarter.java:363)
> >         at org.eclipse.core.runtime.adaptor.EclipseStarter.run 
> > (EclipseStarter.java:176)
> >         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >         at sun.reflect.NativeMethodAccessorImpl.invoke 
> > (NativeMethodAccessorImpl.java:39)
> >         at sun.reflect.DelegatingMethodAccessorImpl.invoke 
> > (DelegatingMethodAccessorImpl.java:25)
> >         at java.lang.reflect.Method.invoke(Method.java:585)
> >         at org.eclipse.equinox.launcher.Main.invokeFramework 
> > (Main.java:497)
> >         at org.eclipse.equinox.launcher.Main.basicRun(Main.java:436)
> >         at org.eclipse.equinox.launcher.Main.run(Main.java:1162)
> >
> > !ENTRY org.eclipse.osgi 2 0 2007-05-16 11:05:46.449
> > !MESSAGE One or more bundles are not resolved because the following 
> > root constraints are not resolved:
> > !SUBENTRY 1 org.eclipse.osgi 2 0 2007-05-16 11:05:46.450
> > !MESSAGE Bundle initial@reference:file:plugins/ 
> > org.eclipse.core.runtime_3.3.100.v20070409.jar/ was not resolved.
> > !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.450
> > !MESSAGE Missing required bundle org.eclipse.equinox.app_ 
> > [1.0.0,2.0.0).
> > !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.450
> > !MESSAGE Missing required bundle org.eclipse.equinox.preferences_ 
> > [3.2.0,4.0.0).
> > !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.450
> > !MESSAGE Missing required bundle org.eclipse.core.contenttype_ 
> > [3.2.0,4.0.0).
> > !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.451
> > !MESSAGE Missing required bundle org.eclipse.core.jobs_[3.2.0,4.0.0).
> > !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.451
> > !MESSAGE Missing required bundle org.eclipse.equinox.registry_ 
> > [3.2.0,4.0.0).
> >
> > !ENTRY org.eclipse.osgi 2 0 2007-05-16 11:05:46.453
> > !MESSAGE The following is a complete list of bundles which are not 
> > resolved, see the prior log entry for the root cause if it exists:
> > !SUBENTRY 1 org.eclipse.osgi 2 0 2007-05-16 11:05:46.453
> > !MESSAGE Bundle initial@reference:file:plugins/ 
> > org.eclipse.core.runtime_3.3.100.v20070409.jar/ [3] was not resolved.
> > !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.453
> > !MESSAGE Missing required bundle org.eclipse.core.jobs_[3.2.0,4.0.0).
> > !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.453
> > !MESSAGE Missing required bundle org.eclipse.equinox.registry_ 
> > [3.2.0,4.0.0).
> > !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.453
> > !MESSAGE Missing required bundle org.eclipse.equinox.preferences_ 
> > [3.2.0,4.0.0).
> > !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.454
> > !MESSAGE Missing required bundle org.eclipse.core.contenttype_ 
> > [3.2.0,4.0.0).
> > !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.454
> > !MESSAGE Missing optionally required bundle 
> > org.eclipse.core.runtime.compatibility.auth_[3.2.0,4.0.0).
> > !SUBENTRY 2 org.eclipse.core.runtime 2 0 2007-05-16 11:05:46.454
> > !MESSAGE Missing required bundle org.eclipse.equinox.app_ 
> > [1.0.0,2.0.0).
> >
> 
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org