Re: Felix 1.3.0 Changes
Excellent. Thanx. On Wed, Nov 5, 2008 at 11:01 PM, Richard S. Hall <[EMAIL PROTECTED]> wrote: > Ok, I added some notes to the usage doc, both describing the missing > profiles and the configuration property changes... > > -> richard > > > Alin Dreghiciu wrote: >> >> I guess it would be perfect. >> Thanx. >> >> On Wed, Nov 5, 2008 at 5:03 PM, Richard S. Hall <[EMAIL PROTECTED]> >> wrote: >> >>> >>> Alin, >>> >>> I could add a section to the usage document describing how the old >>> properties have become the new properties, would that work? >>> >>> -> richard >>> >>> Alin Dreghiciu wrote: >>> Thanx for the link Richard. I used the new property for start level. I still think that an migration path or something as what is changed between the "legacy" how you named and 1.4.0 will be a real help for people switching to the new version. On Wed, Nov 5, 2008 at 6:58 PM, Richard S. Hall <[EMAIL PROTECTED]> wrote: > > Alin Dreghiciu wrote: > > >> >> If that's the case, as Stuart mention, can someone provide a list of >> what properties are no longer supported or deprecated and which are >> the new ones? >> >> >> >> > > http://felix.apache.org/site/apache-felix-usage-documentation.html > > -> richard > > > >> >> Thanx, >> >> On Wed, Nov 5, 2008 at 6:04 PM, Stuart McCulloch <[EMAIL PROTECTED]> >> wrote: >> >> >> >>> >>> 2008/11/6 Richard S. Hall <[EMAIL PROTECTED]> >>> >>> >>> >>> Yep, Clement is correct. We have introduced a new property in 1.3.0 development version (1.4.0 should be officially released soon). These new changes align with a standard framework API under consideration by the OSGi Alliance. Felix will now set a reasonable default value for org.osgi.framework.system.packages, but you can override the default by setting this property yourself. If you just want to append to the default value, then use org.osgi.framework.system.packages.extra, like Clement described. >>> >>> quick question: has "felix.startlevel.framework" been deprecated in >>> favour >>> of "org.osgi.framework.startlevel" ? >>> if so then should the old property name still be checked as a last >>> resort? >>> I think it's currently ignored in trunk, >>> but "felix.startlevel.bundle" still seems to be accepted... >>> >>> -> richard >>> >>> >>> Clement Escoffier wrote: > > Hi, > > You can set the "org.osgi.framework.system.packages.extra=" > property > in > the > conf.properties file. > For example: > org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ > bar;version=1.1.0 > > Those packages will be appended to the default list contained in > Felix. > So, if you launch the 'packages 0' command in the Felix shell, you > will > see > the default exported packages, and the two appended packages: > ->packages 0 > ... > System Bundle (0): org.xml.sax.ext; version=1.5.0 > System Bundle (0): org.xml.sax.helpers; version=1.5.0 > System Bundle (0): foo; version=1.0.0 > System Bundle (0): bar; version=1.1.0 > > Regards, > > > Clement > > > > -Original Message- > From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: > mercredi > 5 > novembre 2008 08:20 > To: dev@felix.apache.org > Subject: Felix 1.3.0 Changes > > Hei, > > i have just built the 1.3.0-SNAPSHOT and i see there are some > changes > from > the 1.2.1 (obviously). > > I have a question about how i declare the packages the framework > should > export. Are they defined as before, or is there a new key in the > config.proprties? > > Thank you > - atle prange > > > > > > >>> >>> -- >>> Cheers, Stuart >>> >>> >>> >>> >> >> >> >> >> >> > -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org- New Energy for Java - Domain Driven Development. http://malaysia.jayway.net - New Energy for Projects - Great People working on Great Projects at Great Places
Re: Felix 1.3.0 Changes
Ok, I added some notes to the usage doc, both describing the missing profiles and the configuration property changes... -> richard Alin Dreghiciu wrote: I guess it would be perfect. Thanx. On Wed, Nov 5, 2008 at 5:03 PM, Richard S. Hall <[EMAIL PROTECTED]> wrote: Alin, I could add a section to the usage document describing how the old properties have become the new properties, would that work? -> richard Alin Dreghiciu wrote: Thanx for the link Richard. I used the new property for start level. I still think that an migration path or something as what is changed between the "legacy" how you named and 1.4.0 will be a real help for people switching to the new version. On Wed, Nov 5, 2008 at 6:58 PM, Richard S. Hall <[EMAIL PROTECTED]> wrote: Alin Dreghiciu wrote: If that's the case, as Stuart mention, can someone provide a list of what properties are no longer supported or deprecated and which are the new ones? http://felix.apache.org/site/apache-felix-usage-documentation.html -> richard Thanx, On Wed, Nov 5, 2008 at 6:04 PM, Stuart McCulloch <[EMAIL PROTECTED]> wrote: 2008/11/6 Richard S. Hall <[EMAIL PROTECTED]> Yep, Clement is correct. We have introduced a new property in 1.3.0 development version (1.4.0 should be officially released soon). These new changes align with a standard framework API under consideration by the OSGi Alliance. Felix will now set a reasonable default value for org.osgi.framework.system.packages, but you can override the default by setting this property yourself. If you just want to append to the default value, then use org.osgi.framework.system.packages.extra, like Clement described. quick question: has "felix.startlevel.framework" been deprecated in favour of "org.osgi.framework.startlevel" ? if so then should the old property name still be checked as a last resort? I think it's currently ignored in trunk, but "felix.startlevel.bundle" still seems to be accepted... -> richard Clement Escoffier wrote: Hi, You can set the "org.osgi.framework.system.packages.extra=" property in the conf.properties file. For example: org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ bar;version=1.1.0 Those packages will be appended to the default list contained in Felix. So, if you launch the 'packages 0' command in the Felix shell, you will see the default exported packages, and the two appended packages: ->packages 0 ... System Bundle (0): org.xml.sax.ext; version=1.5.0 System Bundle (0): org.xml.sax.helpers; version=1.5.0 System Bundle (0): foo; version=1.0.0 System Bundle (0): bar; version=1.1.0 Regards, Clement -Original Message- From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: mercredi 5 novembre 2008 08:20 To: dev@felix.apache.org Subject: Felix 1.3.0 Changes Hei, i have just built the 1.3.0-SNAPSHOT and i see there are some changes from the 1.2.1 (obviously). I have a question about how i declare the packages the framework should export. Are they defined as before, or is there a new key in the config.proprties? Thank you - atle prange -- Cheers, Stuart
Re: Felix 1.3.0 Changes
I guess it would be perfect. Thanx. On Wed, Nov 5, 2008 at 5:03 PM, Richard S. Hall <[EMAIL PROTECTED]> wrote: > Alin, > > I could add a section to the usage document describing how the old > properties have become the new properties, would that work? > > -> richard > > Alin Dreghiciu wrote: >> >> Thanx for the link Richard. I used the new property for start level. >> I still think that an migration path or something as what is changed >> between the "legacy" how you named and 1.4.0 will be a real help for >> people switching to the new version. >> >> On Wed, Nov 5, 2008 at 6:58 PM, Richard S. Hall <[EMAIL PROTECTED]> >> wrote: >> >>> >>> Alin Dreghiciu wrote: >>> If that's the case, as Stuart mention, can someone provide a list of what properties are no longer supported or deprecated and which are the new ones? >>> >>> http://felix.apache.org/site/apache-felix-usage-documentation.html >>> >>> -> richard >>> >>> Thanx, On Wed, Nov 5, 2008 at 6:04 PM, Stuart McCulloch <[EMAIL PROTECTED]> wrote: > > 2008/11/6 Richard S. Hall <[EMAIL PROTECTED]> > > > >> >> Yep, Clement is correct. >> >> We have introduced a new property in 1.3.0 development version (1.4.0 >> should be officially released soon). These new changes align with a >> standard >> framework API under consideration by the OSGi Alliance. >> >> Felix will now set a reasonable default value for >> org.osgi.framework.system.packages, but you can override the default >> by >> setting this property yourself. If you just want to append to the >> default >> value, then use org.osgi.framework.system.packages.extra, like Clement >> described. >> >> >> > > quick question: has "felix.startlevel.framework" been deprecated in > favour > of "org.osgi.framework.startlevel" ? > if so then should the old property name still be checked as a last > resort? > I think it's currently ignored in trunk, > but "felix.startlevel.bundle" still seems to be accepted... > > -> richard > > >> >> Clement Escoffier wrote: >> >> >> >>> >>> Hi, >>> >>> You can set the "org.osgi.framework.system.packages.extra=" property >>> in >>> the >>> conf.properties file. >>> For example: >>> org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ >>> bar;version=1.1.0 >>> >>> Those packages will be appended to the default list contained in >>> Felix. >>> So, if you launch the 'packages 0' command in the Felix shell, you >>> will >>> see >>> the default exported packages, and the two appended packages: >>> ->packages 0 >>> ... >>> System Bundle (0): org.xml.sax.ext; version=1.5.0 >>> System Bundle (0): org.xml.sax.helpers; version=1.5.0 >>> System Bundle (0): foo; version=1.0.0 >>> System Bundle (0): bar; version=1.1.0 >>> >>> Regards, >>> >>> >>> Clement >>> >>> >>> >>> -Original Message- >>> From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: mercredi >>> 5 >>> novembre 2008 08:20 >>> To: dev@felix.apache.org >>> Subject: Felix 1.3.0 Changes >>> >>> Hei, >>> >>> i have just built the 1.3.0-SNAPSHOT and i see there are some changes >>> from >>> the 1.2.1 (obviously). >>> >>> I have a question about how i declare the packages the framework >>> should >>> export. Are they defined as before, or is there a new key in the >>> config.proprties? >>> >>> Thank you >>> - atle prange >>> >>> >>> >>> >>> > > -- > Cheers, Stuart > > > >> >> >> >> > -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org- New Energy for Java - Domain Driven Development. http://malaysia.jayway.net - New Energy for Projects - Great People working on Great Projects at Great Places
Re: Felix 1.3.0 Changes
Alin, I could add a section to the usage document describing how the old properties have become the new properties, would that work? -> richard Alin Dreghiciu wrote: Thanx for the link Richard. I used the new property for start level. I still think that an migration path or something as what is changed between the "legacy" how you named and 1.4.0 will be a real help for people switching to the new version. On Wed, Nov 5, 2008 at 6:58 PM, Richard S. Hall <[EMAIL PROTECTED]> wrote: Alin Dreghiciu wrote: If that's the case, as Stuart mention, can someone provide a list of what properties are no longer supported or deprecated and which are the new ones? http://felix.apache.org/site/apache-felix-usage-documentation.html -> richard Thanx, On Wed, Nov 5, 2008 at 6:04 PM, Stuart McCulloch <[EMAIL PROTECTED]> wrote: 2008/11/6 Richard S. Hall <[EMAIL PROTECTED]> Yep, Clement is correct. We have introduced a new property in 1.3.0 development version (1.4.0 should be officially released soon). These new changes align with a standard framework API under consideration by the OSGi Alliance. Felix will now set a reasonable default value for org.osgi.framework.system.packages, but you can override the default by setting this property yourself. If you just want to append to the default value, then use org.osgi.framework.system.packages.extra, like Clement described. quick question: has "felix.startlevel.framework" been deprecated in favour of "org.osgi.framework.startlevel" ? if so then should the old property name still be checked as a last resort? I think it's currently ignored in trunk, but "felix.startlevel.bundle" still seems to be accepted... -> richard Clement Escoffier wrote: Hi, You can set the "org.osgi.framework.system.packages.extra=" property in the conf.properties file. For example: org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ bar;version=1.1.0 Those packages will be appended to the default list contained in Felix. So, if you launch the 'packages 0' command in the Felix shell, you will see the default exported packages, and the two appended packages: ->packages 0 ... System Bundle (0): org.xml.sax.ext; version=1.5.0 System Bundle (0): org.xml.sax.helpers; version=1.5.0 System Bundle (0): foo; version=1.0.0 System Bundle (0): bar; version=1.1.0 Regards, Clement -Original Message- From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: mercredi 5 novembre 2008 08:20 To: dev@felix.apache.org Subject: Felix 1.3.0 Changes Hei, i have just built the 1.3.0-SNAPSHOT and i see there are some changes from the 1.2.1 (obviously). I have a question about how i declare the packages the framework should export. Are they defined as before, or is there a new key in the config.proprties? Thank you - atle prange -- Cheers, Stuart
Re: Felix 1.3.0 Changes
Thanx for the link Richard. I used the new property for start level. I still think that an migration path or something as what is changed between the "legacy" how you named and 1.4.0 will be a real help for people switching to the new version. On Wed, Nov 5, 2008 at 6:58 PM, Richard S. Hall <[EMAIL PROTECTED]> wrote: > > > Alin Dreghiciu wrote: >> >> If that's the case, as Stuart mention, can someone provide a list of >> what properties are no longer supported or deprecated and which are >> the new ones? >> >> > > http://felix.apache.org/site/apache-felix-usage-documentation.html > > -> richard > >> Thanx, >> >> On Wed, Nov 5, 2008 at 6:04 PM, Stuart McCulloch <[EMAIL PROTECTED]> >> wrote: >> >>> >>> 2008/11/6 Richard S. Hall <[EMAIL PROTECTED]> >>> >>> Yep, Clement is correct. We have introduced a new property in 1.3.0 development version (1.4.0 should be officially released soon). These new changes align with a standard framework API under consideration by the OSGi Alliance. Felix will now set a reasonable default value for org.osgi.framework.system.packages, but you can override the default by setting this property yourself. If you just want to append to the default value, then use org.osgi.framework.system.packages.extra, like Clement described. >>> >>> quick question: has "felix.startlevel.framework" been deprecated in >>> favour >>> of "org.osgi.framework.startlevel" ? >>> if so then should the old property name still be checked as a last >>> resort? >>> I think it's currently ignored in trunk, >>> but "felix.startlevel.bundle" still seems to be accepted... >>> >>> -> richard >>> Clement Escoffier wrote: > > Hi, > > You can set the "org.osgi.framework.system.packages.extra=" property in > the > conf.properties file. > For example: > org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ > bar;version=1.1.0 > > Those packages will be appended to the default list contained in Felix. > So, if you launch the 'packages 0' command in the Felix shell, you will > see > the default exported packages, and the two appended packages: > ->packages 0 > ... > System Bundle (0): org.xml.sax.ext; version=1.5.0 > System Bundle (0): org.xml.sax.helpers; version=1.5.0 > System Bundle (0): foo; version=1.0.0 > System Bundle (0): bar; version=1.1.0 > > Regards, > > > Clement > > > > -Original Message- > From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: mercredi 5 > novembre 2008 08:20 > To: dev@felix.apache.org > Subject: Felix 1.3.0 Changes > > Hei, > > i have just built the 1.3.0-SNAPSHOT and i see there are some changes > from > the 1.2.1 (obviously). > > I have a question about how i declare the packages the framework should > export. Are they defined as before, or is there a new key in the > config.proprties? > > Thank you > - atle prange > > > > >>> >>> -- >>> Cheers, Stuart >>> >>> >> >> >> >> > -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org- New Energy for Java - Domain Driven Development. http://malaysia.jayway.net - New Energy for Projects - Great People working on Great Projects at Great Places
[jira] Commented: (FELIX-806) changing the internal configuration of the archive plugin doesn't seem to be possible
[ https://issues.apache.org/jira/browse/FELIX-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645305#action_12645305 ] Stuart McCulloch commented on FELIX-806: FYI we do already read some settings from the archive configuration of the maven-jar-plugin, but unfortunately don't take notice of the descriptor setting, so the descriptor is always added It should be straightforward to fix, however I have not yet planned the next release of the plugin > changing the internal configuration of the archive plugin doesn't seem to be > possible > - > > Key: FELIX-806 > URL: https://issues.apache.org/jira/browse/FELIX-806 > Project: Felix > Issue Type: Improvement > Components: Maven Bundle Plugin >Reporter: Sylvain MARIE > > Hi, > It does not seem to be possible to configure the maven-archive-plugin through > configuration of the maven-bundle plugin. > For example in order to remove the META-INF/maven dir in a resulting jar you > can do the following conf > of the maven-jar-plugin: > > > > org.apache.maven.plugins > maven-jar-plugin > > > > > false > > > > > > This will result in the internal archive plugin being configured accordingly > (i.e. without the META-INF/maven dir). > However it is not possible to do the same with maven-bundle-plugin. > Could this feature be integrated easily ? > Thanks, > Sylvain -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-806) changing the internal configuration of the archive plugin doesn't seem to be possible
changing the internal configuration of the archive plugin doesn't seem to be possible - Key: FELIX-806 URL: https://issues.apache.org/jira/browse/FELIX-806 Project: Felix Issue Type: Improvement Components: Maven Bundle Plugin Reporter: Sylvain MARIE Hi, It does not seem to be possible to configure the maven-archive-plugin through configuration of the maven-bundle plugin. For example in order to remove the META-INF/maven dir in a resulting jar you can do the following conf of the maven-jar-plugin: org.apache.maven.plugins maven-jar-plugin false This will result in the internal archive plugin being configured accordingly (i.e. without the META-INF/maven dir). However it is not possible to do the same with maven-bundle-plugin. Could this feature be integrated easily ? Thanks, Sylvain -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Felix 1.3.0 Changes
Alin Dreghiciu wrote: If that's the case, as Stuart mention, can someone provide a list of what properties are no longer supported or deprecated and which are the new ones? http://felix.apache.org/site/apache-felix-usage-documentation.html -> richard Thanx, On Wed, Nov 5, 2008 at 6:04 PM, Stuart McCulloch <[EMAIL PROTECTED]> wrote: 2008/11/6 Richard S. Hall <[EMAIL PROTECTED]> Yep, Clement is correct. We have introduced a new property in 1.3.0 development version (1.4.0 should be officially released soon). These new changes align with a standard framework API under consideration by the OSGi Alliance. Felix will now set a reasonable default value for org.osgi.framework.system.packages, but you can override the default by setting this property yourself. If you just want to append to the default value, then use org.osgi.framework.system.packages.extra, like Clement described. quick question: has "felix.startlevel.framework" been deprecated in favour of "org.osgi.framework.startlevel" ? if so then should the old property name still be checked as a last resort? I think it's currently ignored in trunk, but "felix.startlevel.bundle" still seems to be accepted... -> richard Clement Escoffier wrote: Hi, You can set the "org.osgi.framework.system.packages.extra=" property in the conf.properties file. For example: org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ bar;version=1.1.0 Those packages will be appended to the default list contained in Felix. So, if you launch the 'packages 0' command in the Felix shell, you will see the default exported packages, and the two appended packages: ->packages 0 ... System Bundle (0): org.xml.sax.ext; version=1.5.0 System Bundle (0): org.xml.sax.helpers; version=1.5.0 System Bundle (0): foo; version=1.0.0 System Bundle (0): bar; version=1.1.0 Regards, Clement -Original Message- From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: mercredi 5 novembre 2008 08:20 To: dev@felix.apache.org Subject: Felix 1.3.0 Changes Hei, i have just built the 1.3.0-SNAPSHOT and i see there are some changes from the 1.2.1 (obviously). I have a question about how i declare the packages the framework should export. Are they defined as before, or is there a new key in the config.proprties? Thank you - atle prange -- Cheers, Stuart
Re: Felix 1.3.0 Changes
Stuart McCulloch wrote: 2008/11/6 Richard S. Hall <[EMAIL PROTECTED]> Yep, Clement is correct. We have introduced a new property in 1.3.0 development version (1.4.0 should be officially released soon). These new changes align with a standard framework API under consideration by the OSGi Alliance. Felix will now set a reasonable default value for org.osgi.framework.system.packages, but you can override the default by setting this property yourself. If you just want to append to the default value, then use org.osgi.framework.system.packages.extra, like Clement described. quick question: has "felix.startlevel.framework" been deprecated in favour of "org.osgi.framework.startlevel" ? if so then should the old property name still be checked as a last resort? I think it's currently ignored in trunk, but "felix.startlevel.bundle" still seems to be accepted... The framework startlevel property is the newly proposed standard property, but there is no equivalent one proposed for bundles, so we have to keep the Felix one... I am not a fan of keeping around Felix-specific legacy. I understand that this may cause some issues for people upgrading, but it is pretty minor and it encourages people to move to the standard settings, which is ultimately beneficial to them since it will work across frameworks. -> richard -> richard Clement Escoffier wrote: Hi, You can set the "org.osgi.framework.system.packages.extra=" property in the conf.properties file. For example: org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ bar;version=1.1.0 Those packages will be appended to the default list contained in Felix. So, if you launch the 'packages 0' command in the Felix shell, you will see the default exported packages, and the two appended packages: ->packages 0 ... System Bundle (0): org.xml.sax.ext; version=1.5.0 System Bundle (0): org.xml.sax.helpers; version=1.5.0 System Bundle (0): foo; version=1.0.0 System Bundle (0): bar; version=1.1.0 Regards, Clement -Original Message- From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: mercredi 5 novembre 2008 08:20 To: dev@felix.apache.org Subject: Felix 1.3.0 Changes Hei, i have just built the 1.3.0-SNAPSHOT and i see there are some changes from the 1.2.1 (obviously). I have a question about how i declare the packages the framework should export. Are they defined as before, or is there a new key in the config.proprties? Thank you - atle prange
Re: Felix 1.3.0 Changes
If that's the case, as Stuart mention, can someone provide a list of what properties are no longer supported or deprecated and which are the new ones? Thanx, On Wed, Nov 5, 2008 at 6:04 PM, Stuart McCulloch <[EMAIL PROTECTED]> wrote: > 2008/11/6 Richard S. Hall <[EMAIL PROTECTED]> > >> Yep, Clement is correct. >> >> We have introduced a new property in 1.3.0 development version (1.4.0 >> should be officially released soon). These new changes align with a standard >> framework API under consideration by the OSGi Alliance. >> >> Felix will now set a reasonable default value for >> org.osgi.framework.system.packages, but you can override the default by >> setting this property yourself. If you just want to append to the default >> value, then use org.osgi.framework.system.packages.extra, like Clement >> described. >> > > quick question: has "felix.startlevel.framework" been deprecated in favour > of "org.osgi.framework.startlevel" ? > if so then should the old property name still be checked as a last resort? > I think it's currently ignored in trunk, > but "felix.startlevel.bundle" still seems to be accepted... > > -> richard >> >> Clement Escoffier wrote: >> >>> Hi, >>> >>> You can set the "org.osgi.framework.system.packages.extra=" property in >>> the >>> conf.properties file. >>> For example: >>> org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ >>> bar;version=1.1.0 >>> >>> Those packages will be appended to the default list contained in Felix. >>> So, if you launch the 'packages 0' command in the Felix shell, you will >>> see >>> the default exported packages, and the two appended packages: >>> ->packages 0 >>> ... >>> System Bundle (0): org.xml.sax.ext; version=1.5.0 >>> System Bundle (0): org.xml.sax.helpers; version=1.5.0 >>> System Bundle (0): foo; version=1.0.0 >>> System Bundle (0): bar; version=1.1.0 >>> >>> Regards, >>> >>> >>> Clement >>> >>> >>> >>> -Original Message- >>> From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: mercredi 5 >>> novembre 2008 08:20 >>> To: dev@felix.apache.org >>> Subject: Felix 1.3.0 Changes >>> >>> Hei, >>> >>> i have just built the 1.3.0-SNAPSHOT and i see there are some changes from >>> the 1.2.1 (obviously). >>> >>> I have a question about how i declare the packages the framework should >>> export. Are they defined as before, or is there a new key in the >>> config.proprties? >>> >>> Thank you >>> - atle prange >>> >>> >>> >> > > > -- > Cheers, Stuart > -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org- New Energy for Java - Domain Driven Development. http://malaysia.jayway.net - New Energy for Projects - Great People working on Great Projects at Great Places
Re: Felix 1.3.0 Changes
2008/11/6 Richard S. Hall <[EMAIL PROTECTED]> > Yep, Clement is correct. > > We have introduced a new property in 1.3.0 development version (1.4.0 > should be officially released soon). These new changes align with a standard > framework API under consideration by the OSGi Alliance. > > Felix will now set a reasonable default value for > org.osgi.framework.system.packages, but you can override the default by > setting this property yourself. If you just want to append to the default > value, then use org.osgi.framework.system.packages.extra, like Clement > described. > quick question: has "felix.startlevel.framework" been deprecated in favour of "org.osgi.framework.startlevel" ? if so then should the old property name still be checked as a last resort? I think it's currently ignored in trunk, but "felix.startlevel.bundle" still seems to be accepted... -> richard > > Clement Escoffier wrote: > >> Hi, >> >> You can set the "org.osgi.framework.system.packages.extra=" property in >> the >> conf.properties file. >> For example: >> org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ >> bar;version=1.1.0 >> >> Those packages will be appended to the default list contained in Felix. >> So, if you launch the 'packages 0' command in the Felix shell, you will >> see >> the default exported packages, and the two appended packages: >> ->packages 0 >> ... >> System Bundle (0): org.xml.sax.ext; version=1.5.0 >> System Bundle (0): org.xml.sax.helpers; version=1.5.0 >> System Bundle (0): foo; version=1.0.0 >> System Bundle (0): bar; version=1.1.0 >> >> Regards, >> >> >> Clement >> >> >> >> -Original Message- >> From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: mercredi 5 >> novembre 2008 08:20 >> To: dev@felix.apache.org >> Subject: Felix 1.3.0 Changes >> >> Hei, >> >> i have just built the 1.3.0-SNAPSHOT and i see there are some changes from >> the 1.2.1 (obviously). >> >> I have a question about how i declare the packages the framework should >> export. Are they defined as before, or is there a new key in the >> config.proprties? >> >> Thank you >> - atle prange >> >> >> > -- Cheers, Stuart
[jira] Closed: (FELIX-799) ServiceReferenceImpl does not support the compareTo() method
[ https://issues.apache.org/jira/browse/FELIX-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart McCulloch closed FELIX-799. -- Tested and it works great - closing issue. > ServiceReferenceImpl does not support the compareTo() method > > > Key: FELIX-799 > URL: https://issues.apache.org/jira/browse/FELIX-799 > Project: Felix > Issue Type: Bug > Components: Framework, Specification compliance >Affects Versions: felix-1.2.2 >Reporter: Stuart McCulloch >Assignee: Richard S. Hall > Fix For: felix-1.4.0 > > Attachments: FELIX-799.txt > > > The current ServiceReferenceImpl does not support the compareTo() method, > introduced in release 4.1 of the OSGi spec: > > http://www.osgi.org/javadoc/r4v41/org/osgi/framework/ServiceReference.html#compareTo(java.lang.Object) > I'm also going to link to the general contract for compareTo() in the Java > spec, as it explains what happens when comparing against different types: > > http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Comparable.html#compareTo(java.lang.Object) > I'll attach an initial patch which should work according to the spec, > although I have not tested it thoroughly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Felix 1.3.0 Changes
Alin Dreghiciu wrote: Hi, Do you have an rough date when 1.4.0 is out? So, I know how to plan support in Pax Runner. We are shooting for calling the vote tomorrow, but if that slips we will probably wait until Monday to avoid calling a vote just before the weekend. -> richard Thanx. On Wed, Nov 5, 2008 at 5:22 PM, Richard S. Hall <[EMAIL PROTECTED]> wrote: Yep, Clement is correct. We have introduced a new property in 1.3.0 development version (1.4.0 should be officially released soon). These new changes align with a standard framework API under consideration by the OSGi Alliance. Felix will now set a reasonable default value for org.osgi.framework.system.packages, but you can override the default by setting this property yourself. If you just want to append to the default value, then use org.osgi.framework.system.packages.extra, like Clement described. -> richard Clement Escoffier wrote: Hi, You can set the "org.osgi.framework.system.packages.extra=" property in the conf.properties file. For example: org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ bar;version=1.1.0 Those packages will be appended to the default list contained in Felix. So, if you launch the 'packages 0' command in the Felix shell, you will see the default exported packages, and the two appended packages: ->packages 0 ... System Bundle (0): org.xml.sax.ext; version=1.5.0 System Bundle (0): org.xml.sax.helpers; version=1.5.0 System Bundle (0): foo; version=1.0.0 System Bundle (0): bar; version=1.1.0 Regards, Clement -Original Message- From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: mercredi 5 novembre 2008 08:20 To: dev@felix.apache.org Subject: Felix 1.3.0 Changes Hei, i have just built the 1.3.0-SNAPSHOT and i see there are some changes from the 1.2.1 (obviously). I have a question about how i declare the packages the framework should export. Are they defined as before, or is there a new key in the config.proprties? Thank you - atle prange
Re: Felix 1.3.0 Changes
Hi, Do you have an rough date when 1.4.0 is out? So, I know how to plan support in Pax Runner. Thanx. On Wed, Nov 5, 2008 at 5:22 PM, Richard S. Hall <[EMAIL PROTECTED]> wrote: > Yep, Clement is correct. > > We have introduced a new property in 1.3.0 development version (1.4.0 should > be officially released soon). These new changes align with a standard > framework API under consideration by the OSGi Alliance. > > Felix will now set a reasonable default value for > org.osgi.framework.system.packages, but you can override the default by > setting this property yourself. If you just want to append to the default > value, then use org.osgi.framework.system.packages.extra, like Clement > described. > > -> richard > > Clement Escoffier wrote: >> >> Hi, >> >> You can set the "org.osgi.framework.system.packages.extra=" property in >> the >> conf.properties file. >> For example: >> org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ >> bar;version=1.1.0 >> >> Those packages will be appended to the default list contained in Felix. >> So, if you launch the 'packages 0' command in the Felix shell, you will >> see >> the default exported packages, and the two appended packages: >> ->packages 0 >> ... >> System Bundle (0): org.xml.sax.ext; version=1.5.0 >> System Bundle (0): org.xml.sax.helpers; version=1.5.0 >> System Bundle (0): foo; version=1.0.0 >> System Bundle (0): bar; version=1.1.0 >> >> Regards, >> >> >> Clement >> >> >> >> -Original Message- >> From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: mercredi 5 >> novembre 2008 08:20 >> To: dev@felix.apache.org >> Subject: Felix 1.3.0 Changes >> >> Hei, >> >> i have just built the 1.3.0-SNAPSHOT and i see there are some changes from >> the 1.2.1 (obviously). >> >> I have a question about how i declare the packages the framework should >> export. Are they defined as before, or is there a new key in the >> config.proprties? >> >> Thank you >> - atle prange >> >> > -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org- New Energy for Java - Domain Driven Development. http://malaysia.jayway.net - New Energy for Projects - Great People working on Great Projects at Great Places
Re: Felix 1.3.0 Changes
Yep, Clement is correct. We have introduced a new property in 1.3.0 development version (1.4.0 should be officially released soon). These new changes align with a standard framework API under consideration by the OSGi Alliance. Felix will now set a reasonable default value for org.osgi.framework.system.packages, but you can override the default by setting this property yourself. If you just want to append to the default value, then use org.osgi.framework.system.packages.extra, like Clement described. -> richard Clement Escoffier wrote: Hi, You can set the "org.osgi.framework.system.packages.extra=" property in the conf.properties file. For example: org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ bar;version=1.1.0 Those packages will be appended to the default list contained in Felix. So, if you launch the 'packages 0' command in the Felix shell, you will see the default exported packages, and the two appended packages: ->packages 0 ... System Bundle (0): org.xml.sax.ext; version=1.5.0 System Bundle (0): org.xml.sax.helpers; version=1.5.0 System Bundle (0): foo; version=1.0.0 System Bundle (0): bar; version=1.1.0 Regards, Clement -Original Message- From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: mercredi 5 novembre 2008 08:20 To: dev@felix.apache.org Subject: Felix 1.3.0 Changes Hei, i have just built the 1.3.0-SNAPSHOT and i see there are some changes from the 1.2.1 (obviously). I have a question about how i declare the packages the framework should export. Are they defined as before, or is there a new key in the config.proprties? Thank you - atle prange
[jira] Commented: (FELIX-756) Allow URLStreamHandler services to override built-in handlers.
[ https://issues.apache.org/jira/browse/FELIX-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645233#action_12645233 ] Karl Pauls commented on FELIX-756: -- Don't bother with the system property. Starting with revision 711578, the trunk will override the built-in handlers by default. Please don't forget to test and close this issue if it works for you. > Allow URLStreamHandler services to override built-in handlers. > --- > > Key: FELIX-756 > URL: https://issues.apache.org/jira/browse/FELIX-756 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: felix-1.2.2 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: felix-1.4.0 > > > In certain cases it might be desirable to override built-in URLStreamHandlers > with services provided by bundles. As of now, the spec doesn't allow this > (see 11.3.2 ff) but it might in the future. Furthermore, it looks like other > implementations are less strict on this issue as we are. For now, the best > one can do is to put handlers in the classpath of the framework and make them > available via the java.protocol.handler.pkgs properties. This way, one can > override the built-in handlers but needs control over the jvm (which is not > the best solution). > It should be possible to add an option to felix that will register handlers > that proxy the built-in ones but prefer registered URLStreamHandler services > if there is one available for a given schema. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: Felix 1.3.0 Changes
Hi, You can set the "org.osgi.framework.system.packages.extra=" property in the conf.properties file. For example: org.osgi.framework.system.packages.extra=foo;version=1.0.0, \ bar;version=1.1.0 Those packages will be appended to the default list contained in Felix. So, if you launch the 'packages 0' command in the Felix shell, you will see the default exported packages, and the two appended packages: ->packages 0 ... System Bundle (0): org.xml.sax.ext; version=1.5.0 System Bundle (0): org.xml.sax.helpers; version=1.5.0 System Bundle (0): foo; version=1.0.0 System Bundle (0): bar; version=1.1.0 Regards, Clement -Original Message- From: Atle Prange [mailto:[EMAIL PROTECTED] Sent: mercredi 5 novembre 2008 08:20 To: dev@felix.apache.org Subject: Felix 1.3.0 Changes Hei, i have just built the 1.3.0-SNAPSHOT and i see there are some changes from the 1.2.1 (obviously). I have a question about how i declare the packages the framework should export. Are they defined as before, or is there a new key in the config.proprties? Thank you - atle prange
[jira] Resolved: (FELIX-805) Instance not created if the factory becomes valid later
[ https://issues.apache.org/jira/browse/FELIX-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier resolved FELIX-805. - Resolution: Fixed Fixed at revision: 711559. Instances targeting non valid factories are created as soon as the factory becomes valid. > Instance not created if the factory becomes valid later > --- > > Key: FELIX-805 > URL: https://issues.apache.org/jira/browse/FELIX-805 > Project: Felix > Issue Type: Bug > Components: iPOJO >Affects Versions: iPOJO-1.0.0 >Reporter: Clement Escoffier >Assignee: Clement Escoffier > Fix For: iPOJO-1.2.0 > > > When an instance is declared, and uses a non valid factory, the instance > creation fails. However, when the factory becomes valid (later), the instance > must be re-created (successfully). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-803) iPOJO Core schema needs to be fixed
[ https://issues.apache.org/jira/browse/FELIX-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645211#action_12645211 ] Clement Escoffier commented on FELIX-803: - Fixed at revision: 711559. The 'interface' attribute is now prohibited in service dependencies. This old attribute was replaced by specification to be consistent with other service dependencies. Guillaume, do you see another inconsistency in the XML-Schema? > iPOJO Core schema needs to be fixed > --- > > Key: FELIX-803 > URL: https://issues.apache.org/jira/browse/FELIX-803 > Project: Felix > Issue Type: Bug > Components: iPOJO >Affects Versions: iPOJO-1.0.0 >Reporter: Guillaume Sauthier >Assignee: Clement Escoffier > > The @interface attribute is still defined in the RequiresType complexType in > the core.xsd -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (FELIX-803) iPOJO Core schema needs to be fixed
[ https://issues.apache.org/jira/browse/FELIX-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-803 started by Clement Escoffier. > iPOJO Core schema needs to be fixed > --- > > Key: FELIX-803 > URL: https://issues.apache.org/jira/browse/FELIX-803 > Project: Felix > Issue Type: Bug > Components: iPOJO >Affects Versions: iPOJO-1.0.0 >Reporter: Guillaume Sauthier >Assignee: Clement Escoffier > > The @interface attribute is still defined in the RequiresType complexType in > the core.xsd -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-805) Instance not created if the factory becomes valid later
Instance not created if the factory becomes valid later --- Key: FELIX-805 URL: https://issues.apache.org/jira/browse/FELIX-805 Project: Felix Issue Type: Bug Components: iPOJO Affects Versions: iPOJO-1.0.0 Reporter: Clement Escoffier Assignee: Clement Escoffier Fix For: iPOJO-1.2.0 When an instance is declared, and uses a non valid factory, the instance creation fails. However, when the factory becomes valid (later), the instance must be re-created (successfully). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Felix 1.3.0 Changes
Hei, i have just built the 1.3.0-SNAPSHOT and i see there are some changes from the 1.2.1 (obviously). I have a question about how i declare the packages the framework should export. Are they defined as before, or is there a new key in the config.proprties? Thank you - atle prange
[jira] Assigned: (FELIX-803) iPOJO Core schema needs to be fixed
[ https://issues.apache.org/jira/browse/FELIX-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier reassigned FELIX-803: --- Assignee: Clement Escoffier > iPOJO Core schema needs to be fixed > --- > > Key: FELIX-803 > URL: https://issues.apache.org/jira/browse/FELIX-803 > Project: Felix > Issue Type: Bug > Components: iPOJO >Affects Versions: iPOJO-1.0.0 >Reporter: Guillaume Sauthier >Assignee: Clement Escoffier > > The @interface attribute is still defined in the RequiresType complexType in > the core.xsd -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Contributing parts of the ServiceRegistry Hooks (RFC 126) implementation into Felix
Hello David, On Nov 4, 2008, at 17:33 , David Bosschaert wrote: In the context of the Apache CXF project a number of people have been involved in implementing the Distribution Software part of Distributed OSGi (RFC 119 [1]). [...] If Felix is interested in taking this implementation, it might make sense to create a bug in Felix JIRA so that this stuff can be attached as a patch to that once its ready to move into Felix. +1 That's great news! After discussing this with you in Berlin, I've become very enthousiastic about this. Greetings, Marcel
