[jira] [Work started] (FELIX-3883) [Framework] Move OS and processor aliases to configuration properties
[ https://issues.apache.org/jira/browse/FELIX-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-3883 started by Bob Paulin. - [Framework] Move OS and processor aliases to configuration properties - Key: FELIX-3883 URL: https://issues.apache.org/jira/browse/FELIX-3883 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-4.2.0 Reporter: Richard S. Hall Assignee: Bob Paulin Fix For: framework-4.6.0 Currently, we hard code our OS and processor aliases for matching native code libraries. This is bad since it requires us to edit source code to add aliases. It would be better if we moved these to configuration properties, something like this: felix.native.os.[normalname] = alias1, alias2, etc. felix.native.arch.[normalname] = alias1, alias2, etc. More concretely: felix.native.os.win32 = Windows 8, Windows 7, Windows Vista felix.native.arch.x86 = i386, i486, i586 We could then use the properties to define as many normal names as we want and associate all their known aliases, so at run time all names could be normalized. We can include a default set of normal names and aliases in default.properties, but allow people to override any of them (or add new normal names/aliases) in config.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-3883) [Framework] Move OS and processor aliases to configuration properties
[ https://issues.apache.org/jira/browse/FELIX-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270474#comment-14270474 ] Bob Paulin commented on FELIX-3883: --- Addressed with rev 1650432 [Framework] Move OS and processor aliases to configuration properties - Key: FELIX-3883 URL: https://issues.apache.org/jira/browse/FELIX-3883 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-4.2.0 Reporter: Richard S. Hall Assignee: Bob Paulin Fix For: framework-4.6.0 Currently, we hard code our OS and processor aliases for matching native code libraries. This is bad since it requires us to edit source code to add aliases. It would be better if we moved these to configuration properties, something like this: felix.native.os.[normalname] = alias1, alias2, etc. felix.native.arch.[normalname] = alias1, alias2, etc. More concretely: felix.native.os.win32 = Windows 8, Windows 7, Windows Vista felix.native.arch.x86 = i386, i486, i586 We could then use the properties to define as many normal names as we want and associate all their known aliases, so at run time all names could be normalized. We can include a default set of normal names and aliases in default.properties, but allow people to override any of them (or add new normal names/aliases) in config.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-3883) [Framework] Move OS and processor aliases to configuration properties
[ https://issues.apache.org/jira/browse/FELIX-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Paulin resolved FELIX-3883. --- Resolution: Fixed [Framework] Move OS and processor aliases to configuration properties - Key: FELIX-3883 URL: https://issues.apache.org/jira/browse/FELIX-3883 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-4.2.0 Reporter: Richard S. Hall Assignee: Bob Paulin Fix For: framework-4.6.0 Currently, we hard code our OS and processor aliases for matching native code libraries. This is bad since it requires us to edit source code to add aliases. It would be better if we moved these to configuration properties, something like this: felix.native.os.[normalname] = alias1, alias2, etc. felix.native.arch.[normalname] = alias1, alias2, etc. More concretely: felix.native.os.win32 = Windows 8, Windows 7, Windows Vista felix.native.arch.x86 = i386, i486, i586 We could then use the properties to define as many normal names as we want and associate all their known aliases, so at run time all names could be normalized. We can include a default set of normal names and aliases in default.properties, but allow people to override any of them (or add new normal names/aliases) in config.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FELIX-3883) [Framework] Move OS and processor aliases to configuration properties
[ https://issues.apache.org/jira/browse/FELIX-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Paulin reassigned FELIX-3883: - Assignee: Bob Paulin [Framework] Move OS and processor aliases to configuration properties - Key: FELIX-3883 URL: https://issues.apache.org/jira/browse/FELIX-3883 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-4.2.0 Reporter: Richard S. Hall Assignee: Bob Paulin Fix For: framework-4.6.0 Currently, we hard code our OS and processor aliases for matching native code libraries. This is bad since it requires us to edit source code to add aliases. It would be better if we moved these to configuration properties, something like this: felix.native.os.[normalname] = alias1, alias2, etc. felix.native.arch.[normalname] = alias1, alias2, etc. More concretely: felix.native.os.win32 = Windows 8, Windows 7, Windows Vista felix.native.arch.x86 = i386, i486, i586 We could then use the properties to define as many normal names as we want and associate all their known aliases, so at run time all names could be normalized. We can include a default set of normal names and aliases in default.properties, but allow people to override any of them (or add new normal names/aliases) in config.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4696) Improve native OS version sanitation
[ https://issues.apache.org/jira/browse/FELIX-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270523#comment-14270523 ] Bob Paulin commented on FELIX-4696: --- Hi Felix. Sanitizing the Version makes sense to me. I think for the Native Capabilities I've decided to simply drop the classifier opting for a pattern of \\d+\\.?\\d*\\.?\\d* (See ExtentionManager.buildNativeCapabilites). I know the linux os versions often include a classifier. Do you think they are useful? Improve native OS version sanitation Key: FELIX-4696 URL: https://issues.apache.org/jira/browse/FELIX-4696 Project: Felix Issue Type: Improvement Components: Framework Affects Versions: framework-4.4.1 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: framework-4.6.0 Attachments: FELIX-4696.patch The Native OS version sanitation currently simply tries to parse the native OS version and if failing falls back to 0.0.0. I think it would be better to actually properly sanitize the version similar to what the DefaultMaven2OsgiConverter class of the Bundle Maven Plugin does. So for example, a FC9 version of 3.14.22-100.fc19.i686.PAE would then be converted to 3.14.22.100_fc19_i686_PAE which is much more suited to real world use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [Heads-up]: Felix framework release
My changes are good to go Karl. +1 (non-binding) - Bob On 1/8/2015 9:31 AM, Bob Paulin wrote: Karl, I should have it ready before the weekend. Thanks. - Bob On Thu, Jan 8, 2015 at 9:16 AM, Jean-Baptiste Onofré j...@nanthrax.net mailto:j...@nanthrax.net wrote: +1 (non binding). I'm testing two potential issues: 1/ the bundles cache get corrupted when we kill the framework java process (with a kill -9). Some bundles goes into inconsistent state. 2/ I have a NullPointerException on the ResolverImpl (on the toStringBlame() method): java.lang.NullPointerException at org.apache.felix.framework.resolver.ResolverImpl.toStringBlame(ResolverImpl.java:1671) It's not blocking for the release, and I need some time to create simple test cases and prepare patches. Regards JB On 01/08/2015 01:34 PM, Carsten Ziegeler wrote: Am 08.01.15 um 12:10 schrieb Karl Pauls: Looks like we are getting to the point where we should have a new framework release. If you still need something to get in first speak-up now - otherwise, I'm going to cut the release soonish. regards, Great, thanks Karl for taking this up. Right now we have 18 open issues scheduled for this release, but I don't think any of them is blocking us from releasing. +1 :) Carsten -- Jean-Baptiste Onofré jbono...@apache.org mailto:jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
[jira] [Resolved] (FELIX-4690) Some bundles containing native code can fail to start on Windows 7+
[ https://issues.apache.org/jira/browse/FELIX-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Paulin resolved FELIX-4690. --- Resolution: Fixed This is resolved with the fix for FELIX-3883. Added a test with rev 1650433 to confirm Windows7 resolves to windows7 not win. Some bundles containing native code can fail to start on Windows 7+ --- Key: FELIX-4690 URL: https://issues.apache.org/jira/browse/FELIX-4690 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-4.4.1 Environment: Windows 7, 8, 9 Reporter: Andrey Zelenchuk Assignee: Bob Paulin Priority: Minor Fix For: framework-4.6.0 Attachments: R4LibrabyClause-normalizeOSName.patch The fix of the FELIX-4534 is incomplete a little: Windows7 is still normalized to win instead of windows7. Bundles which have Windows7 in their manifest fail to start. *Workaround:* for bundle provider to use windows7 instead of Windows7 in a manifest. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FELIX-4690) Some bundles containing native code can fail to start on Windows 7+
[ https://issues.apache.org/jira/browse/FELIX-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Paulin reassigned FELIX-4690: - Assignee: Bob Paulin Some bundles containing native code can fail to start on Windows 7+ --- Key: FELIX-4690 URL: https://issues.apache.org/jira/browse/FELIX-4690 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-4.4.1 Environment: Windows 7, 8, 9 Reporter: Andrey Zelenchuk Assignee: Bob Paulin Priority: Minor Fix For: framework-4.6.0 Attachments: R4LibrabyClause-normalizeOSName.patch The fix of the FELIX-4534 is incomplete a little: Windows7 is still normalized to win instead of windows7. Bundles which have Windows7 in their manifest fail to start. *Workaround:* for bundle provider to use windows7 instead of Windows7 in a manifest. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4671) Provide an expression parser
[ https://issues.apache.org/jira/browse/FELIX-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270205#comment-14270205 ] Ferry Huberts commented on FELIX-4671: -- Please reopen, see https://issues.apache.org/jira/browse/FELIX-4697 Provide an expression parser Key: FELIX-4671 URL: https://issues.apache.org/jira/browse/FELIX-4671 Project: Felix Issue Type: New Feature Components: Gogo Runtime Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: gogo.runtime-0.14.0 Gogo provides no way to do arithmetic operations or to provide boolean operators. This makes writing scripted loops or conditions extremely difficult. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4697) Error parsing the default gosh_profile.
[
https://issues.apache.org/jira/browse/FELIX-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270178#comment-14270178
]
Ferry Huberts commented on FELIX-4697:
--
Just had it too. Have to revert back to 0.12.1
Error parsing the default gosh_profile.
---
Key: FELIX-4697
URL: https://issues.apache.org/jira/browse/FELIX-4697
Project: Felix
Issue Type: Bug
Components: Gogo Runtime
Affects Versions: gogo.runtime-0.14.0
Reporter: J.W. Janssen
It appears that the implementation of FELIX-4671 has caused an unexpected
side-effect in the parsing of the default {{gosh_profile}}. More
specifically: the Tokenizer now bails out on the following expression:
{code}
addcommand system (((${.context} bundles) 0) loadclass java.lang.System)
{code}
The reason for this is that the {{((}} makes the Tokenizer believe that it
should keep parsing until {{))}} is found, which isn't the case in the above
situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (FELIX-4583) [Core R6] Ensure that all OSGi Core R6 CT tests pass
[ https://issues.apache.org/jira/browse/FELIX-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved FELIX-4583. - Resolution: Fixed [Core R6] Ensure that all OSGi Core R6 CT tests pass Key: FELIX-4583 URL: https://issues.apache.org/jira/browse/FELIX-4583 Project: Felix Issue Type: Sub-task Components: Framework Reporter: David Bosschaert Assignee: David Bosschaert Fix For: framework-4.6.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [Heads-up]: Felix framework release
Great! And if I'm not mistaken, this release has full OSGi Core R6 support! https://issues.apache.org/jira/browse/FELIX-4502 Would be great if we can get this released! Thanks Karl! David On 8 January 2015 at 11:10, Karl Pauls karlpa...@gmail.com wrote: Looks like we are getting to the point where we should have a new framework release. If you still need something to get in first speak-up now - otherwise, I'm going to cut the release soonish. regards, Karl -- Karl Pauls karlpa...@gmail.com
[jira] [Resolved] (FELIX-4502) [Core R6] Provide an OSGi R6 compliant framework implementation
[ https://issues.apache.org/jira/browse/FELIX-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved FELIX-4502. - Resolution: Fixed [Core R6] Provide an OSGi R6 compliant framework implementation --- Key: FELIX-4502 URL: https://issues.apache.org/jira/browse/FELIX-4502 Project: Felix Issue Type: Improvement Components: Framework Affects Versions: framework-4.4.0 Reporter: David Bosschaert Fix For: framework-4.6.0 OSGi Core R6 compliance needs to be provided. This is an umbrella issue to track the necessary tasks to make Felix R6 compliant. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [Heads-up]: Felix framework release
Am 08.01.15 um 12:10 schrieb Karl Pauls: Looks like we are getting to the point where we should have a new framework release. If you still need something to get in first speak-up now - otherwise, I'm going to cut the release soonish. regards, Great, thanks Karl for taking this up. Right now we have 18 open issues scheduled for this release, but I don't think any of them is blocking us from releasing. +1 :) Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Commented] (FELIX-4757) Native Capabilities should allow OS and Processor alias to load from default and config properties
[ https://issues.apache.org/jira/browse/FELIX-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269285#comment-14269285 ] Richard S. Hall commented on FELIX-4757: The suggested approach is more similar to the approach for handling the auto-install/start properties where start-levels can be specified as part of the property. I doubt the processing overhead on this would be significant given the reasonably small size of strings we are talking about and the fact that it happens only on startup when lots of other stuff is going on anyway. One other benefit is that if the user wants to override/add an alias in config.properties, they can do it in a more targeted way. But, in the end, its your effort so I'll leave it up to you. Native Capabilities should allow OS and Processor alias to load from default and config properties -- Key: FELIX-4757 URL: https://issues.apache.org/jira/browse/FELIX-4757 Project: Felix Issue Type: Improvement Components: Framework Reporter: Bob Paulin Assignee: Bob Paulin Priority: Minor Fix For: framework-4.6.0 The initial implementation of the native os and processor aliases had them hard coded inside the NativeCodeClause Class. The aliases should be handled in a properties file outside the code to allow them to be overridden and make them easier to update within the framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4760) Support default/alternate values for variable substitution
Guillaume Nodet created FELIX-4760:
--
Summary: Support default/alternate values for variable substitution
Key: FELIX-4760
URL: https://issues.apache.org/jira/browse/FELIX-4760
Project: Felix
Issue Type: New Feature
Components: File Install, Utils
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
Fix For: fileinstall-3.4.4, utils-1.6.2
This should be done using {{:-}} and {{:+}} operators as done in {{gogo}} and
{{bash}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (FELIX-4759) Support env:XXX subtitution for environment variables
[ https://issues.apache.org/jira/browse/FELIX-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved FELIX-4759. Resolution: Fixed http://svn.apache.org/viewvc?view=revisionrevision=1650235 Support env:XXX subtitution for environment variables - Key: FELIX-4759 URL: https://issues.apache.org/jira/browse/FELIX-4759 Project: Felix Issue Type: New Feature Components: File Install, Utils Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: fileinstall-3.4.4, utils-1.6.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4760) Support default/alternate values for variable substitution
[
https://issues.apache.org/jira/browse/FELIX-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved FELIX-4760.
Resolution: Fixed
http://svn.apache.org/viewvc?view=revisionrevision=1650235
Support default/alternate values for variable substitution
--
Key: FELIX-4760
URL: https://issues.apache.org/jira/browse/FELIX-4760
Project: Felix
Issue Type: New Feature
Components: File Install, Utils
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
Fix For: fileinstall-3.4.4, utils-1.6.2
This should be done using {{:-}} and {{:+}} operators as done in {{gogo}} and
{{bash}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-4759) Support env:XXX subtitution for environment variables
Guillaume Nodet created FELIX-4759: -- Summary: Support env:XXX subtitution for environment variables Key: FELIX-4759 URL: https://issues.apache.org/jira/browse/FELIX-4759 Project: Felix Issue Type: New Feature Components: File Install, Utils Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: fileinstall-3.4.4, utils-1.6.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4583) [Core R6] Ensure that all OSGi Core R6 CT tests pass
[ https://issues.apache.org/jira/browse/FELIX-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269191#comment-14269191 ] Karl Pauls commented on FELIX-4583: --- I just made the security related parts pass in r1650249. [Core R6] Ensure that all OSGi Core R6 CT tests pass Key: FELIX-4583 URL: https://issues.apache.org/jira/browse/FELIX-4583 Project: Felix Issue Type: Sub-task Components: Framework Reporter: David Bosschaert Assignee: David Bosschaert Fix For: framework-4.6.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4579) [Core R6] Support Framework Extension Bundle Activators
[
https://issues.apache.org/jira/browse/FELIX-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved FELIX-4579.
---
Resolution: Fixed
Implemented (as in passes the ct) in r1650249. Please close this issue if it
works for you.
[Core R6] Support Framework Extension Bundle Activators
---
Key: FELIX-4579
URL: https://issues.apache.org/jira/browse/FELIX-4579
Project: Felix
Issue Type: Sub-task
Components: Framework
Reporter: David Bosschaert
Assignee: Karl Pauls
Fix For: framework-4.6.0
See section 3.15.3 of the Core R6 spec for details.
The manifest header for these activators is:
{{ExtensionBundle-Activator: com.acme.Activator}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[Heads-up]: Felix framework release
Looks like we are getting to the point where we should have a new framework release. If you still need something to get in first speak-up now - otherwise, I'm going to cut the release soonish. regards, Karl -- Karl Pauls karlpa...@gmail.com
[jira] [Commented] (FELIX-4757) Native Capabilities should allow OS and Processor alias to load from default and config properties
[ https://issues.apache.org/jira/browse/FELIX-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269297#comment-14269297 ] Bob Paulin commented on FELIX-4757: --- Richard thank you for the feedback. I think having the ability to be more targeted on the overriding of a specific OS or Processor is a big selling point of the approach in FELIX-3883 that I did not consider. It's probably worth a little extra overhead to make this easier on the end user. Let me see if everyone is willing to hold up a day or 2 on the framework release so I can try to get this in. Thanks again. Native Capabilities should allow OS and Processor alias to load from default and config properties -- Key: FELIX-4757 URL: https://issues.apache.org/jira/browse/FELIX-4757 Project: Felix Issue Type: Improvement Components: Framework Reporter: Bob Paulin Assignee: Bob Paulin Priority: Minor Fix For: framework-4.6.0 The initial implementation of the native os and processor aliases had them hard coded inside the NativeCodeClause Class. The aliases should be handled in a properties file outside the code to allow them to be overridden and make them easier to update within the framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [Heads-up]: Felix framework release
Well, if you could get it done by tomorrow that would be great (as I'd like to cut the release of the weekend). regards, Karl On Thu, Jan 8, 2015 at 2:43 PM, Bob Paulin b...@bobpaulin.com wrote: Hi Karl, Don't want to be late for the train but I'm working through some feedback from Richard on FELIX-4757 FELIX-3883 that I'd like to get in. Probably just need today and tomorrow to complete it. Perhaps pencil in a release on Monday? Let me know if there are concerns with waiting. Thanks! - Bob On 1/8/2015 6:34 AM, Carsten Ziegeler wrote: Am 08.01.15 um 12:10 schrieb Karl Pauls: Looks like we are getting to the point where we should have a new framework release. If you still need something to get in first speak-up now - otherwise, I'm going to cut the release soonish. regards, Great, thanks Karl for taking this up. Right now we have 18 open issues scheduled for this release, but I don't think any of them is blocking us from releasing. +1 :) Carsten -- Karl Pauls karlpa...@gmail.com
Re: [Heads-up]: Felix framework release
+1 (non binding). I'm testing two potential issues: 1/ the bundles cache get corrupted when we kill the framework java process (with a kill -9). Some bundles goes into inconsistent state. 2/ I have a NullPointerException on the ResolverImpl (on the toStringBlame() method): java.lang.NullPointerException at org.apache.felix.framework.resolver.ResolverImpl.toStringBlame(ResolverImpl.java:1671) It's not blocking for the release, and I need some time to create simple test cases and prepare patches. Regards JB On 01/08/2015 01:34 PM, Carsten Ziegeler wrote: Am 08.01.15 um 12:10 schrieb Karl Pauls: Looks like we are getting to the point where we should have a new framework release. If you still need something to get in first speak-up now - otherwise, I'm going to cut the release soonish. regards, Great, thanks Karl for taking this up. Right now we have 18 open issues scheduled for this release, but I don't think any of them is blocking us from releasing. +1 :) Carsten -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
