[GitHub] [felix-atomos] tjwatson merged pull request #24: FELIX-6283 - leave class resources out of image
tjwatson merged pull request #24: URL: https://github.com/apache/felix-atomos/pull/24 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [felix-atomos] tjwatson opened a new pull request #24: FELIX-6283 - leave class resources out of image
tjwatson opened a new pull request #24: URL: https://github.com/apache/felix-atomos/pull/24 There should be no need to actually include the class resources in the native image. It only bloats the size of the image. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (FELIX-6283) Declarative Services components are not getting activated
[ https://issues.apache.org/jira/browse/FELIX-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6283. --- Resolution: Fixed > Declarative Services components are not getting activated > - > > Key: FELIX-6283 > URL: https://issues.apache.org/jira/browse/FELIX-6283 > Project: Felix > Issue Type: Bug > Components: Atomos > Environment: Tested on MacOS 10.14.6 using GraalVM CE 20.1.0 Java 11 >Reporter: Jörg Wille >Assignee: Tom Watson >Priority: Major > > [Simple OSGi application|https://github.com/joerg-wille/OSGiAOT] using DS to > create gogo command is not working as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FELIX-6283) Declarative Services components are not getting activated
[ https://issues.apache.org/jira/browse/FELIX-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson reassigned FELIX-6283: - Assignee: Tom Watson > Declarative Services components are not getting activated > - > > Key: FELIX-6283 > URL: https://issues.apache.org/jira/browse/FELIX-6283 > Project: Felix > Issue Type: Bug > Components: Atomos > Environment: Tested on MacOS 10.14.6 using GraalVM CE 20.1.0 Java 11 >Reporter: Jörg Wille >Assignee: Tom Watson >Priority: Major > > [Simple OSGi application|https://github.com/joerg-wille/OSGiAOT] using DS to > create gogo command is not working as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FELIX-6283) Declarative Services components are not getting activated
[ https://issues.apache.org/jira/browse/FELIX-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121321#comment-17121321 ] Tom Watson commented on FELIX-6283: --- This should be fixed now. > Declarative Services components are not getting activated > - > > Key: FELIX-6283 > URL: https://issues.apache.org/jira/browse/FELIX-6283 > Project: Felix > Issue Type: Bug > Components: Atomos > Environment: Tested on MacOS 10.14.6 using GraalVM CE 20.1.0 Java 11 >Reporter: Jörg Wille >Assignee: Tom Watson >Priority: Major > > [Simple OSGi application|https://github.com/joerg-wille/OSGiAOT] using DS to > create gogo command is not working as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [felix-atomos] tjwatson merged pull request #23: FELIX-6283 - Use correct path for including resources
tjwatson merged pull request #23: URL: https://github.com/apache/felix-atomos/pull/23 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [felix-atomos] tjwatson opened a new pull request #23: FELIX-6283 - Use correct path for including resources
tjwatson opened a new pull request #23: URL: https://github.com/apache/felix-atomos/pull/23 The Atomos index was updated to only index paths that have duplicates. All other resources are expected to come from the root of the image (or classpath). This fix ensures the correct resource path is used to include the unique paths from the root of the image This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (FELIX-6283) Declarative Services components are not getting activated
[
https://issues.apache.org/jira/browse/FELIX-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121245#comment-17121245
]
Tom Watson commented on FELIX-6283:
---
The same problem exists in the {{atomos.examples.substrate.maven}} example.
I'm pretty sure the problem is in the interaction with the changes to the
Atomos index implementation which expects all resources except for duplicate
resources to be located from the root of the image. I think now the root of
the image is missing a bunch of resources by default.
> Declarative Services components are not getting activated
> -
>
> Key: FELIX-6283
> URL: https://issues.apache.org/jira/browse/FELIX-6283
> Project: Felix
> Issue Type: Bug
> Components: Atomos
> Environment: Tested on MacOS 10.14.6 using GraalVM CE 20.1.0 Java 11
>Reporter: Jörg Wille
>Priority: Major
>
> [Simple OSGi application|https://github.com/joerg-wille/OSGiAOT] using DS to
> create gogo command is not working as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (FELIX-6283) Declarative Services components are not getting activated
Jörg Wille created FELIX-6283: - Summary: Declarative Services components are not getting activated Key: FELIX-6283 URL: https://issues.apache.org/jira/browse/FELIX-6283 Project: Felix Issue Type: Bug Components: Atomos Environment: Tested on MacOS 10.14.6 using GraalVM CE 20.1.0 Java 11 Reporter: Jörg Wille [Simple OSGi application|https://github.com/joerg-wille/OSGiAOT] using DS to create gogo command is not working as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FELIX-6282) Felix Connect R7 support
[
https://issues.apache.org/jira/browse/FELIX-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120926#comment-17120926
]
Pierre De Rop commented on FELIX-6282:
--
Added PR #24.
> Felix Connect R7 support
>
>
> Key: FELIX-6282
> URL: https://issues.apache.org/jira/browse/FELIX-6282
> Project: Felix
> Issue Type: Improvement
> Components: Connect
>Affects Versions: connect-0.2.0
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
>Priority: Major
>
> The Felix Connect library seems to be almost ready for OSGi R7 support.
> At least, modifying the project's pom in order to depend on
> org.osgi:osgi.core:7.0.0 allows to use recent declarative service,
> configadmin, metatype, etc ...
> There is one minor issue: the support for FrameworkWiringDTO is missing (even
> if it's not really useful in the context of felix connect): in the following
> code, the adapt method returns null:
> {code:java}
> Bundle system = _ctx.getBundle(0);
> FrameworkWiringDTO wiring = system.adapt(FrameworkWiringDTO.class);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [felix-dev] pderop opened a new pull request #24: [FELIX-6282] Added core R7 dependency in pom. Exports R7 api to allow …
pderop opened a new pull request #24: URL: https://github.com/apache/felix-dev/pull/24 …to resolve the connect bundle from an OBR. Avoid NPE when adapting system bundle to FrameworkWiringDTO. This PR provides three things: 1) in the connect/pom.xml, depend on org.osgi:osgi.core:7.0.0 2) you will notice another thing: in the pom.xml, the OSGI and Felix Connect APIs are now exported. You might wonder why: It is just to allow to resolve the Felix Connect bundle as well as OSGI API from an OBR. In my case, some or our application dependencies are calculated by an offline OSGI resolver that pulls dependencies from an OBR. So far, it was not possible to resolve the Apache Felix Connect bundle from the OBR, because all packages were private. Exporting the connect packages (as well as the OSGI packages) allows to make the bundle resolvable from OBR. 3) Added small patch in DTOFactory.java to add support for FrameworkWiringDTO. It's probably useless in context on FelixConnect to support such dto, but at least the patch avoids an NPE when someone tries to adapt the FrameworkWiringDTO from the system bundle. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (FELIX-6282) Felix Connect R7 support
Pierre De Rop created FELIX-6282:
Summary: Felix Connect R7 support
Key: FELIX-6282
URL: https://issues.apache.org/jira/browse/FELIX-6282
Project: Felix
Issue Type: Improvement
Components: Connect
Affects Versions: connect-0.2.0
Reporter: Pierre De Rop
Assignee: Pierre De Rop
The Felix Connect library seems to be almost ready for OSGi R7 support.
At least, modifying the project's pom in order to depend on
org.osgi:osgi.core:7.0.0 allows to use recent declarative service, configadmin,
metatype, etc ...
There is one minor issue: the support for FrameworkWiringDTO is missing (even
if it's not really useful in the context of felix connect): in the following
code, the adapt method returns null:
{code:java}
Bundle system = _ctx.getBundle(0);
FrameworkWiringDTO wiring = system.adapt(FrameworkWiringDTO.class);
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
