[jira] [Commented] (FELIX-5652) Felix Framework hangs on shutdown

[Karl Pauls (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067301#comment-16067301
 ] 

Karl Pauls commented on FELIX-5652:
---

I don't think so, what are you trying to build? 

However, I just pushed a SNAPSHOT - hence, just use 5.7.0-SNAPSHOT and you 
should get the latest version (with the fix).

> Felix Framework hangs on shutdown
> -
>
> Key: FELIX-5652
> URL: https://issues.apache.org/jira/browse/FELIX-5652
> Project: Felix
>  Issue Type: Bug
>  Components: Framework
>Affects Versions: framework-5.6.2, framework-5.6.4
>Reporter: Florian Brunner
>Assignee: Karl Pauls
>Priority: Blocker
> Fix For: framework-5.6.6
>
> Attachments: felix-5652-v4.6.0.zip, felix-5652-v5.6.2.zip
>
>
> When shutting down the Felix Framework the process hangs for about 1 minute 
> or so.
> When running with the debugger, NetBeans shows 8 FelixResolver threads still 
> running (my machine has 8 cores, the number might be related).
> The issue did not occur with v4.6.0



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (FELIX-5652) Felix Framework hangs on shutdown

[Florian Brunner (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067217#comment-16067217
 ] 

Florian Brunner edited comment on FELIX-5652 at 6/28/17 9:07 PM:
-

[~karlpauls] : Thanks a lot!

The Apache Felix build failed however with:

{quote}Failed to execute goal on project org.apache.felix.converter: Could not 
resolve dependencies for project 
org.apache.felix:org.apache.felix.converter:jar:0.1.0-SNAPSHOT: Could not find 
artifact org.osgi:org.osgi.util.converter:jar:1.0.0-SNAPSHOT in nexus {quote}

Is there an additional Maven Repo I need to configure in Nexus?

Or can I get the latest build from a Maven Repo?


was (Author: puce):
[~karlpauls] : The build failed with:

{quote}Failed to execute goal on project org.apache.felix.converter: Could not 
resolve dependencies for project 
org.apache.felix:org.apache.felix.converter:jar:0.1.0-SNAPSHOT: Could not find 
artifact org.osgi:org.osgi.util.converter:jar:1.0.0-SNAPSHOT in nexus {quote}

Is there an additional Maven Repo I need to configure in Nexus?

Or can I get the latest build from a Maven Repo?

> Felix Framework hangs on shutdown
> -
>
> Key: FELIX-5652
> URL: https://issues.apache.org/jira/browse/FELIX-5652
> Project: Felix
>  Issue Type: Bug
>  Components: Framework
>Affects Versions: framework-5.6.2, framework-5.6.4
>Reporter: Florian Brunner
>Assignee: Karl Pauls
>Priority: Blocker
> Fix For: framework-5.6.6
>
> Attachments: felix-5652-v4.6.0.zip, felix-5652-v5.6.2.zip
>
>
> When shutting down the Felix Framework the process hangs for about 1 minute 
> or so.
> When running with the debugger, NetBeans shows 8 FelixResolver threads still 
> running (my machine has 8 cores, the number might be related).
> The issue did not occur with v4.6.0



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (FELIX-5652) Felix Framework hangs on shutdown

[Florian Brunner (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067217#comment-16067217
 ] 

Florian Brunner edited comment on FELIX-5652 at 6/28/17 9:04 PM:
-

[~karlpauls] : The build failed with:

{quote}Failed to execute goal on project org.apache.felix.converter: Could not 
resolve dependencies for project 
org.apache.felix:org.apache.felix.converter:jar:0.1.0-SNAPSHOT: Could not find 
artifact org.osgi:org.osgi.util.converter:jar:1.0.0-SNAPSHOT in nexus {quote}

Is there an additional Maven Repo I need to configure in Nexus?

Or can I get the latest build from a Maven Repo?


was (Author: puce):
@karlpauls: The build failed with:

{quote}Failed to execute goal on project org.apache.felix.converter: Could not 
resolve dependencies for project 
org.apache.felix:org.apache.felix.converter:jar:0.1.0-SNAPSHOT: Could not find 
artifact org.osgi:org.osgi.util.converter:jar:1.0.0-SNAPSHOT in nexus {quote}

Is there an additional Maven Repo I need to configure in Nexus?

Or can I get the latest build from a Maven Repo?

> Felix Framework hangs on shutdown
> -
>
> Key: FELIX-5652
> URL: https://issues.apache.org/jira/browse/FELIX-5652
> Project: Felix
>  Issue Type: Bug
>  Components: Framework
>Affects Versions: framework-5.6.2, framework-5.6.4
>Reporter: Florian Brunner
>Assignee: Karl Pauls
>Priority: Blocker
> Fix For: framework-5.6.6
>
> Attachments: felix-5652-v4.6.0.zip, felix-5652-v5.6.2.zip
>
>
> When shutting down the Felix Framework the process hangs for about 1 minute 
> or so.
> When running with the debugger, NetBeans shows 8 FelixResolver threads still 
> running (my machine has 8 cores, the number might be related).
> The issue did not occur with v4.6.0



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FELIX-5652) Felix Framework hangs on shutdown

[Florian Brunner (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067217#comment-16067217
 ] 

Florian Brunner commented on FELIX-5652:


@karlpauls: The build failed with:

{quote}Failed to execute goal on project org.apache.felix.converter: Could not 
resolve dependencies for project 
org.apache.felix:org.apache.felix.converter:jar:0.1.0-SNAPSHOT: Could not find 
artifact org.osgi:org.osgi.util.converter:jar:1.0.0-SNAPSHOT in nexus {quote}

Is there an additional Maven Repo I need to configure in Nexus?

Or can I get the latest build from a Maven Repo?

> Felix Framework hangs on shutdown
> -
>
> Key: FELIX-5652
> URL: https://issues.apache.org/jira/browse/FELIX-5652
> Project: Felix
>  Issue Type: Bug
>  Components: Framework
>Affects Versions: framework-5.6.2, framework-5.6.4
>Reporter: Florian Brunner
>Assignee: Karl Pauls
>Priority: Blocker
> Fix For: framework-5.6.6
>
> Attachments: felix-5652-v4.6.0.zip, felix-5652-v5.6.2.zip
>
>
> When shutting down the Felix Framework the process hangs for about 1 minute 
> or so.
> When running with the debugger, NetBeans shows 8 FelixResolver threads still 
> running (my machine has 8 cores, the number might be related).
> The issue did not occur with v4.6.0



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Apache Felix Dependency Manager Release R11

[Cédric Dos Santos]

+1 (non binding)

2017-06-28 10:06 GMT+02:00 Jean-Baptiste Onofré :

> +1 (binding)
>
> Regards
> JB
>
>
> On 06/27/2017 03:13 PM, fleygues wrote:
>
>> +1
>>
>> Congratulations.
>>
>> Pierre De Rop wrote:
>>
>>> Hello all,
>>>
>>> After a failed attempt to release the DM-R10 release, I would like to
>>> call
>>> for a new vote on the Dependency Manager toplevel release R11.
>>>
>>> The following issues were solved:
>>>
>>> ** Bug
>>>  * [FELIX-5630] - NullObject is created for a required dependency if
>>> the
>>> component is removed and added again to the dependency manager
>>>  * [FELIX-5636] - Component of aspect service does not have any
>>> service
>>> properties anymore
>>>  * [FELIX-5657] - DM released sources can't be rebuilt
>>>
>>> ** Improvement
>>>  * [FELIX-5619] - MultiProperyFilterIndex memory consumption
>>>  * [FELIX-5623] - Improve performance of ComponentImpl.getName method
>>>  * [FELIX-5650] - Support latest version of Gogo
>>>  * [FELIX-5653] - Simplify DM-Lambda samples
>>>  * [FELIX-5658] - Include poms in dm artifacts
>>>
>>> You can use this UNIX script to download the release and verify the
>>> signatures:
>>>
>>>
>>> http://svn.apache.org/repos/asf/felix/trunk/dependencymanage
>>> r/release/check_staged_release.sh
>>>
>>> Usage:
>>>
>>>  sh check_staged_release.sh r11 /tmp/felix-staging
>>>
>>> This script, unlike the original Felix check_stage_release.sh, is
>>> specific
>>> to the new Dependency Manager release process (see FELIX-4818) and will
>>> download staging from https://dist.apache.org/repos/dist/dev/felix
>>> instead
>>> of http://repository.apache.org/content/repositories.
>>>
>>> To rebuild the DM binaries from the source, you can then refer to
>>> https://svn.apache.org/repos/asf/felix/trunk/dependencymanag
>>> er/release/resources/src/README.src
>>>
>>>
>>> Please vote to approve this release:
>>>
>>> [ ] +1 Approve the release
>>> [ ] -1 Veto the release (please provide specific comments)
>>>
>>>
>>> Many thanks;
>>>
>>> regards;
>>> /Pierre
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Apache Felix Dependency Manager Release R11

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On 06/27/2017 03:13 PM, fleygues wrote:

+1

Congratulations.

Pierre De Rop wrote:

Hello all,

After a failed attempt to release the DM-R10 release, I would like to call
for a new vote on the Dependency Manager toplevel release R11.

The following issues were solved:

** Bug
 * [FELIX-5630] - NullObject is created for a required dependency if the
component is removed and added again to the dependency manager
 * [FELIX-5636] - Component of aspect service does not have any service
properties anymore
 * [FELIX-5657] - DM released sources can't be rebuilt

** Improvement
 * [FELIX-5619] - MultiProperyFilterIndex memory consumption
 * [FELIX-5623] - Improve performance of ComponentImpl.getName method
 * [FELIX-5650] - Support latest version of Gogo
 * [FELIX-5653] - Simplify DM-Lambda samples
 * [FELIX-5658] - Include poms in dm artifacts

You can use this UNIX script to download the release and verify the
signatures:


http://svn.apache.org/repos/asf/felix/trunk/dependencymanager/release/check_staged_release.sh 



Usage:

 sh check_staged_release.sh r11 /tmp/felix-staging

This script, unlike the original Felix check_stage_release.sh, is specific
to the new Dependency Manager release process (see FELIX-4818) and will
download staging from https://dist.apache.org/repos/dist/dev/felix instead
of http://repository.apache.org/content/repositories.

To rebuild the DM binaries from the source, you can then refer to
https://svn.apache.org/repos/asf/felix/trunk/dependencymanager/release/resources/src/README.src 




Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)


Many thanks;

regards;
/Pierre





--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Felix Dependency Manager Release R11

[Clement Escoffier]

+1,

Regards,

Clement

> On 28 Jun 2017, at 09:52, David Bosschaert  wrote:
> 
> +1
> 
> David
> 
> On 27 June 2017 at 09:17, Pierre De Rop  wrote:
> 
>> Hello all,
>> 
>> After a failed attempt to release the DM-R10 release, I would like to call
>> for a new vote on the Dependency Manager toplevel release R11.
>> 
>> The following issues were solved:
>> 
>> ** Bug
>>* [FELIX-5630] - NullObject is created for a required dependency if the
>> component is removed and added again to the dependency manager
>>* [FELIX-5636] - Component of aspect service does not have any service
>> properties anymore
>>* [FELIX-5657] - DM released sources can't be rebuilt
>> 
>> ** Improvement
>>* [FELIX-5619] - MultiProperyFilterIndex memory consumption
>>* [FELIX-5623] - Improve performance of ComponentImpl.getName method
>>* [FELIX-5650] - Support latest version of Gogo
>>* [FELIX-5653] - Simplify DM-Lambda samples
>>* [FELIX-5658] - Include poms in dm artifacts
>> 
>> You can use this UNIX script to download the release and verify the
>> signatures:
>> 
>> 
>> http://svn.apache.org/repos/asf/felix/trunk/dependencymanager/release/
>> check_staged_release.sh
>> 
>> Usage:
>> 
>>sh check_staged_release.sh r11 /tmp/felix-staging
>> 
>> This script, unlike the original Felix check_stage_release.sh, is specific
>> to the new Dependency Manager release process (see FELIX-4818) and will
>> download staging from https://dist.apache.org/repos/dist/dev/felix instead
>> of http://repository.apache.org/content/repositories.
>> 
>> To rebuild the DM binaries from the source, you can then refer to
>> https://svn.apache.org/repos/asf/felix/trunk/dependencymanager/release/
>> resources/src/README.src
>> 
>> 
>> Please vote to approve this release:
>> 
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>> 
>> 
>> Many thanks;
>> 
>> regards;
>> /Pierre
>> 

Re: [VOTE] Apache Felix Dependency Manager Release R11

[David Bosschaert]

+1

David

On 27 June 2017 at 09:17, Pierre De Rop  wrote:

> Hello all,
>
> After a failed attempt to release the DM-R10 release, I would like to call
> for a new vote on the Dependency Manager toplevel release R11.
>
> The following issues were solved:
>
> ** Bug
> * [FELIX-5630] - NullObject is created for a required dependency if the
> component is removed and added again to the dependency manager
> * [FELIX-5636] - Component of aspect service does not have any service
> properties anymore
> * [FELIX-5657] - DM released sources can't be rebuilt
>
> ** Improvement
> * [FELIX-5619] - MultiProperyFilterIndex memory consumption
> * [FELIX-5623] - Improve performance of ComponentImpl.getName method
> * [FELIX-5650] - Support latest version of Gogo
> * [FELIX-5653] - Simplify DM-Lambda samples
> * [FELIX-5658] - Include poms in dm artifacts
>
> You can use this UNIX script to download the release and verify the
> signatures:
>
>
> http://svn.apache.org/repos/asf/felix/trunk/dependencymanager/release/
> check_staged_release.sh
>
> Usage:
>
> sh check_staged_release.sh r11 /tmp/felix-staging
>
> This script, unlike the original Felix check_stage_release.sh, is specific
> to the new Dependency Manager release process (see FELIX-4818) and will
> download staging from https://dist.apache.org/repos/dist/dev/felix instead
> of http://repository.apache.org/content/repositories.
>
> To rebuild the DM binaries from the source, you can then refer to
> https://svn.apache.org/repos/asf/felix/trunk/dependencymanager/release/
> resources/src/README.src
>
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
>
> Many thanks;
>
> regards;
> /Pierre
>

Re: [VOTE] Apache Felix Dependency Manager Release R11

[Juan Manuel Calderon]

+1 (non binding)

On Tue, Jun 27, 2017 at 3:13 PM, fleygues 
wrote:

> +1
>
> Congratulations.
>
> Pierre De Rop wrote:
>
>> Hello all,
>>
>> After a failed attempt to release the DM-R10 release, I would like to call
>> for a new vote on the Dependency Manager toplevel release R11.
>>
>> The following issues were solved:
>>
>> ** Bug
>>  * [FELIX-5630] - NullObject is created for a required dependency if
>> the
>> component is removed and added again to the dependency manager
>>  * [FELIX-5636] - Component of aspect service does not have any
>> service
>> properties anymore
>>  * [FELIX-5657] - DM released sources can't be rebuilt
>>
>> ** Improvement
>>  * [FELIX-5619] - MultiProperyFilterIndex memory consumption
>>  * [FELIX-5623] - Improve performance of ComponentImpl.getName method
>>  * [FELIX-5650] - Support latest version of Gogo
>>  * [FELIX-5653] - Simplify DM-Lambda samples
>>  * [FELIX-5658] - Include poms in dm artifacts
>>
>> You can use this UNIX script to download the release and verify the
>> signatures:
>>
>>
>> http://svn.apache.org/repos/asf/felix/trunk/dependencymanage
>> r/release/check_staged_release.sh
>>
>> Usage:
>>
>>  sh check_staged_release.sh r11 /tmp/felix-staging
>>
>> This script, unlike the original Felix check_stage_release.sh, is specific
>> to the new Dependency Manager release process (see FELIX-4818) and will
>> download staging from https://dist.apache.org/repos/dist/dev/felix
>> instead
>> of http://repository.apache.org/content/repositories.
>>
>> To rebuild the DM binaries from the source, you can then refer to
>> https://svn.apache.org/repos/asf/felix/trunk/dependencymanag
>> er/release/resources/src/README.src
>>
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>>
>>
>> Many thanks;
>>
>> regards;
>> /Pierre
>>
>>
>