Re: error in 0.8.0 in incubator (shellui hang in svn)
Richard, thanks for the quick response. I will update from the trunk, rebuild and give it a try. Yes, I also got error messages indicating it could not find the bundles--which I thought was because of the location where I was starting it from. I'm reading right now and going throught the tutorials to bring myself up to speed. Thanks, again. Brian On 4/13/07, Richard S. Hall <[EMAIL PROTECTED]> wrote: Brian, FYI, I just submitted a patch to Main.java that fixed how we calculate the parent directory of felix.jar, which is how we locate the conf/config.properties file. Your comment below about not being able to start from the bin/ directory made me think there was a problem and there was. The method File.getParent() was not returning what I expected, it was actually returning null for relative paths, not the actual parent directory. So, I modified this to use getAbsolutePath() to really get the parent directory. Now you can run Felix from bin (and hopefully any other directory) and it will find conf/config.properties. However! The config.properties file itself DOES expect to be run from the installation directory (or the main directory if using source builds), not from bin/. The config.properties file uses relative paths for auto-starting the shell bundles, so for these relative paths to work, you must do "java -jar bin/felix.jar"...this is just a simplification that allows us to run easily no matter where the files are installed or if you move the felix directory. If you really want Felix to be able to start from any directory, then you must edit the config.properties file to have absolute path names pointing to your shell bundles. -> richard Brian Bonner wrote: > I compared the config.properties to the one that is in svn. It looks > like the one in svn/trunk has the jdk 1.6 packages. > > I tried running it from main, but I realized that I was cd'd into the > main\bin directory when I ran it. When I did this, it just hung after > asking for the profile name. > > After getting your prior msg about conf/config.properites. I realized > I started it in the bin directory vs. starting it from main as: > > java -jar bin\felix.jar > > Once I did this, all was well again. Thanks. Now I can start to > experiment. > > --> Brian > > On 4/13/07, Brian Bonner <[EMAIL PROTECTED]> wrote: >> sweet, richard, that did the trick. Yes, I saw the dangling comma at >> the end that looked like it was continuing to look for something. >> >> The new conf/config.properties works like a champ. I'm going to try >> this in the build that came out of svn. >> >> Brian >> >> On 4/13/07, Brian Bonner <[EMAIL PROTECTED]> wrote: >> > doh! yes, I'm running 1.6. >> > >> > I just built felix from the source and ran into a problem with the >> > code needing access to snapshots. Specifically for the >> > maven-bundle-plugin. I had already had the snapshot repository in my >> > settings.xml as a profile, so I built this project by hand: >> > >> > cd felix\tools\maven2\maven-bundle-plugin >> > >> > and ran mvn -P snapshot clean install >> > >> > and then the ant build went fine. >> > >> > I'll try your config file and see if that does the trick. Thanks. >> > >> > Brian >> > >> > On 4/13/07, Richard S. Hall <[EMAIL PROTECTED]> wrote: >> > > You are probably running on a JVM we were not expecting. >> > > >> > > This issue has been somewhat resolved in the trunk. The issue is >> that >> > > the conf/config.properties file is used to construct a list of >> packages >> > > exported by the JVM you are running on. The 0.8.0 release only knows >> > > about 1.3, 1.4, and 1.5...are you running on 1.6? >> > > >> > > In 0.8.0 what would end up happening in the case where it didn't >> > > recognize the JRE version, it would end up creating an invalid >> export >> > > package string with a dangling comma. See your error: >> > > >> > > org.osgi.framework; version >> > > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, >> > > org.osgi.service.startleve >> > > l; version=1.0.0, org.osgi.service.url; version=1.0.0, >> > > >> > > Notice the dangling comma at the end? >> > > >> > > I have attached a config.properties file that fixes the dangling >> comma >> > > issue and adds support for 1.6...see if that works. >> > > >> > > -> richard >> > > >> > > Brian Bonner wrote: >> > > > I'm new to felix. I pulled it down and was trying to run the >> example. >> > > > I was definitely not expecting the resulting stack trace. Can >> anyone >> > > > tell me where I went wrong? >> > > > >> > > > Thanks. >> > > > >> > > > Brian >> > > > >> > > > >> > > > >> > > > C:\felix-0.8.0-incubator>java -jar bin/felix.jar >> > > > >> > > > Welcome to Felix. >> > > > = >> > > > >> > > > Enter profile name: test >> > > > >> > > > ERROR: Error parsing system bundle export statement: >> > > > org.osgi.framework; version >> > > > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, >> > > > org.osgi.service.startleve >> > > > l; version=1.0.0, org.o
Re: error in 0.8.0 in incubator (shellui hang in svn)
Brian, FYI, I just submitted a patch to Main.java that fixed how we calculate the parent directory of felix.jar, which is how we locate the conf/config.properties file. Your comment below about not being able to start from the bin/ directory made me think there was a problem and there was. The method File.getParent() was not returning what I expected, it was actually returning null for relative paths, not the actual parent directory. So, I modified this to use getAbsolutePath() to really get the parent directory. Now you can run Felix from bin (and hopefully any other directory) and it will find conf/config.properties. However! The config.properties file itself DOES expect to be run from the installation directory (or the main directory if using source builds), not from bin/. The config.properties file uses relative paths for auto-starting the shell bundles, so for these relative paths to work, you must do "java -jar bin/felix.jar"...this is just a simplification that allows us to run easily no matter where the files are installed or if you move the felix directory. If you really want Felix to be able to start from any directory, then you must edit the config.properties file to have absolute path names pointing to your shell bundles. -> richard Brian Bonner wrote: I compared the config.properties to the one that is in svn. It looks like the one in svn/trunk has the jdk 1.6 packages. I tried running it from main, but I realized that I was cd'd into the main\bin directory when I ran it. When I did this, it just hung after asking for the profile name. After getting your prior msg about conf/config.properites. I realized I started it in the bin directory vs. starting it from main as: java -jar bin\felix.jar Once I did this, all was well again. Thanks. Now I can start to experiment. --> Brian On 4/13/07, Brian Bonner <[EMAIL PROTECTED]> wrote: sweet, richard, that did the trick. Yes, I saw the dangling comma at the end that looked like it was continuing to look for something. The new conf/config.properties works like a champ. I'm going to try this in the build that came out of svn. Brian On 4/13/07, Brian Bonner <[EMAIL PROTECTED]> wrote: > doh! yes, I'm running 1.6. > > I just built felix from the source and ran into a problem with the > code needing access to snapshots. Specifically for the > maven-bundle-plugin. I had already had the snapshot repository in my > settings.xml as a profile, so I built this project by hand: > > cd felix\tools\maven2\maven-bundle-plugin > > and ran mvn -P snapshot clean install > > and then the ant build went fine. > > I'll try your config file and see if that does the trick. Thanks. > > Brian > > On 4/13/07, Richard S. Hall <[EMAIL PROTECTED]> wrote: > > You are probably running on a JVM we were not expecting. > > > > This issue has been somewhat resolved in the trunk. The issue is that > > the conf/config.properties file is used to construct a list of packages > > exported by the JVM you are running on. The 0.8.0 release only knows > > about 1.3, 1.4, and 1.5...are you running on 1.6? > > > > In 0.8.0 what would end up happening in the case where it didn't > > recognize the JRE version, it would end up creating an invalid export > > package string with a dangling comma. See your error: > > > > org.osgi.framework; version > > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, > > org.osgi.service.startleve > > l; version=1.0.0, org.osgi.service.url; version=1.0.0, > > > > Notice the dangling comma at the end? > > > > I have attached a config.properties file that fixes the dangling comma > > issue and adds support for 1.6...see if that works. > > > > -> richard > > > > Brian Bonner wrote: > > > I'm new to felix. I pulled it down and was trying to run the example. > > > I was definitely not expecting the resulting stack trace. Can anyone > > > tell me where I went wrong? > > > > > > Thanks. > > > > > > Brian > > > > > > > > > > > > C:\felix-0.8.0-incubator>java -jar bin/felix.jar > > > > > > Welcome to Felix. > > > = > > > > > > Enter profile name: test > > > > > > ERROR: Error parsing system bundle export statement: > > > org.osgi.framework; version > > > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, > > > org.osgi.service.startleve > > > l; version=1.0.0, org.osgi.service.url; version=1.0.0, > > > (java.lang.IllegalArgume > > > ntException: No paths specified in header: ) > > > java.lang.IllegalArgumentException: No paths specified in header: > > >at > > > org.apache.felix.framework.util.ManifestParser.parseStandardHeaderCla > > > use(ManifestParser.java:794) > > >at > > > org.apache.felix.framework.util.ManifestParser.parseStandardHeader(Ma > > > nifestParser.java:761) > > >at > > > org.apache.felix.framework.util.ManifestParser.parseImportExportHeade > > > r(ManifestParser.java:668) > > >at > > > org.apache.felix.framework.SystemBundle.(SystemBundle
Re: error in 0.8.0 in incubator (shellui hang in svn)
Brian Bonner wrote: I compared the config.properties to the one that is in svn. It looks like the one in svn/trunk has the jdk 1.6 packages. I tried running it from main, but I realized that I was cd'd into the main\bin directory when I ran it. When I did this, it just hung after asking for the profile name. After getting your prior msg about conf/config.properites. I realized I started it in the bin directory vs. starting it from main as: java -jar bin\felix.jar Once I did this, all was well again. Thanks. Now I can start to experiment. Hmm. It should probably be smarter than that. I will look into it. At any rate, glad that it is now working for you... -> richard --> Brian On 4/13/07, Brian Bonner <[EMAIL PROTECTED]> wrote: sweet, richard, that did the trick. Yes, I saw the dangling comma at the end that looked like it was continuing to look for something. The new conf/config.properties works like a champ. I'm going to try this in the build that came out of svn. Brian On 4/13/07, Brian Bonner <[EMAIL PROTECTED]> wrote: > doh! yes, I'm running 1.6. > > I just built felix from the source and ran into a problem with the > code needing access to snapshots. Specifically for the > maven-bundle-plugin. I had already had the snapshot repository in my > settings.xml as a profile, so I built this project by hand: > > cd felix\tools\maven2\maven-bundle-plugin > > and ran mvn -P snapshot clean install > > and then the ant build went fine. > > I'll try your config file and see if that does the trick. Thanks. > > Brian > > On 4/13/07, Richard S. Hall <[EMAIL PROTECTED]> wrote: > > You are probably running on a JVM we were not expecting. > > > > This issue has been somewhat resolved in the trunk. The issue is that > > the conf/config.properties file is used to construct a list of packages > > exported by the JVM you are running on. The 0.8.0 release only knows > > about 1.3, 1.4, and 1.5...are you running on 1.6? > > > > In 0.8.0 what would end up happening in the case where it didn't > > recognize the JRE version, it would end up creating an invalid export > > package string with a dangling comma. See your error: > > > > org.osgi.framework; version > > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, > > org.osgi.service.startleve > > l; version=1.0.0, org.osgi.service.url; version=1.0.0, > > > > Notice the dangling comma at the end? > > > > I have attached a config.properties file that fixes the dangling comma > > issue and adds support for 1.6...see if that works. > > > > -> richard > > > > Brian Bonner wrote: > > > I'm new to felix. I pulled it down and was trying to run the example. > > > I was definitely not expecting the resulting stack trace. Can anyone > > > tell me where I went wrong? > > > > > > Thanks. > > > > > > Brian > > > > > > > > > > > > C:\felix-0.8.0-incubator>java -jar bin/felix.jar > > > > > > Welcome to Felix. > > > = > > > > > > Enter profile name: test > > > > > > ERROR: Error parsing system bundle export statement: > > > org.osgi.framework; version > > > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, > > > org.osgi.service.startleve > > > l; version=1.0.0, org.osgi.service.url; version=1.0.0, > > > (java.lang.IllegalArgume > > > ntException: No paths specified in header: ) > > > java.lang.IllegalArgumentException: No paths specified in header: > > >at > > > org.apache.felix.framework.util.ManifestParser.parseStandardHeaderCla > > > use(ManifestParser.java:794) > > >at > > > org.apache.felix.framework.util.ManifestParser.parseStandardHeader(Ma > > > nifestParser.java:761) > > >at > > > org.apache.felix.framework.util.ManifestParser.parseImportExportHeade > > > r(ManifestParser.java:668) > > >at > > > org.apache.felix.framework.SystemBundle.(SystemBundle.java:68) > > >at org.apache.felix.framework.Felix.start(Felix.java:344) > > >at org.apache.felix.main.Main.main(Main.java:208) > > > ERROR: Error starting > > > file:bundle/org.apache.felix.shell-0.8.0-incubator.jar (or > > > g.osgi.framework.BundleException: Unresolved package in bundle 1: > > > org.osgi.servi > > > ce.startlevel [version=1.0.0]) > > > org.osgi.framework.BundleException: Unresolved package in bundle 1: > > > org.osgi.ser > > > vice.startlevel [version=1.0.0] > > >at > > > org.apache.felix.framework.Felix._resolveBundle(Felix.java:1362) > > >at org.apache.felix.framework.Felix._startBundle(Felix.java:1241) > > >at org.apache.felix.framework.Felix.startBundle(Felix.java:1201) > > >at > > > org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:80 > > > 7) > > >at > > > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256 > > > ) > > >at java.lang.Thread.run(Thread.java:619) > > > ERROR: Error starting > > > file:bundle/org.apache.felix.shell.tui-0.8.0-incubator.jar > > > (org.osgi.framework.BundleException: Unresolved pa
Re: error in 0.8.0 in incubator
Brian Bonner wrote: sweet, richard, that did the trick. Yes, I saw the dangling comma at the end that looked like it was continuing to look for something. The new conf/config.properties works like a champ. I'm going to try this in the build that came out of svn. If you are building from trunk, then the config.properties file in there should be correct... -> richard Brian On 4/13/07, Brian Bonner <[EMAIL PROTECTED]> wrote: doh! yes, I'm running 1.6. I just built felix from the source and ran into a problem with the code needing access to snapshots. Specifically for the maven-bundle-plugin. I had already had the snapshot repository in my settings.xml as a profile, so I built this project by hand: cd felix\tools\maven2\maven-bundle-plugin and ran mvn -P snapshot clean install and then the ant build went fine. I'll try your config file and see if that does the trick. Thanks. Brian On 4/13/07, Richard S. Hall <[EMAIL PROTECTED]> wrote: > You are probably running on a JVM we were not expecting. > > This issue has been somewhat resolved in the trunk. The issue is that > the conf/config.properties file is used to construct a list of packages > exported by the JVM you are running on. The 0.8.0 release only knows > about 1.3, 1.4, and 1.5...are you running on 1.6? > > In 0.8.0 what would end up happening in the case where it didn't > recognize the JRE version, it would end up creating an invalid export > package string with a dangling comma. See your error: > > org.osgi.framework; version > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, > org.osgi.service.startleve > l; version=1.0.0, org.osgi.service.url; version=1.0.0, > > Notice the dangling comma at the end? > > I have attached a config.properties file that fixes the dangling comma > issue and adds support for 1.6...see if that works. > > -> richard > > Brian Bonner wrote: > > I'm new to felix. I pulled it down and was trying to run the example. > > I was definitely not expecting the resulting stack trace. Can anyone > > tell me where I went wrong? > > > > Thanks. > > > > Brian > > > > > > > > C:\felix-0.8.0-incubator>java -jar bin/felix.jar > > > > Welcome to Felix. > > = > > > > Enter profile name: test > > > > ERROR: Error parsing system bundle export statement: > > org.osgi.framework; version > > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, > > org.osgi.service.startleve > > l; version=1.0.0, org.osgi.service.url; version=1.0.0, > > (java.lang.IllegalArgume > > ntException: No paths specified in header: ) > > java.lang.IllegalArgumentException: No paths specified in header: > >at > > org.apache.felix.framework.util.ManifestParser.parseStandardHeaderCla > > use(ManifestParser.java:794) > >at > > org.apache.felix.framework.util.ManifestParser.parseStandardHeader(Ma > > nifestParser.java:761) > >at > > org.apache.felix.framework.util.ManifestParser.parseImportExportHeade > > r(ManifestParser.java:668) > >at > > org.apache.felix.framework.SystemBundle.(SystemBundle.java:68) > >at org.apache.felix.framework.Felix.start(Felix.java:344) > >at org.apache.felix.main.Main.main(Main.java:208) > > ERROR: Error starting > > file:bundle/org.apache.felix.shell-0.8.0-incubator.jar (or > > g.osgi.framework.BundleException: Unresolved package in bundle 1: > > org.osgi.servi > > ce.startlevel [version=1.0.0]) > > org.osgi.framework.BundleException: Unresolved package in bundle 1: > > org.osgi.ser > > vice.startlevel [version=1.0.0] > >at > > org.apache.felix.framework.Felix._resolveBundle(Felix.java:1362) > >at org.apache.felix.framework.Felix._startBundle(Felix.java:1241) > >at org.apache.felix.framework.Felix.startBundle(Felix.java:1201) > >at > > org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:80 > > 7) > >at > > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256 > > ) > >at java.lang.Thread.run(Thread.java:619) > > ERROR: Error starting > > file:bundle/org.apache.felix.shell.tui-0.8.0-incubator.jar > > (org.osgi.framework.BundleException: Unresolved package in bundle 1: > > org.osgi.s > > ervice.startlevel [version=1.0.0]) > > org.osgi.framework.BundleException: Unresolved package in bundle 1: > > org.osgi.ser > > vice.startlevel [version=1.0.0] > >at > > org.apache.felix.framework.Felix._resolveBundle(Felix.java:1362) > >at org.apache.felix.framework.Felix._startBundle(Felix.java:1241) > >at org.apache.felix.framework.Felix.startBundle(Felix.java:1201) > >at > > org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:80 > > 7) > >at > > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256 > > ) > >at java.lang.Thread.run(Thread.java:619) > > ERROR: Error starting > > file:bundle/org.apache.felix.bundlerepository-0.8.0-incuba > > tor.jar (org.osgi.framework.BundleException: Unresolved
Re: error in 0.8.0 in incubator (shellui hang in svn)
I compared the config.properties to the one that is in svn. It looks like the one in svn/trunk has the jdk 1.6 packages. I tried running it from main, but I realized that I was cd'd into the main\bin directory when I ran it. When I did this, it just hung after asking for the profile name. After getting your prior msg about conf/config.properites. I realized I started it in the bin directory vs. starting it from main as: java -jar bin\felix.jar Once I did this, all was well again. Thanks. Now I can start to experiment. --> Brian On 4/13/07, Brian Bonner <[EMAIL PROTECTED]> wrote: sweet, richard, that did the trick. Yes, I saw the dangling comma at the end that looked like it was continuing to look for something. The new conf/config.properties works like a champ. I'm going to try this in the build that came out of svn. Brian On 4/13/07, Brian Bonner <[EMAIL PROTECTED]> wrote: > doh! yes, I'm running 1.6. > > I just built felix from the source and ran into a problem with the > code needing access to snapshots. Specifically for the > maven-bundle-plugin. I had already had the snapshot repository in my > settings.xml as a profile, so I built this project by hand: > > cd felix\tools\maven2\maven-bundle-plugin > > and ran mvn -P snapshot clean install > > and then the ant build went fine. > > I'll try your config file and see if that does the trick. Thanks. > > Brian > > On 4/13/07, Richard S. Hall <[EMAIL PROTECTED]> wrote: > > You are probably running on a JVM we were not expecting. > > > > This issue has been somewhat resolved in the trunk. The issue is that > > the conf/config.properties file is used to construct a list of packages > > exported by the JVM you are running on. The 0.8.0 release only knows > > about 1.3, 1.4, and 1.5...are you running on 1.6? > > > > In 0.8.0 what would end up happening in the case where it didn't > > recognize the JRE version, it would end up creating an invalid export > > package string with a dangling comma. See your error: > > > > org.osgi.framework; version > > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, > > org.osgi.service.startleve > > l; version=1.0.0, org.osgi.service.url; version=1.0.0, > > > > Notice the dangling comma at the end? > > > > I have attached a config.properties file that fixes the dangling comma > > issue and adds support for 1.6...see if that works. > > > > -> richard > > > > Brian Bonner wrote: > > > I'm new to felix. I pulled it down and was trying to run the example. > > > I was definitely not expecting the resulting stack trace. Can anyone > > > tell me where I went wrong? > > > > > > Thanks. > > > > > > Brian > > > > > > > > > > > > C:\felix-0.8.0-incubator>java -jar bin/felix.jar > > > > > > Welcome to Felix. > > > = > > > > > > Enter profile name: test > > > > > > ERROR: Error parsing system bundle export statement: > > > org.osgi.framework; version > > > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, > > > org.osgi.service.startleve > > > l; version=1.0.0, org.osgi.service.url; version=1.0.0, > > > (java.lang.IllegalArgume > > > ntException: No paths specified in header: ) > > > java.lang.IllegalArgumentException: No paths specified in header: > > >at > > > org.apache.felix.framework.util.ManifestParser.parseStandardHeaderCla > > > use(ManifestParser.java:794) > > >at > > > org.apache.felix.framework.util.ManifestParser.parseStandardHeader(Ma > > > nifestParser.java:761) > > >at > > > org.apache.felix.framework.util.ManifestParser.parseImportExportHeade > > > r(ManifestParser.java:668) > > >at > > > org.apache.felix.framework.SystemBundle.(SystemBundle.java:68) > > >at org.apache.felix.framework.Felix.start(Felix.java:344) > > >at org.apache.felix.main.Main.main(Main.java:208) > > > ERROR: Error starting > > > file:bundle/org.apache.felix.shell-0.8.0-incubator.jar (or > > > g.osgi.framework.BundleException: Unresolved package in bundle 1: > > > org.osgi.servi > > > ce.startlevel [version=1.0.0]) > > > org.osgi.framework.BundleException: Unresolved package in bundle 1: > > > org.osgi.ser > > > vice.startlevel [version=1.0.0] > > >at > > > org.apache.felix.framework.Felix._resolveBundle(Felix.java:1362) > > >at org.apache.felix.framework.Felix._startBundle(Felix.java:1241) > > >at org.apache.felix.framework.Felix.startBundle(Felix.java:1201) > > >at > > > org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:80 > > > 7) > > >at > > > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256 > > > ) > > >at java.lang.Thread.run(Thread.java:619) > > > ERROR: Error starting > > > file:bundle/org.apache.felix.shell.tui-0.8.0-incubator.jar > > > (org.osgi.framework.BundleException: Unresolved package in bundle 1: > > > org.osgi.s > > > ervice.startlevel [version=1.0.0]) > > > org.osgi.framework.BundleException: Unresolved package in bundle 1: > > > org.osgi.ser > > > vice.start
Re: error in 0.8.0 in incubator
sweet, richard, that did the trick. Yes, I saw the dangling comma at the end that looked like it was continuing to look for something. The new conf/config.properties works like a champ. I'm going to try this in the build that came out of svn. Brian On 4/13/07, Brian Bonner <[EMAIL PROTECTED]> wrote: doh! yes, I'm running 1.6. I just built felix from the source and ran into a problem with the code needing access to snapshots. Specifically for the maven-bundle-plugin. I had already had the snapshot repository in my settings.xml as a profile, so I built this project by hand: cd felix\tools\maven2\maven-bundle-plugin and ran mvn -P snapshot clean install and then the ant build went fine. I'll try your config file and see if that does the trick. Thanks. Brian On 4/13/07, Richard S. Hall <[EMAIL PROTECTED]> wrote: > You are probably running on a JVM we were not expecting. > > This issue has been somewhat resolved in the trunk. The issue is that > the conf/config.properties file is used to construct a list of packages > exported by the JVM you are running on. The 0.8.0 release only knows > about 1.3, 1.4, and 1.5...are you running on 1.6? > > In 0.8.0 what would end up happening in the case where it didn't > recognize the JRE version, it would end up creating an invalid export > package string with a dangling comma. See your error: > > org.osgi.framework; version > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, > org.osgi.service.startleve > l; version=1.0.0, org.osgi.service.url; version=1.0.0, > > Notice the dangling comma at the end? > > I have attached a config.properties file that fixes the dangling comma > issue and adds support for 1.6...see if that works. > > -> richard > > Brian Bonner wrote: > > I'm new to felix. I pulled it down and was trying to run the example. > > I was definitely not expecting the resulting stack trace. Can anyone > > tell me where I went wrong? > > > > Thanks. > > > > Brian > > > > > > > > C:\felix-0.8.0-incubator>java -jar bin/felix.jar > > > > Welcome to Felix. > > = > > > > Enter profile name: test > > > > ERROR: Error parsing system bundle export statement: > > org.osgi.framework; version > > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, > > org.osgi.service.startleve > > l; version=1.0.0, org.osgi.service.url; version=1.0.0, > > (java.lang.IllegalArgume > > ntException: No paths specified in header: ) > > java.lang.IllegalArgumentException: No paths specified in header: > >at > > org.apache.felix.framework.util.ManifestParser.parseStandardHeaderCla > > use(ManifestParser.java:794) > >at > > org.apache.felix.framework.util.ManifestParser.parseStandardHeader(Ma > > nifestParser.java:761) > >at > > org.apache.felix.framework.util.ManifestParser.parseImportExportHeade > > r(ManifestParser.java:668) > >at > > org.apache.felix.framework.SystemBundle.(SystemBundle.java:68) > >at org.apache.felix.framework.Felix.start(Felix.java:344) > >at org.apache.felix.main.Main.main(Main.java:208) > > ERROR: Error starting > > file:bundle/org.apache.felix.shell-0.8.0-incubator.jar (or > > g.osgi.framework.BundleException: Unresolved package in bundle 1: > > org.osgi.servi > > ce.startlevel [version=1.0.0]) > > org.osgi.framework.BundleException: Unresolved package in bundle 1: > > org.osgi.ser > > vice.startlevel [version=1.0.0] > >at > > org.apache.felix.framework.Felix._resolveBundle(Felix.java:1362) > >at org.apache.felix.framework.Felix._startBundle(Felix.java:1241) > >at org.apache.felix.framework.Felix.startBundle(Felix.java:1201) > >at > > org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:80 > > 7) > >at > > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256 > > ) > >at java.lang.Thread.run(Thread.java:619) > > ERROR: Error starting > > file:bundle/org.apache.felix.shell.tui-0.8.0-incubator.jar > > (org.osgi.framework.BundleException: Unresolved package in bundle 1: > > org.osgi.s > > ervice.startlevel [version=1.0.0]) > > org.osgi.framework.BundleException: Unresolved package in bundle 1: > > org.osgi.ser > > vice.startlevel [version=1.0.0] > >at > > org.apache.felix.framework.Felix._resolveBundle(Felix.java:1362) > >at org.apache.felix.framework.Felix._startBundle(Felix.java:1241) > >at org.apache.felix.framework.Felix.startBundle(Felix.java:1201) > >at > > org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:80 > > 7) > >at > > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256 > > ) > >at java.lang.Thread.run(Thread.java:619) > > ERROR: Error starting > > file:bundle/org.apache.felix.bundlerepository-0.8.0-incuba > > tor.jar (org.osgi.framework.BundleException: Unresolved package in > > bundle 3: org > > .osgi.framework [version=1.3.0]) > > org.osgi.framework.BundleException: Unresolved package in bundle 3: > > org.osgi.fra >
Re: error in 0.8.0 in incubator
doh! yes, I'm running 1.6. I just built felix from the source and ran into a problem with the code needing access to snapshots. Specifically for the maven-bundle-plugin. I had already had the snapshot repository in my settings.xml as a profile, so I built this project by hand: cd felix\tools\maven2\maven-bundle-plugin and ran mvn -P snapshot clean install and then the ant build went fine. I'll try your config file and see if that does the trick. Thanks. Brian On 4/13/07, Richard S. Hall <[EMAIL PROTECTED]> wrote: You are probably running on a JVM we were not expecting. This issue has been somewhat resolved in the trunk. The issue is that the conf/config.properties file is used to construct a list of packages exported by the JVM you are running on. The 0.8.0 release only knows about 1.3, 1.4, and 1.5...are you running on 1.6? In 0.8.0 what would end up happening in the case where it didn't recognize the JRE version, it would end up creating an invalid export package string with a dangling comma. See your error: org.osgi.framework; version =1.3.0, org.osgi.service.packageadmin; version=1.2.0, org.osgi.service.startleve l; version=1.0.0, org.osgi.service.url; version=1.0.0, Notice the dangling comma at the end? I have attached a config.properties file that fixes the dangling comma issue and adds support for 1.6...see if that works. -> richard Brian Bonner wrote: > I'm new to felix. I pulled it down and was trying to run the example. > I was definitely not expecting the resulting stack trace. Can anyone > tell me where I went wrong? > > Thanks. > > Brian > > > > C:\felix-0.8.0-incubator>java -jar bin/felix.jar > > Welcome to Felix. > = > > Enter profile name: test > > ERROR: Error parsing system bundle export statement: > org.osgi.framework; version > =1.3.0, org.osgi.service.packageadmin; version=1.2.0, > org.osgi.service.startleve > l; version=1.0.0, org.osgi.service.url; version=1.0.0, > (java.lang.IllegalArgume > ntException: No paths specified in header: ) > java.lang.IllegalArgumentException: No paths specified in header: >at > org.apache.felix.framework.util.ManifestParser.parseStandardHeaderCla > use(ManifestParser.java:794) >at > org.apache.felix.framework.util.ManifestParser.parseStandardHeader(Ma > nifestParser.java:761) >at > org.apache.felix.framework.util.ManifestParser.parseImportExportHeade > r(ManifestParser.java:668) >at > org.apache.felix.framework.SystemBundle.(SystemBundle.java:68) >at org.apache.felix.framework.Felix.start(Felix.java:344) >at org.apache.felix.main.Main.main(Main.java:208) > ERROR: Error starting > file:bundle/org.apache.felix.shell-0.8.0-incubator.jar (or > g.osgi.framework.BundleException: Unresolved package in bundle 1: > org.osgi.servi > ce.startlevel [version=1.0.0]) > org.osgi.framework.BundleException: Unresolved package in bundle 1: > org.osgi.ser > vice.startlevel [version=1.0.0] >at > org.apache.felix.framework.Felix._resolveBundle(Felix.java:1362) >at org.apache.felix.framework.Felix._startBundle(Felix.java:1241) >at org.apache.felix.framework.Felix.startBundle(Felix.java:1201) >at > org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:80 > 7) >at > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256 > ) >at java.lang.Thread.run(Thread.java:619) > ERROR: Error starting > file:bundle/org.apache.felix.shell.tui-0.8.0-incubator.jar > (org.osgi.framework.BundleException: Unresolved package in bundle 1: > org.osgi.s > ervice.startlevel [version=1.0.0]) > org.osgi.framework.BundleException: Unresolved package in bundle 1: > org.osgi.ser > vice.startlevel [version=1.0.0] >at > org.apache.felix.framework.Felix._resolveBundle(Felix.java:1362) >at org.apache.felix.framework.Felix._startBundle(Felix.java:1241) >at org.apache.felix.framework.Felix.startBundle(Felix.java:1201) >at > org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:80 > 7) >at > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256 > ) >at java.lang.Thread.run(Thread.java:619) > ERROR: Error starting > file:bundle/org.apache.felix.bundlerepository-0.8.0-incuba > tor.jar (org.osgi.framework.BundleException: Unresolved package in > bundle 3: org > .osgi.framework [version=1.3.0]) > org.osgi.framework.BundleException: Unresolved package in bundle 3: > org.osgi.fra > mework [version=1.3.0] >at > org.apache.felix.framework.Felix._resolveBundle(Felix.java:1362) >at org.apache.felix.framework.Felix._startBundle(Felix.java:1241) >at org.apache.felix.framework.Felix.startBundle(Felix.java:1201) >at > org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:80 > 7) >at > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256 > ) >at java.lang.Thread.run(Thread.java:619) # Licensed to the Apache Software
Re: error in 0.8.0 in incubator
You are probably running on a JVM we were not expecting. This issue has been somewhat resolved in the trunk. The issue is that the conf/config.properties file is used to construct a list of packages exported by the JVM you are running on. The 0.8.0 release only knows about 1.3, 1.4, and 1.5...are you running on 1.6? In 0.8.0 what would end up happening in the case where it didn't recognize the JRE version, it would end up creating an invalid export package string with a dangling comma. See your error: org.osgi.framework; version =1.3.0, org.osgi.service.packageadmin; version=1.2.0, org.osgi.service.startleve l; version=1.0.0, org.osgi.service.url; version=1.0.0, Notice the dangling comma at the end? I have attached a config.properties file that fixes the dangling comma issue and adds support for 1.6...see if that works. -> richard Brian Bonner wrote: I'm new to felix. I pulled it down and was trying to run the example. I was definitely not expecting the resulting stack trace. Can anyone tell me where I went wrong? Thanks. Brian C:\felix-0.8.0-incubator>java -jar bin/felix.jar Welcome to Felix. = Enter profile name: test ERROR: Error parsing system bundle export statement: org.osgi.framework; version =1.3.0, org.osgi.service.packageadmin; version=1.2.0, org.osgi.service.startleve l; version=1.0.0, org.osgi.service.url; version=1.0.0, (java.lang.IllegalArgume ntException: No paths specified in header: ) java.lang.IllegalArgumentException: No paths specified in header: at org.apache.felix.framework.util.ManifestParser.parseStandardHeaderCla use(ManifestParser.java:794) at org.apache.felix.framework.util.ManifestParser.parseStandardHeader(Ma nifestParser.java:761) at org.apache.felix.framework.util.ManifestParser.parseImportExportHeade r(ManifestParser.java:668) at org.apache.felix.framework.SystemBundle.(SystemBundle.java:68) at org.apache.felix.framework.Felix.start(Felix.java:344) at org.apache.felix.main.Main.main(Main.java:208) ERROR: Error starting file:bundle/org.apache.felix.shell-0.8.0-incubator.jar (or g.osgi.framework.BundleException: Unresolved package in bundle 1: org.osgi.servi ce.startlevel [version=1.0.0]) org.osgi.framework.BundleException: Unresolved package in bundle 1: org.osgi.ser vice.startlevel [version=1.0.0] at org.apache.felix.framework.Felix._resolveBundle(Felix.java:1362) at org.apache.felix.framework.Felix._startBundle(Felix.java:1241) at org.apache.felix.framework.Felix.startBundle(Felix.java:1201) at org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:80 7) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256 ) at java.lang.Thread.run(Thread.java:619) ERROR: Error starting file:bundle/org.apache.felix.shell.tui-0.8.0-incubator.jar (org.osgi.framework.BundleException: Unresolved package in bundle 1: org.osgi.s ervice.startlevel [version=1.0.0]) org.osgi.framework.BundleException: Unresolved package in bundle 1: org.osgi.ser vice.startlevel [version=1.0.0] at org.apache.felix.framework.Felix._resolveBundle(Felix.java:1362) at org.apache.felix.framework.Felix._startBundle(Felix.java:1241) at org.apache.felix.framework.Felix.startBundle(Felix.java:1201) at org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:80 7) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256 ) at java.lang.Thread.run(Thread.java:619) ERROR: Error starting file:bundle/org.apache.felix.bundlerepository-0.8.0-incuba tor.jar (org.osgi.framework.BundleException: Unresolved package in bundle 3: org .osgi.framework [version=1.3.0]) org.osgi.framework.BundleException: Unresolved package in bundle 3: org.osgi.fra mework [version=1.3.0] at org.apache.felix.framework.Felix._resolveBundle(Felix.java:1362) at org.apache.felix.framework.Felix._startBundle(Felix.java:1241) at org.apache.felix.framework.Felix.startBundle(Felix.java:1201) at org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:80 7) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:256 ) at java.lang.Thread.run(Thread.java:619) # Licensed to the Apache Software Foundation (ASF) under one # or more contributor license agreements. See the NOTICE file # distributed with this work for additional information # regarding copyright ownership. The ASF licenses this file # to you under the Apache License, Version 2.0 (the # "License"); you may not use this file except in compliance # with the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, # software distributed under the License is distributed on an # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY # KIND, either express or implied. See t
