[
https://issues.apache.org/jira/browse/FELIX-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-5435:
Fix Version/s: configadmin-1.8.14
> Service does not get loaded with updated properties that
[
https://issues.apache.org/jira/browse/FELIX-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-5443:
Fix Version/s: configadmin-1.8.14
> Frequent Changes cause UpdateThread to ConcurrentModific
[
https://issues.apache.org/jira/browse/FELIX-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-5474:
Issue Type: Improvement (was: Bug)
> Do not call no-arg Bundle.getHeaders() method
> --
[
https://issues.apache.org/jira/browse/FELIX-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-5474:
Fix Version/s: scr-2.0.8
> Do not call no-arg Bundle.getHeaders() method
> -
[
https://issues.apache.org/jira/browse/FELIX-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-5474:
Fix Version/s: scr-2.1.0
> Do not call no-arg Bundle.getHeaders() method
> -
[
https://issues.apache.org/jira/browse/FELIX-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-5374:
Fix Version/s: scr-2.0.8
> Reduce severity of log message from SCR when there is no metatype
[
https://issues.apache.org/jira/browse/FELIX-5459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-5459:
Fix Version/s: scr-2.0.8
> Use Java 6 as minimum version
> -
>
>
I assume you're talking about DS, right?
I'll create a branch similar to what we did for config admin
Carsten
Thomas Watson wrote
> Changed subject to stop hijacking the discussion on releasing provisional
> API from the org.osgi namespace.
>
> How do we come to an agreement on what branch to d
[
https://issues.apache.org/jira/browse/FELIX-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799549#comment-15799549
]
Andreas Gebhardt commented on FELIX-5470:
-
Thanks Stefan
> website documentation
[
https://issues.apache.org/jira/browse/FELIX-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799473#comment-15799473
]
Pierre De Rop commented on FELIX-5471:
--
Hi Jeroen,
I have committed a patch in rv 17
[
https://issues.apache.org/jira/browse/FELIX-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799473#comment-15799473
]
Pierre De Rop edited comment on FELIX-5471 at 1/4/17 9:57 PM:
--
Changed subject to stop hijacking the discussion on releasing provisional
API from the org.osgi namespace.
How do we come to an agreement on what branch to do OSGi R-next work in? I
would prefer to keep trunk in a releasable state based on the latest
published specification from OSGi. But we hav
[
https://issues.apache.org/jira/browse/FELIX-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Watson resolved FELIX-5474.
--
Resolution: Fixed
I replaced all calls to getHeaders() with getHeaders(""). I also replaced all
[
https://issues.apache.org/jira/browse/FELIX-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Watson reassigned FELIX-5474:
Assignee: Thomas Watson
> Do not call no-arg Bundle.getHeaders() method
> -
Github user fhuberts closed the pull request at:
https://github.com/apache/felix/pull/67
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
[
https://issues.apache.org/jira/browse/FELIX-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed FELIX-5478.
> Dependency on snakeyaml should be private
> -
>
>
[
https://issues.apache.org/jira/browse/FELIX-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen resolved FELIX-5478.
--
Resolution: Duplicate
> Dependency on snakeyaml should be private
>
[
https://issues.apache.org/jira/browse/FELIX-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798714#comment-15798714
]
David Leangen commented on FELIX-5478:
--
No need for a separate issue.
> Dependency o
David Leangen created FELIX-5481:
Summary: Various updates to Schematizer
Key: FELIX-5481
URL: https://issues.apache.org/jira/browse/FELIX-5481
Project: Felix
Issue Type: Improvement
David Leangen created FELIX-5480:
Summary: Serializer should be more lenient with trailing commas
Key: FELIX-5480
URL: https://issues.apache.org/jira/browse/FELIX-5480
Project: Felix
Issue Ty
David Leangen created FELIX-5479:
Summary: Serializer should be more lenient with trailing commas
Key: FELIX-5479
URL: https://issues.apache.org/jira/browse/FELIX-5479
Project: Felix
Issue Ty
David Leangen created FELIX-5478:
Summary: Dependency on snakeyaml should be private
Key: FELIX-5478
URL: https://issues.apache.org/jira/browse/FELIX-5478
Project: Felix
Issue Type: Bug
David Leangen created FELIX-5477:
Summary: DTOs should allow lambdas
Key: FELIX-5477
URL: https://issues.apache.org/jira/browse/FELIX-5477
Project: Felix
Issue Type: Bug
Components:
David Leangen created FELIX-5476:
Summary: Serializer does not accept empty values
Key: FELIX-5476
URL: https://issues.apache.org/jira/browse/FELIX-5476
Project: Felix
Issue Type: Bug
David Leangen created FELIX-5475:
Summary: Allow the use of DTO.class to signal that an Object
should be treated as a DTO.
Key: FELIX-5475
URL: https://issues.apache.org/jira/browse/FELIX-5475
Project
Congratulations and welcome, Stefan !
Keep the good stuff coming.
Regards
Felix
> Am 23.12.2016 um 11:47 schrieb Stefan Seifert :
>
> thanks!
>
> it is a tradition that a new committer introduces himself, so here are some
> words about myself:
>
> i'm living in berlin, and using OSGi and Fel
Hi
As of now, we don’t have an official branch policy. In fact we had a discussion
before and we decided against such.
So I would think that we should continue releasing from trunk and from trunk
only.
As such I like Tom’s proposal for a R-Next working branch. And since OSGi
generally release
My preference would be to do new osgi R-Next work in a dedicated feature
branch instead of directly in trunk. That way trunk remains releasable at
all times. But if we want to instead branch each project when its trunk
version becomes unreleasable then I guess that is fine, but it does seem
confu
+1
Carsten
David Bosschaert wrote
> Hi Stefan,
>
> This sounds like a useful change to me - the change will mean less
> maintenance which is always good IMHO.
>
> David
>
> On 4 January 2017 at 10:41, Stefan Seifert wrote:
>
>> the list of committers [1] and PMC members [2] on the felix site
Hi Stefan,
This sounds like a useful change to me - the change will mean less
maintenance which is always good IMHO.
David
On 4 January 2017 at 10:41, Stefan Seifert wrote:
> the list of committers [1] and PMC members [2] on the felix site is
> outdated.
>
> perhaps we should just replace it w
the list of committers [1] and PMC members [2] on the felix site is outdated.
perhaps we should just replace it with a link to the apache phonebook?
list of chair, PMC members, committers:
https://people.apache.org/phonebook.html?pmc=felix
what we not see no this list but on the information is a
I understand that the OSGi alliance would not release an unfinished spec .. but
I think it would not need to.
What I propose instead is that the alliance develops specs like we develop open
source software. The spec could be defined in a maven project on github.
There would be a daily build of
32 matches
Mail list logo
