[equinox-dev] [prov] Comments on "Equinox Provisioning Engine" Wiki page
Simon thanks for adding the info to the wiki. I have a lot of questions and comments but will constrain myself to a few here. Once these are clarified I will attack the remainder. In the section "Engine processing model and phases" You list collect, validate, uninstall/unconfigure,... Is this the order that an operation is asked if it wants to participate in? The uninstall/unconfigure is not clear. I view these as separate phases. And unconfigure would come first. In general I don't know what is meant by the use of the '/' means. For the "We should move to a model where we pass a set of operations with internal operands." comment. Are we saying that we don't want to allow externally specifying the phase to stop on? It is not clear to me what we are proposing. Is it possible to add 1 or 2 sentence definitions to what is performed in each phase? I think that would open up the discussion.___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Launching with Foundation 1.1 VM
I am trying to run a simple Equinox-based product with J9 (Foundation 1.1 profile). Is there some trick to getting running with this setup? Here is the command line that allows me to make the most progress: eclipse -product org.eclipse.prov.client.installer.product -debug -vm jre\bin\j9.exe -vmargs -jcl:ppro11 -Dorg.osgi.framework.executionenvironment="OSGi/Minimum-1.0,OSGi/Minimum-1.1,CDC-1.0/Foundation-1.0,CDC-1.1/Foundation-1.1" With this command line, I get various errors in the log, starting with: !ENTRY org.eclipse.equinox.app 4 0 2007-09-06 12:17:51.968 !MESSAGE !STACK 0 org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.equinox.registry; 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.resumeBundles(StartLevelManager.java:634) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:209) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:319) I have tried invoking the VM directly rather than using eclipse.exe, but get the same result. The same launch runs fine with a 1.4 or Java 5 VM. Ideas?___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Launching with Foundation 1.1 VM
Can you run with -noExit -console and see if the org.eclipse.equinox.registry bundle is installed and resolved. If it is not resolved then run the 'diag' command to see why the registry bundle is not resolved. Tom John Arthorne <[EMAIL PROTECTED] .ibm.com> To Sent by: equinox-dev@eclipse.org equinox-dev-bounc cc [EMAIL PROTECTED] Subject [equinox-dev] Launching with 09/06/2007 11:21 Foundation 1.1 VM AM Please respond to Equinox development mailing list <[EMAIL PROTECTED] pse.org> I am trying to run a simple Equinox-based product with J9 (Foundation 1.1 profile). Is there some trick to getting running with this setup? Here is the command line that allows me to make the most progress: eclipse -product org.eclipse.prov.client.installer.product -debug -vm jre\bin\j9.exe -vmargs -jcl:ppro11 -Dorg.osgi.framework.executionenvironment="OSGi/Minimum-1.0,OSGi/Minimum-1.1,CDC-1.0 /Foundation-1.0,CDC-1.1/Foundation-1.1" With this command line, I get various errors in the log, starting with: !ENTRY org.eclipse.equinox.app 4 0 2007-09-06 12:17:51.968 !MESSAGE !STACK 0 org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.equinox.registry; 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.resumeBundles(StartLevelManager.java:634) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:209) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:319) I have tried invoking the VM directly rather than using eclipse.exe, but get the same result. The same launch runs fine with a 1.4 or Java 5 VM. Ideas?___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev <><><>___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Launching with Foundation 1.1 VM
Thanks Tom. Registry is not resolved because it requires a SAX parser. I tried org.apache.xerces from orbit, but it requires a 1.2 EE. Does anyone know of a SAX parser that will run in Foundation 1.1? Thomas Watson <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 09/06/2007 12:47 PM Please respond to Equinox development mailing list To Equinox development mailing list cc Subject Re: [equinox-dev] Launching with Foundation 1.1 VM Can you run with -noExit -console and see if the org.eclipse.equinox.registry bundle is installed and resolved. If it is not resolved then run the 'diag' command to see why the registry bundle is not resolved. Tom John Arthorne ---09/06/2007 11:22:26 AM---I am trying to run a simple Equinox-based product with J9 (Foundation 1.1 profile). Is there some trick to getting running with John Arthorne <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 09/06/2007 11:21 AM Please respond to Equinox development mailing list To equinox-dev@eclipse.org cc Subject [equinox-dev] Launching with Foundation 1.1 VM I am trying to run a simple Equinox-based product with J9 (Foundation 1.1 profile). Is there some trick to getting running with this setup? Here is the command line that allows me to make the most progress: eclipse -product org.eclipse.prov.client.installer.product -debug -vm jre\bin\j9.exe -vmargs -jcl:ppro11 -Dorg.osgi.framework.executionenvironment="OSGi/Minimum-1.0,OSGi/Minimum-1.1,CDC-1.0/Foundation-1.0,CDC-1.1/Foundation-1.1" With this command line, I get various errors in the log, starting with: !ENTRY org.eclipse.equinox.app 4 0 2007-09-06 12:17:51.968 !MESSAGE !STACK 0 org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.equinox.registry; 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.resumeBundles(StartLevelManager.java:634) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:209) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:319) I have tried invoking the VM directly rather than using eclipse.exe, but get the same result. The same launch runs fine with a 1.4 or Java 5 VM. Ideas?___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev <><><><><><><><><><>___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Launching with Foundation 1.1 VM
The eRCP project has a XML parser they use. I believe they install them as framework extensions. See http://www.eclipse.org/downloads/download.php?file=/dsdp/ercp/eRCP-v20070801.win32-x86.zip It includes two xml bundles (org.eclipse.ercp.xml and org.eclipse.ercp.xmlParserAPIs). These two bundles are configured as framework extensions with the following config.ini property in eRCP. osgi.framework.extensions=org.eclipse.ercp.xml, org.eclipse.ercp.xmlParserAPIs The reason they use them as framework extensions is so they can support plugin.xml parsing for compatibility and more importantly to take advantage of the framework code which registers the xml parsers as OSGi services. Tom John Arthorne <[EMAIL PROTECTED] .ibm.com> To Sent by: Equinox development mailing list equinox-dev-bounc [EMAIL PROTECTED] cc Subject 09/06/2007 12:08 Re: [equinox-dev] Launching with PMFoundation 1.1 VM Please respond to Equinox development mailing list <[EMAIL PROTECTED] pse.org> Thanks Tom. Registry is not resolved because it requires a SAX parser. I tried org.apache.xerces from orbit, but it requires a 1.2 EE. Does anyone know of a SAX parser that will run in Foundation 1.1? Thomas Watson <[EMAIL PROTECTED]> Sent by: To [EMAIL PROTECTED]Equinox development mailing list cc 09/06/2007 12:47 PM Subject Re: [equinox-dev] Launching Please respond to with Foundation 1.1 VM Equinox development mailing list Can you run with -noExit -console and see if the org.eclipse.equinox.registry bundle is installed and resolved. If it is not resolved then run the 'diag' command to see why the registry bundle is not resolved. Tom Inactive hide details for John Arthorne ---09/06/2007 11:22:26 AM---I am trying to run a simple Equinox-based product with J9 (John Arthorne ---09 /06/2007 11:22:26 AM---I am trying to run a simple Equinox-based product with J9 (Foundation 1.1 profile). Is there some trick to getting running with John Arthorne <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] To 09/06/2007 11:21 AM equinox-dev@eclipse.org Please respond to Equinox development mailing list
Re: [equinox-dev] Launching with Foundation 1.1 VM
I used the XML bundles from eRCP (http://www.eclipse.org/ercp/). Note that you will also have to set the following system property: osgi.framework.extensions=org.eclipse.ercp.xmlParserAPIs,org.eclipse.ercp.xml John Arthorne/Ottawa/I [EMAIL PROTECTED] To Sent by: Equinox development mailing list equinox-dev-bounc [EMAIL PROTECTED] cc Subject 09/06/2007 01:08 Re: [equinox-dev] Launching with PMFoundation 1.1 VM Please respond to Equinox development mailing list <[EMAIL PROTECTED] pse.org> Thanks Tom. Registry is not resolved because it requires a SAX parser. I tried org.apache.xerces from orbit, but it requires a 1.2 EE. Does anyone know of a SAX parser that will run in Foundation 1.1? Thomas Watson <[EMAIL PROTECTED]> Sent by: To [EMAIL PROTECTED]Equinox development mailing list cc 09/06/2007 12:47 PM Subject Re: [equinox-dev] Launching Please respond to with Foundation 1.1 VM Equinox development mailing list Can you run with -noExit -console and see if the org.eclipse.equinox.registry bundle is installed and resolved. If it is not resolved then run the 'diag' command to see why the registry bundle is not resolved. Tom (Embedded image moved to file: pic16843.gif)Inactive hide details for John Arthorne ---09/06/2007 11:22:26 AM---I am trying to run a simple Equinox-based product with J9 (John Arthorne ---09/06/2007 11:22:26 AM---I am trying to run a simple Equinox-based product with J9 (Foundation 1.1 profile). Is there some trick to getting running with John Arthorne <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED](Embedded image moved to file: pic14311.gif) 09/06/2007 11:21 AMTo (Embedded image moved to file: pic25857.gif) Please respond toequinox-dev@eclipse.org Equinox development mailing list(Embedded image moved to file: pic29694.gif) cc
Re: [equinox-dev] Launching with Foundation 1.1 VM
As an aside, find attached an example .ee file that can be used to start the J9 vm in-process using JNI instead of forking a process with j9.exe. Starting eclipse with -vm foundation11.ee will add all arguments found in the .ee file to the vmargs list. -Andrew Thomas Watson <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 09/06/2007 12:47 PM Please respond to Equinox development mailing list To Equinox development mailing list cc Subject Re: [equinox-dev] Launching with Foundation 1.1 VM Can you run with -noExit -console and see if the org.eclipse.equinox.registry bundle is installed and resolved. If it is not resolved then run the 'diag' command to see why the registry bundle is not resolved. Tom John Arthorne ---09/06/2007 11:22:26 AM---I am trying to run a simple Equinox-based product with J9 (Foundation 1.1 profile). Is there some trick to getting running with John Arthorne <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 09/06/2007 11:21 AM Please respond to Equinox development mailing list To equinox-dev@eclipse.org cc Subject [equinox-dev] Launching with Foundation 1.1 VM I am trying to run a simple Equinox-based product with J9 (Foundation 1.1 profile). Is there some trick to getting running with this setup? Here is the command line that allows me to make the most progress: eclipse -product org.eclipse.prov.client.installer.product -debug -vm jre\bin\j9.exe -vmargs -jcl:ppro11 -Dorg.osgi.framework.executionenvironment="OSGi/Minimum-1.0,OSGi/Minimum-1.1,CDC-1.0/Foundation-1.0,CDC-1.1/Foundation-1.1" With this command line, I get various errors in the log, starting with: !ENTRY org.eclipse.equinox.app 4 0 2007-09-06 12:17:51.968 !MESSAGE !STACK 0 org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.equinox.registry; 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.resumeBundles(StartLevelManager.java:634) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:209) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:319) I have tried invoking the VM directly rather than using eclipse.exe, but get the same result. The same launch runs fine with a 1.4 or Java 5 VM. Ideas?___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev <><><><><><><><><><> foundation11.ee Description: Binary data ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] [prov] - internal error "updating metadata"
Is anyone else seeing these errors in their working IDE? For example, I just got this error while syncing with the repository. An internal error occurred during: "Updating metadata". java.lang.NegativeArraySizeException I believe this is a self hosting issue (keeping metadata up to date with the workspace), but thought I better post just to make sure. When we get these errors, should we be cleaning out the metadata generated for a self hosting launch, and if so, exactly what needs to be deleted? thanks, susan___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [prov] directory watcher
You are correct, the project preferences themselves are stored in /.settings/.prefs. But I don't know how the UI determines if they should be used. In a perfect world everyone would go through the preference service with the default lookup order (project being one of them) and then they would just be discovered. From your experience though, it seems that this is not the case. dj Jeff McAffer/Ottawa/IB [EMAIL PROTECTED] To Sent by: Equinox development mailing list equinox-dev-bounc [EMAIL PROTECTED] cc Subject 08/30/2007 05:27 Re: [equinox-dev] [prov] directory PMwatcher Please respond to Equinox development mailing list <[EMAIL PROTECTED] pse.org> Interesting. So it might be that the coding practice project setup instructions need to be tweaked. I worked with Tom last night to clean things up and setup templates for both the JDT Core and UI related preferences. The assumptoin on my part was that if these pref files were simply copied into the project that they would take effect for that project. Perhaps there is something missing? I wonder where the "project specific settings" setting is stored. Perhaps DJ "preference man" Houghton knows? Anyone else? Jeff Pascal Rapicault/Ottawa/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED]To Equinox development mailing list 08/30/2007 02:36 PMcc Subject Please respond to Re: [equinox-dev] [prov] Equinox development mailing list directory watcher The problem in the preferences, not in the code. If you look at the project preferences, you will notice that under "java code style" > "organize imports" the project specific settings are not enabled. I will fix it. It feels like we are missing a provisioning solution for preferences :-) PaScaL |> | From: | |> >--| |Jeff McAffer/Ottawa/[EMAIL PROTECTED] | >--| |> | To:| |> >--| |Equinox development mailing list | >--| |> | Date: | |> >
Re: [equinox-dev] [prov] - internal error "updating metadata"
You are right, this is caused by the selfhosting bundle trying to react (poorly) to workspace changes... Once this occured it is likely that the metadata repo and artifact repo representing your workspace and target platform contain stale content. You can recover from this state by: - going to the console and stopping the selfhosting bundle - going in /.metadata/.plugins/ and deleting the org.eclipse.equinox.prov.selfhosting folder - going to the console and starting the selfhosting bundle From: Susan M Franklin <[EMAIL PROTECTED]> To: equinox-dev@eclipse.org Date: 09/06/2007 01:59 PM Subject:[equinox-dev] [prov] - internal error "updating metadata" Is anyone else seeing these errors in their working IDE? For example, I just got this error while syncing with the repository. An internal error occurred during: "Updating metadata". java.lang.NegativeArraySizeException I believe this is a self hosting issue (keeping metadata up to date with the workspace), but thought I better post just to make sure. When we get these errors, should we be cleaning out the metadata generated for a self hosting launch, and if so, exactly what needs to be deleted? thanks, susan___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [prov] directory watcher
ok. Can someone (DJ?) take a stab at figuring out exactly how this should work? We have two settings template file that people can put in the project but we need to figure out how this gets hooked in etc. Jeff DJ Houghton/Ottawa/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09/06/2007 02:14 PM Please respond to Equinox development mailing list To Equinox development mailing list cc Subject Re: [equinox-dev] [prov] directory watcher You are correct, the project preferences themselves are stored in /.settings/.prefs. But I don't know how the UI determines if they should be used. In a perfect world everyone would go through the preference service with the default lookup order (project being one of them) and then they would just be discovered. From your experience though, it seems that this is not the case. dj Jeff McAffer/Ottawa/IB [EMAIL PROTECTED] To Sent by: Equinox development mailing list equinox-dev-bounc [EMAIL PROTECTED] cc Subject 08/30/2007 05:27 Re: [equinox-dev] [prov] directory PMwatcher Please respond to Equinox development mailing list <[EMAIL PROTECTED] pse.org> Interesting. So it might be that the coding practice project setup instructions need to be tweaked. I worked with Tom last night to clean things up and setup templates for both the JDT Core and UI related preferences. The assumptoin on my part was that if these pref files were simply copied into the project that they would take effect for that project. Perhaps there is something missing? I wonder where the "project specific settings" setting is stored. Perhaps DJ "preference man" Houghton knows? Anyone else? Jeff Pascal Rapicault/Ottawa/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED]To Equinox development mailing list 08/30/2007 02:36 PMcc Subject Please respond to Re: [equinox-dev] [prov] Equinox development mailing list directory watcher The problem in the preferences, not in the code. If you look at the project preferences, you will notice that under "java code style" > "organize imports" the project specific settings are not enabled. I will fix it. It feels like we are missing a provisioning solution for preferences :-) PaScaL |> | From: | |> >--| |Jeff McAffer/Ottawa/[EMAIL PROTECTED] | >--| |> | To:| |> >--| |Equinox development mailing list | >--| |> | Date: | |> >--| |08/30/2007 02:30 PM | >--| |> | Subject: | |> >--| |Re: [equinox-dev] [prov] directory watcher | >--| can you point out a precise problem? I had used an older version of the JDT UI prefs template (I've now updated the project) but organizing imports on the code did not change anything (ie.., they were properly organized). Jeff Pascal Rapicault/Ottawa/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED]To Equinox development mailing list 08/30/200
Re: [equinox-dev] Launching with Foundation 1.1 VM
Tom, Thanks for handing out the info on eRCP. John, I'm afraid that you will probably find that SWT has some dependencies outside of Foundation 1.1. JFace certainly does. It may be possible for you to choose widgets that don't have dependencies, though. Things could get dicey doing this since unless you build SWT against Foundation 1.1 you won't know where the issues are. I suggest you try using eRCP as it is a project specifically developed to work on Foundation 1.0. Mark Thomas Watson/Austin/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09/06/2007 12:19 PM Please respond to Equinox development mailing list To Equinox development mailing list cc Subject Re: [equinox-dev] Launching with Foundation 1.1 VM The eRCP project has a XML parser they use. I believe they install them as framework extensions. See http://www.eclipse.org/downloads/download.php?file=/dsdp/ercp/eRCP-v20070801.win32-x86.zip It includes two xml bundles (org.eclipse.ercp.xml and org.eclipse.ercp.xmlParserAPIs). These two bundles are configured as framework extensions with the following config.ini property in eRCP. osgi.framework.extensions=org.eclipse.ercp.xml, org.eclipse.ercp.xmlParserAPIs The reason they use them as framework extensions is so they can support plugin.xml parsing for compatibility and more importantly to take advantage of the framework code which registers the xml parsers as OSGi services. Tom John Arthorne ---09/06/2007 12:08:59 PM---Thanks Tom. Registry is not resolved because it requires a SAX parser. I tried org.apache.xerces from orbit, but it requires John Arthorne <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 09/06/2007 12:08 PM Please respond to Equinox development mailing list To Equinox development mailing list cc Subject Re: [equinox-dev] Launching with Foundation 1.1 VM Thanks Tom. Registry is not resolved because it requires a SAX parser. I tried org.apache.xerces from orbit, but it requires a 1.2 EE. Does anyone know of a SAX parser that will run in Foundation 1.1? Thomas Watson <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 09/06/2007 12:47 PM Please respond to Equinox development mailing list To Equinox development mailing list cc Subject Re: [equinox-dev] Launching with Foundation 1.1 VM Can you run with -noExit -console and see if the org.eclipse.equinox.registry bundle is installed and resolved. If it is not resolved then run the 'diag' command to see why the registry bundle is not resolved. Tom John Arthorne ---09/06/2007 11:22:26 AM---I am trying to run a simple Equinox-based product with J9 (Foundation 1.1 profile). Is there some trick to getting running with John Arthorne <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 09/06/2007 11:21 AM Please respond to Equinox development mailing list To equinox-dev@eclipse.org cc Subject [equinox-dev] Launching with Foundation 1.1 VM I am trying to run a simple Equinox-based product with J9 (Foundation 1.1 profile). Is there some trick to getting running with this setup? Here is the command line that allows me to make the most progress: eclipse -product org.eclipse.prov.client.installer.product -debug -vm jre\bin\j9.exe -vmargs -jcl:ppro11 -Dorg.osgi.framework.executionenvironment="OSGi/Minimum-1.0,OSGi/Minimum-1.1,CDC-1.0/Foundation-1.0,CDC-1.1/Foundation-1.1" With this command line, I get various errors in the log, starting with: !ENTRY org.eclipse.equinox.app 4 0 2007-09-06 12:17:51.968 !MESSAGE !STACK 0 org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.equinox.registry; 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.resumeBundles(StartLevelManager.java:634) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:209) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:319) I have tried invoking the VM directly rather than using eclipse.exe, but get the same result. The same launch runs fine with a 1.4 or Java 5 VM. Ideas?___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-
