[jira] [Commented] (FELIX-1974) Implement boot class path extension bundle support
[ https://issues.apache.org/jira/browse/FELIX-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218042#comment-16218042 ] Thomas Watson commented on FELIX-1974: -- FYI, R7 will drop boot classpath extensions altogether. As you say Java 9 make implementation nearly impossible. > Implement boot class path extension bundle support > -- > > Key: FELIX-1974 > URL: https://issues.apache.org/jira/browse/FELIX-1974 > Project: Felix > Issue Type: New Feature > Components: Framework >Affects Versions: framework-0.8.0, framework-1.0.0, framework-1.0.1, > framework-1.0.3, framework-1.0.4, framework-1.2.0, framework-1.2.1, > framework-1.2.2, framework-1.4.0, framework-1.4.1, framework-1.6.0, > framework-1.6.1, framework-1.8.0, framework-1.8.1, framework-2.0.0, > framework-2.0.1, framework-2.0.2 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Minor > Fix For: framework-5.6.10 > > > This issue is described in section 3.14 of the OSGi R4 specification. The > main jist is to provide a standard mechanism to place classes on the JVM boot > class path. This mechanisms is modeled as bundle fragments, but it not really > completely related to it. The boot class path aspect is likely to be > dependent on specific JVMs. Please note that we have support for "normal" > extension bundles already. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[RESULT] [VOTE] Release Gogo Runtime 1.0.10 and Gogo JLine 1.0.10
Closing the vote with 3 +1s and no other votes. I'll publish the artifacts asap. Cheers, Guillaume 2017-10-18 14:39 GMT+02:00 Guillaume Nodet : > The following bugs are fixed: > 028349068 [FELIX-5715] Central point to allow customization of security > related checks > > 81fb98f6d [FELIX-5706] Unable to access DTO fields using reflection > > 10982fc79 Use english locale to convert method names > > ceaeb4170 [FELIX-5651] Disable log history in Gogo console > > dea697ae7 [FELIX-5714] ArrayIndexOutOfBoundsException running history | > grep > > 479b59c00 [FELIX-5705] Provide completion for SCR commands > > 3917ffc14 [FELIX-5635][gogo][jline] The "cd" command should not attempt > to complete multiple directories > > > The candidate bundles are uploaded to the usual staging area: > https://repository.apache.org/content/repositories/orgapachefelix-1202 > > Please review and vote ! > > Cheers, > Guillaume Nodet > > -- Guillaume Nodet
[jira] [Created] (FELIX-5728) Whong default for outputDirectory property
Vladimir Smirnov created FELIX-5728:
---
Summary: Whong default for outputDirectory property
Key: FELIX-5728
URL: https://issues.apache.org/jira/browse/FELIX-5728
Project: Felix
Issue Type: Bug
Components: SCR Tooling
Affects Versions: maven-scr-plugin-1.25.0, maven-scr-plugin 1.15.0
Reporter: Vladimir Smirnov
Documentation at
http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/apache-felix-maven-scr-plugin-use.html
declare
Default for outputDirectory property:
*${project.build.directory}/scr-plugin-generated*.
Looks like it should be changed to *${project.build.outputDirectory}* according
with FELIX-4241
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] felix pull request #125: [FELIX-5724] Handle CM_DELETED properly (+tests)
Github user grgrzybek closed the pull request at: https://github.com/apache/felix/pull/125 ---
[jira] [Commented] (FELIX-5710) Improve Java9 support
[ https://issues.apache.org/jira/browse/FELIX-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216677#comment-16216677 ] Karl Pauls commented on FELIX-5710: --- I think I'm getting closer to have what I want implemented. With the current snapshot, I at least by and large pass the r6 ct using: java --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED There are 3 failing tests but one is a known ct bug and another one is related to the ct not expecting java9 - hence, only one seems like it really is failing. I have to investigate that last one some more but I think we are in a much better shape now. > Improve Java9 support > - > > Key: FELIX-5710 > URL: https://issues.apache.org/jira/browse/FELIX-5710 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-5.6.8 >Reporter: Karl Pauls >Assignee: Karl Pauls > Fix For: framework-5.6.10 > > > There are a couple of areas where we need to (or at least can) improve things > for better java9 support. This is going to be the umbrella issue (specific > tasks will be created as subtasks). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (FELIX-1974) Implement boot class path extension bundle support
[ https://issues.apache.org/jira/browse/FELIX-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved FELIX-1974. --- Resolution: Workaround I added a service loader lookup for a org.apache.felix.framework.ext.ClassPathExtenderFactory service in r1813157. The idea is that if we find a service for that interface, we will call its getExtender() method with "null" to see if it supports boot class path extensions. If that returns an extender, we will use it to append boot class path extension bundles via the add(File) method of the returned extender. In other words, we don't provide support for this OOTB but somebody could extend the framework to add support. As this feature is optional and has become close to impossible to support on java9 (without command line switch support etc.) I think this is good enough. At a minimum, I don't plan to work on this anymore. > Implement boot class path extension bundle support > -- > > Key: FELIX-1974 > URL: https://issues.apache.org/jira/browse/FELIX-1974 > Project: Felix > Issue Type: New Feature > Components: Framework >Affects Versions: framework-0.8.0, framework-1.0.0, framework-1.0.1, > framework-1.0.3, framework-1.0.4, framework-1.2.0, framework-1.2.1, > framework-1.2.2, framework-1.4.0, framework-1.4.1, framework-1.6.0, > framework-1.6.1, framework-1.8.0, framework-1.8.1, framework-2.0.0, > framework-2.0.1, framework-2.0.2 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Minor > Fix For: framework-5.6.10 > > > This issue is described in section 3.14 of the OSGi R4 specification. The > main jist is to provide a standard mechanism to place classes on the JVM boot > class path. This mechanisms is modeled as bundle fragments, but it not really > completely related to it. The boot class path aspect is likely to be > dependent on specific JVMs. Please note that we have support for "normal" > extension bundles already. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FELIX-1974) Implement boot class path extension bundle support
[ https://issues.apache.org/jira/browse/FELIX-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated FELIX-1974: -- Fix Version/s: framework-5.6.10 > Implement boot class path extension bundle support > -- > > Key: FELIX-1974 > URL: https://issues.apache.org/jira/browse/FELIX-1974 > Project: Felix > Issue Type: New Feature > Components: Framework >Affects Versions: framework-0.8.0, framework-1.0.0, framework-1.0.1, > framework-1.0.3, framework-1.0.4, framework-1.2.0, framework-1.2.1, > framework-1.2.2, framework-1.4.0, framework-1.4.1, framework-1.6.0, > framework-1.6.1, framework-1.8.0, framework-1.8.1, framework-2.0.0, > framework-2.0.1, framework-2.0.2 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Minor > Fix For: framework-5.6.10 > > > This issue is described in section 3.14 of the OSGi R4 specification. The > main jist is to provide a standard mechanism to place classes on the JVM boot > class path. This mechanisms is modeled as bundle fragments, but it not really > completely related to it. The boot class path aspect is likely to be > dependent on specific JVMs. Please note that we have support for "normal" > extension bundles already. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FELIX-1974) Implement boot class path extension bundle support
[ https://issues.apache.org/jira/browse/FELIX-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated FELIX-1974: -- Summary: Implement boot class path extension bundle support (was: Implement boot class path extension bundles) > Implement boot class path extension bundle support > -- > > Key: FELIX-1974 > URL: https://issues.apache.org/jira/browse/FELIX-1974 > Project: Felix > Issue Type: New Feature > Components: Framework >Affects Versions: framework-0.8.0, framework-1.0.0, framework-1.0.1, > framework-1.0.3, framework-1.0.4, framework-1.2.0, framework-1.2.1, > framework-1.2.2, framework-1.4.0, framework-1.4.1, framework-1.6.0, > framework-1.6.1, framework-1.8.0, framework-1.8.1, framework-2.0.0, > framework-2.0.1, framework-2.0.2 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Minor > > This issue is described in section 3.14 of the OSGi R4 specification. The > main jist is to provide a standard mechanism to place classes on the JVM boot > class path. This mechanisms is modeled as bundle fragments, but it not really > completely related to it. The boot class path aspect is likely to be > dependent on specific JVMs. Please note that we have support for "normal" > extension bundles already. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
