FOSDEM 2016 - take action by 4th of December 2015

[Roman Shaposhnik]

As most of you probably know FOSDEM 2016 (the biggest,
100% free open source developer conference) is right 
around the corner:
   https://fosdem.org/2016/

We hope to have an ASF booth and we would love to see as
many ASF projects as possible present at various tracks
(AKA Developer rooms):
   https://fosdem.org/2016/schedule/#devrooms

This year, for the first time, we are running a dedicated
Big Data and HPC Developer Room and given how much of that
open source development is done at ASF it would be great
to have folks submit talks to:
   https://hpc-bigdata-fosdem16.github.io

While the CFPs for different Developer Rooms follow slightly 
different schedules, but if you submit by the end of this week 
you should be fine.

Finally if you don't want to fish for CFP submission URL,
here it is:
   https://fosdem.org/submit

If you have any questions -- please email me *directly* and
hope to see as many of you as possible in two months! 

Thanks,
Roman.

Re: [VOTE] Release Apache Felix JAAS Support 0.0.4

[Carsten Ziegeler]

+1


 
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE] Release Apache Felix Script Console Plugin 1.0.2

[Carsten Ziegeler]

+1

 
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[GitHub] felix pull request: Fixed ClassCastException caused by local resou...

[skahmann]

GitHub user skahmann opened a pull request:

https://github.com/apache/felix/pull/44

Fixed ClassCastException caused by local resources

* Separated commits for exception fix and code cleanup

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/skahmann/felix bug/local_resource_exception

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/felix/pull/44.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #44


commit b782554ae0aebb48f7bc3e0adaa6afe5781e61db
Author: Stephen Kahmann 
Date:   2015-11-30T19:34:42Z

Fixed exception issue

commit ab8ba3a51b8e3d3253dd42fefd7d10ae261351a7
Author: Stephen Kahmann 
Date:   2015-11-30T21:08:07Z

Cleaned up code

commit 237ef0771b0439c3e6b12de15b551f5eec8ea053
Author: Stephen Kahmann 
Date:   2015-11-30T22:29:02Z

more code cleanup




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [VOTE] Release Apache Felix Script Console Plugin 1.0.2

[Pierre De Rop]

+1

regards;
/Pierre

On Mon, Nov 30, 2015 at 3:42 PM, David Bosschaert <
david.bosscha...@gmail.com> wrote:

> +1
>
> David
>
> On 30 November 2015 at 12:21, Chetan Mehrotra  wrote:
> > I would like to call a vote for a new web console release:
> > We fixed four issues:
> > https://issues.apache.org/jira/browse/FELIX/fixforversion/12324783
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1106/
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1106 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Chetan Mehrotra
>

[jira] [Assigned] (FELIX-5112) ClassCastException when deploying an OBR Resource already present in the runtime

[David Bosschaert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Bosschaert reassigned FELIX-5112:
---

Assignee: David Bosschaert

> ClassCastException when deploying an OBR Resource already present in the 
> runtime
> 
>
> Key: FELIX-5112
> URL: https://issues.apache.org/jira/browse/FELIX-5112
> Project: Felix
>  Issue Type: Bug
>  Components: Bundle Repository (OBR)
>Affects Versions: bundlerepository-2.0.6
>Reporter: Stephen Kahmann
>Assignee: David Bosschaert
> Attachments: fix_local_resource_resolver.diff
>
>
> When using OBR to deploy a bundle that is already present in the runtime, 
> there is a ClassCastException:
> {code}
> java.lang.ClassCastException: 
> org.apache.felix.bundlerepository.impl.LazyLocalResourceImpl cannot be cast 
> to org.apache.felix.bundlerepository.impl.LocalResourceImpl
>   at 
> org.apache.felix.bundlerepository.impl.ResolverImpl.findUpdatableLocalResource(ResolverImpl.java:703)
>   at 
> org.apache.felix.bundlerepository.impl.ResolverImpl.deploy(ResolverImpl.java:569)
>   at 
> org.apache.karaf.obr.command.ObrCommandSupport.doDeploy(ObrCommandSupport.java:168)
>   at 
> org.apache.karaf.obr.command.StartCommand.doExecute(StartCommand.java:38)
>   at 
> org.apache.karaf.obr.command.ObrCommandSupport.execute(ObrCommandSupport.java:58)
>   at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)
>   at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)
>   at 
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)
>   at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:94)
>   at 
> org.apache.karaf.shell.impl.console.HeadlessSessionImpl.execute(HeadlessSessionImpl.java:90)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: BundleRepository ClassCastException

[David Bosschaert]

Hi Stephen,

I can take a look over the coming little while...

Best regards,

David

On 30 November 2015 at 16:36, Stephen Kahmann
 wrote:
> Hi,
>
> I created Issue 5112, but I 
> haven’t seen any response to it. Has anyone taken a look at this? PR 
> here.
>
> Thank you!
> Stephen
>

BundleRepository ClassCastException

[Stephen Kahmann]

Hi,

I created Issue 5112, but I 
haven’t seen any response to it. Has anyone taken a look at this? PR 
here.

Thank you!
Stephen

Re: [VOTE] Release Apache Felix Script Console Plugin 1.0.2

[David Bosschaert]

+1

David

On 30 November 2015 at 12:21, Chetan Mehrotra  wrote:
> I would like to call a vote for a new web console release:
> We fixed four issues:
> https://issues.apache.org/jira/browse/FELIX/fixforversion/12324783
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-1106/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1106 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> Regards
> Chetan Mehrotra

Re: [VOTE] Release Apache Felix Script Console Plugin 1.0.2

[Raymond Auge]

+1 (non binding)

Sincerely,
- Ray

On Mon, Nov 30, 2015 at 7:22 AM, Chetan Mehrotra 
wrote:

> +1 (non binding)
>
> Chetan Mehrotra
>



-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [VOTE] Release Apache Felix JAAS Support 0.0.4

[Raymond Auge]

+1 (non binding)

Sincerely,
- Ray

On Mon, Nov 30, 2015 at 9:26 AM, Jean-Baptiste Onofré 
wrote:

> +1 (non binding)
>
> Regards
> JB
>
>
> On 11/30/2015 03:24 PM, David Bosschaert wrote:
>
>> +1
>>
>> David
>>
>> On 30 November 2015 at 12:56, Chetan Mehrotra  wrote:
>>
>>> I would like to call a vote for a new JAAS support release:
>>> We fixed three issues:
>>> https://issues.apache.org/jira/browse/FELIX/fixforversion/12333114
>>>
>>> Staging repositories:
>>> https://repository.apache.org/content/repositories/orgapachefelix-1107/
>>>
>>> You can use this UNIX script to download the release and verify the
>>> signatures:
>>> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>>>
>>> Usage:
>>> sh check_staged_release.sh 1107 /tmp/felix-staging
>>>
>>> Please vote to approve this release:
>>>
>>> [ ] +1 Approve the release
>>> [ ] -1 Veto the release (please provide specific comments)
>>>
>>> Regards
>>> Chetan Mehrotra
>>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>



-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [VOTE] Release Apache Felix JAAS Support 0.0.4

[Jean-Baptiste Onofré]

+1 (non binding)

Regards
JB

On 11/30/2015 03:24 PM, David Bosschaert wrote:

+1

David

On 30 November 2015 at 12:56, Chetan Mehrotra  wrote:

I would like to call a vote for a new JAAS support release:
We fixed three issues:
https://issues.apache.org/jira/browse/FELIX/fixforversion/12333114

Staging repositories:
https://repository.apache.org/content/repositories/orgapachefelix-1107/

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1107 /tmp/felix-staging

Please vote to approve this release:

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

Regards
Chetan Mehrotra


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

Re: [VOTE] Release Apache Felix JAAS Support 0.0.4

[David Bosschaert]

+1

David

On 30 November 2015 at 12:56, Chetan Mehrotra  wrote:
> I would like to call a vote for a new JAAS support release:
> We fixed three issues:
> https://issues.apache.org/jira/browse/FELIX/fixforversion/12333114
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-1107/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1107 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> Regards
> Chetan Mehrotra

Re: [VOTE] Release Apache Felix JAAS Support 0.0.4

[Chetan Mehrotra]

+1 (non binding)
Chetan Mehrotra


On Mon, Nov 30, 2015 at 6:26 PM, Chetan Mehrotra  wrote:
> I would like to call a vote for a new JAAS support release:
> We fixed three issues:
> https://issues.apache.org/jira/browse/FELIX/fixforversion/12333114
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-1107/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1107 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> Regards
> Chetan Mehrotra

[jira] [Closed] (FELIX-5113) Remove useless wrong test in ConfigurationDependencyImpl

[Pierre De Rop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre De Rop closed FELIX-5113.


> Remove useless wrong test in ConfigurationDependencyImpl
> 
>
> Key: FELIX-5113
> URL: https://issues.apache.org/jira/browse/FELIX-5113
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager
>Affects Versions:  org.apache.felix.dependencymanager-r5
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
>Priority: Trivial
> Fix For: org.apache.felix.dependencymanager-r6
>
>
> There is a useless and wrong test in the 
> ConfigurationDependencyImpl.updated() method:
> {code}
> // If this is initial settings, or a configuration update, we handle 
> it synchronously.
> // We'll conclude that the dependency is available only if invoking 
> updated did not cause
> // any ConfigurationException.
> Object[] instances = m_component.getInstances();
> if (instances != null) {
> try {
> invokeUpdated(settings);
> } catch (ConfigurationException e) {
> logConfigurationException(e);
> throw e;
> }
> }
> {code}
> the "if (instances != null)" test is useless, and also wrong, but 
> fortunately, it does not causes any problems.
> Indeed, the m_component.getInstances() never returns null, and return an 
> empty array when the component instance is not yet instantiated. This may 
> happen when an instance callback is specified (like a Factory that needs the 
> configuration before the Factory.create method is called).
> Anyway, this test should be removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FELIX-5104) Call a conf dependency callback Instance with an instantiated component

[Pierre De Rop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre De Rop closed FELIX-5104.


> Call a conf dependency callback Instance with an instantiated component
> ---
>
> Key: FELIX-5104
> URL: https://issues.apache.org/jira/browse/FELIX-5104
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager
>Affects Versions:  org.apache.felix.dependencymanager-r5
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
>Priority: Minor
> Fix For: org.apache.felix.dependencymanager-r6
>
>
> Normally, when you specify a configuration dependency INSTANCE callback, then 
> the component is not yet instantiated at the time the INSTANCE callback is 
> invoked.
> If the INSTANCE callback is a factory object that has to create the component 
> instance (from its "create" method), then this allows the factory object to 
> get injected with the configuration, and then use that configuration from the 
> factory.create method.
> But, in the context of FELIX-4689 (Create a more fluent syntax for the 
> dependency manager builder), we need a way to specify a configuration 
> dependency instance callback and ensure that the component instance(s) is 
> already instantiated before the instance callback is invoked.
> To fix this issue, we simply need to add a " setCallback(Object instance, 
> String callback, boolean needsInstance)" method in the 
> ConfigurationDependency interface, in order to allow to specify if the 
> component instance should be instantiated or not before the instance callback 
> is invoked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FELIX-5114) Schedule configuration update in Component executor synchronously

[Pierre De Rop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre De Rop closed FELIX-5114.


> Schedule configuration update in Component executor synchronously
> -
>
> Key: FELIX-5114
> URL: https://issues.apache.org/jira/browse/FELIX-5114
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager
>Affects Versions:  org.apache.felix.dependencymanager-r5
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
>Priority: Minor
> Fix For: org.apache.felix.dependencymanager-r6
>
>
> Currently, all external events are handled through the Component queue 
> (Executor). This allows to provide a nice thread model, where no 
> synchronization is required inside DM, and also the user benefits from this 
> because, because all component lifecycle callbacks and all dependency 
> injections are also performed using the internal Component queue. So, in some 
> situation, this model make life easier for the developer.
> But there is an exception to all this: the Configuration Dependency is 
> currently handled from the Configuration Admin dispatcher thread, in other 
> words, a component update callback can be called while a component "bind" 
> method is called from another thread (if a service dependency is injected 
> dynamically from another thread).
> We do this because Configuration Admin requires to throw a 
> ConfigurationException from the update thread, in case there is a 
> configuration error.
> The intent of this issue is simply to stay synchronous (we still throw a 
> ConfigurationException from the CM update thread), but instead of calling the 
> component "updated" callback from the CM thread, we schedule the update 
> callback through the Component internal queue, and we wait for the update 
> callback to be executed (using a simple Callbable associated with a 
> FutureTask.
> This trick will allow to call the component "updated" callback safely, and 
> return any configuration errors to the CM update thread.
> So, basically, instead of doing this in the 
> ConfigurationDependencyImpl.updated callback
> {code}
> try {
> invokeUpdated(settings); // either the callback instance or the 
> component instances, if available.
> } catch (ConfigurationException e) {
> logConfigurationException(e);
> throw e;
> }
> {code}
> then schedule the update invocation in the component executor and wait for 
> the result like this:
> {code}
> Callable result = new 
> Callable() {
> @Override
> public ConfigurationException call() throws Exception {
> try {
> invokeUpdated(settings); // either the callback instance 
> or the component instances, if available.
> } catch (ConfigurationException e) {
> return e;
> }
> return null;
> }
> };
> FutureTask ft = new FutureTask<>(result);
> m_component.getExecutor().execute(ft);
> 
> try {
> ConfigurationException confError = ft.get(UPDATE_MAXWAIT, 
> TimeUnit.MILLISECONDS);
> if (confError != null) {
> logConfigurationException(confError);
> throw confError;
> }
>   }
> catch (Throwable error) {
> logConfigurationException(error);
> throw new ConfigurationException(null, "Could not handle 
> configuration update", error);
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FELIX-4922) Simplify DM changelog management

[Pierre De Rop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre De Rop closed FELIX-4922.


> Simplify DM changelog management 
> -
>
> Key: FELIX-4922
> URL: https://issues.apache.org/jira/browse/FELIX-4922
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager, Dependency Manager Annotations, 
> Dependency Manager Runtime, Dependency Manager Samples, Dependency Manager 
> Shell
>Affects Versions:  org.apache.felix.dependencymanager-r5
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
> Fix For: org.apache.felix.dependencymanager-r6
>
>
> Currently, each DM sub module has its own changelog.
> but it's hard to maintain.
> Instead, a single changelog should be maintained in the ./release/resource/ 
> directory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FELIX-5054) Clean-up instance bound dependencies when component is destroyed

[Pierre De Rop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre De Rop closed FELIX-5054.


> Clean-up instance bound dependencies when component is destroyed
> 
>
> Key: FELIX-5054
> URL: https://issues.apache.org/jira/browse/FELIX-5054
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager
>Affects Versions:  org.apache.felix.dependencymanager-r5
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
>Priority: Minor
> Fix For: org.apache.felix.dependencymanager-r6
>
>
> Currently, when a component adds a dependency dynamically from its init() 
> callback or during the life of the component, then if the component goes 
> through multiple init/destroy/init cycles, then all instance bound 
> dependencies must be manually removed from the destroy() callback.
> If the instance bound dependencies are not removed from destroy(), then the 
> next time the component is initialized again (init/destroy/init cycles), then 
> the same instance bound dependencies would then be re-added and duplicated.
> So, the intent of this improvement issue is just to automatically clean-up 
> instance bound dependencies when the component is destroyed. This way, if the 
> component is initialized again, then the earlier added instance bound 
> dependencies are gone, and the init() method can re-add them safely (we won't 
> have duplicated instance bound dependencies in the component).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[VOTE] Release Apache Felix JAAS Support 0.0.4

[Chetan Mehrotra]

I would like to call a vote for a new JAAS support release:
We fixed three issues:
https://issues.apache.org/jira/browse/FELIX/fixforversion/12333114

Staging repositories:
https://repository.apache.org/content/repositories/orgapachefelix-1107/

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1107 /tmp/felix-staging

Please vote to approve this release:

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

Regards
Chetan Mehrotra

[jira] [Closed] (FELIX-5055) Upgrade DM to BndTools 3.0.0

[Pierre De Rop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre De Rop closed FELIX-5055.


> Upgrade DM to BndTools 3.0.0
> 
>
> Key: FELIX-5055
> URL: https://issues.apache.org/jira/browse/FELIX-5055
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager
>Affects Versions:  org.apache.felix.dependencymanager-r5
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
>Priority: Minor
> Fix For: org.apache.felix.dependencymanager-r6
>
>
> BndTools 3.0.0 is available, and we should build DM with this new version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FELIX-5045) DM Optional callbacks may sometimes be invoked before start callback

[Pierre De Rop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre De Rop closed FELIX-5045.


> DM Optional callbacks may sometimes be invoked before start callback
> 
>
> Key: FELIX-5045
> URL: https://issues.apache.org/jira/browse/FELIX-5045
> Project: Felix
>  Issue Type: Bug
>  Components: Dependency Manager
>Affects Versions:  org.apache.felix.dependencymanager-r5
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
> Fix For: org.apache.felix.dependencymanager-r6
>
>
> We just found a corner case that triggers optional dependency callbacks 
> before the component is invoked in its 'start' lifecycel callback. This is a 
> bug, because in DM, optional dependency callbacks should be always invoked 
> after the component's 'start' lifecycle callback.
> I'm describing now the use case: we have the following component players: 
> - B: a simple service component.
> - BFactory: a service that has a 'create' method which registers in the OSGi 
> registry a new B service instance.
> - A: a component that adds from A.init() lifecycle callback a required 
> dependency (with a callback) on BFactory, as well as an optional dependency 
> (with a callback) on B.
> - when A.bind(BFactory factory) is called, it then calls "factory.create()" 
> method which triggers the registration of the B Service.  At this point, 
> A.bind(B b) is then invoked, but the A.start() lifecycle callback has not yet 
> been called. This is because we are currently transiting from 
> INSTANTIATED_AND_WAITING_FOR_REQUIRED -> TRACKING_OPTIONAL; so the current 
> state is TRACKING_OPTIONAL, and we are calling the 
> invokeAddRequiredInstanceBoundDependencies()
> method, which calls A.bind(BFactory) method, which synchronously registers a 
> B service instance; so this ends up calling the handleAdded method, which 
> invoke A.bind(B b) method, but at this point we have not yet called the 
> A.start() callback.
> - then "A.start()" is called.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FELIX-5046) Gradle wrapper is not included in DM source release

[Pierre De Rop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre De Rop closed FELIX-5046.


> Gradle wrapper is not included in DM source release
> ---
>
> Key: FELIX-5046
> URL: https://issues.apache.org/jira/browse/FELIX-5046
> Project: Felix
>  Issue Type: Bug
>  Components: Dependency Manager
>Affects Versions:  org.apache.felix.dependencymanager-r5
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
>Priority: Minor
> Fix For: org.apache.felix.dependencymanager-r6
>
>
> the "gradle/wrapper/gradle-wrapper.jar" jar is not included in the source 
> distribution, preventing the usage of "./gradlew" wrapper.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FELIX-4921) Ensure binary equality of the same bundle between successive DM releases

[Pierre De Rop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre De Rop closed FELIX-4921.


> Ensure binary equality of the same bundle between successive DM releases
> 
>
> Key: FELIX-4921
> URL: https://issues.apache.org/jira/browse/FELIX-4921
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager, Dependency Manager Annotations, 
> Dependency Manager Runtime, Dependency Manager Samples, Dependency Manager 
> Shell
>Affects Versions:  org.apache.felix.dependencymanager-r5
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
>Priority: Trivial
> Fix For: org.apache.felix.dependencymanager-r6
>
>
> As reported by Bram in the vote for the DM release R4 (see [1]); when a new 
> DM release R is made, and if that new release contains an unmodified bundle 
> since the previous R-1, then the new release R includes a rebuilt version of 
> the unmodified bundle. 
> While this is not a real issue, it turns out that there is still a binary 
> difference for the same bundle between R-1 and R.
> Even is we don't include headers like "Bnd-LastModified,Tool,Created-By", 
> there may be a binary diff (because the jar has been rebuilt).
> As suggested by Bram, when a bundle is unmodified, it would be better to just 
> use the same binary version from the release repo instead of using the just 
> rebuilt version. This will ensure binary equality for an unmodified bundle 
> between successive DM releases.
> [1] http://www.mail-archive.com/dev@felix.apache.org/msg36806.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FELIX-4974) DM filter indices not enabled if the dependencymanager bundle is started first

[Pierre De Rop (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre De Rop closed FELIX-4974.


> DM filter indices not enabled if the dependencymanager bundle is started first
> --
>
> Key: FELIX-4974
> URL: https://issues.apache.org/jira/browse/FELIX-4974
> Project: Felix
>  Issue Type: Bug
>  Components: Dependency Manager
>Affects Versions:  org.apache.felix.dependencymanager-r5
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
> Fix For: org.apache.felix.dependencymanager-r6
>
>
> Optimized DM filter indices are not enabled if the 
> org.apache.felix.dependencymanager bundle is started before any other bundles 
> that contain a DM Activator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Felix Script Console Plugin 1.0.2

[Chetan Mehrotra]

+1 (non binding)

Chetan Mehrotra

[VOTE] Release Apache Felix Script Console Plugin 1.0.2

[Chetan Mehrotra]

I would like to call a vote for a new web console release:
We fixed four issues:
https://issues.apache.org/jira/browse/FELIX/fixforversion/12324783

Staging repositories:
https://repository.apache.org/content/repositories/orgapachefelix-1106/

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1106 /tmp/felix-staging

Please vote to approve this release:

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

Regards
Chetan Mehrotra

[jira] [Resolved] (FELIX-5123) Script Console UI improvements

[Chetan Mehrotra (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chetan Mehrotra resolved FELIX-5123.

Resolution: Fixed

Done with 1717221

> Script Console UI improvements
> --
>
> Key: FELIX-5123
> URL: https://issues.apache.org/jira/browse/FELIX-5123
> Project: Felix
>  Issue Type: Improvement
>  Components: Script Console Plugin
>Affects Versions: script-console-1.0.0
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: script-console-1.0.2
>
>
> Following improvements need to be done to script console UI
> # Remove timeout on executed command
> # Drop the Language button



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FELIX-5124) maven-bundle-plugin interferes with installAtEnd setting of maven-install-bundle

[Oliver Heger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Heger updated FELIX-5124:

Attachment: install_test.zip

Maven test project demonstrating the problem.

> maven-bundle-plugin interferes with installAtEnd setting of 
> maven-install-bundle
> 
>
> Key: FELIX-5124
> URL: https://issues.apache.org/jira/browse/FELIX-5124
> Project: Felix
>  Issue Type: Bug
>  Components: Maven Bundle Plugin
>Reporter: Oliver Heger
> Attachments: install_test.zip
>
>
> The maven-install-plugin supports the _installAtEnd_ setting which differs 
> the installation of artifacts in a multi-module build to the very end; the 
> installation happens only if the whole build is successful (see 
> https://maven.apache.org/plugins/maven-install-plugin/install-mojo.html#installAtEnd).
> We wanted to use this feature in our project, but found out that even for 
> successful builds the installation never happend. After each module a message 
> was printed "Installing :: at end", but at the 
> end of the build no installation was performed.
> Investigating this problem showed a relation to the maven-bundle-plugin (in 
> its latest version 3.0.1): If the maven-bundle-plugin is declared in the 
> top-level pom, installation works as expected. However, if the declaration is 
> moved to a sub-module, the installation is skipped.
> I have created a sample maven project demonstrating the issue. The project 
> consists of the top-level pom, a modules pom and two sub-modules for the API 
> and the implementation of a dummy service. The maven-bundle-plugin 
> declaration is commented out in the top-level pom; it is also declared in the 
> modules pom. In this form, when building the project with {{mvn clean 
> install}} the project artifacts are not installed. When the comments are 
> removed to enable the declaration the installation takes place. I hope this 
> helps to reproduce and further anylize the problem.
> I was not sure whether this is the correct place to report this problem 
> because the maven-install-plugin is affected as well. However, the install 
> plugin works well in normal scenarios. The maven-deploy-plugin has a similar 
> setting (_deployAtEnd_), and it is affected by this issue, too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (FELIX-5124) maven-bundle-plugin interferes with installAtEnd setting of maven-install-bundle

[Oliver Heger (JIRA)]

Oliver Heger created FELIX-5124:
---

 Summary: maven-bundle-plugin interferes with installAtEnd setting 
of maven-install-bundle
 Key: FELIX-5124
 URL: https://issues.apache.org/jira/browse/FELIX-5124
 Project: Felix
  Issue Type: Bug
  Components: Maven Bundle Plugin
Reporter: Oliver Heger


The maven-install-plugin supports the _installAtEnd_ setting which differs the 
installation of artifacts in a multi-module build to the very end; the 
installation happens only if the whole build is successful (see 
https://maven.apache.org/plugins/maven-install-plugin/install-mojo.html#installAtEnd).

We wanted to use this feature in our project, but found out that even for 
successful builds the installation never happend. After each module a message 
was printed "Installing :: at end", but at the 
end of the build no installation was performed.

Investigating this problem showed a relation to the maven-bundle-plugin (in its 
latest version 3.0.1): If the maven-bundle-plugin is declared in the top-level 
pom, installation works as expected. However, if the declaration is moved to a 
sub-module, the installation is skipped.

I have created a sample maven project demonstrating the issue. The project 
consists of the top-level pom, a modules pom and two sub-modules for the API 
and the implementation of a dummy service. The maven-bundle-plugin declaration 
is commented out in the top-level pom; it is also declared in the modules pom. 
In this form, when building the project with {{mvn clean install}} the project 
artifacts are not installed. When the comments are removed to enable the 
declaration the installation takes place. I hope this helps to reproduce and 
further anylize the problem.

I was not sure whether this is the correct place to report this problem because 
the maven-install-plugin is affected as well. However, the install plugin works 
well in normal scenarios. The maven-deploy-plugin has a similar setting 
(_deployAtEnd_), and it is affected by this issue, too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (FELIX-5122) Script console output cannot be copied

[Chetan Mehrotra (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chetan Mehrotra resolved FELIX-5122.

Resolution: Fixed

Done with 1717220

> Script console output cannot be copied
> --
>
> Key: FELIX-5122
> URL: https://issues.apache.org/jira/browse/FELIX-5122
> Project: Felix
>  Issue Type: Bug
>  Components: Script Console Plugin
>Affects Versions: script-console-1.0.0
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Fix For: script-console-1.0.2
>
>
> Script console output cannot be copied.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (FELIX-5123) Script Console UI improvements

[Chetan Mehrotra (JIRA)]

Chetan Mehrotra created FELIX-5123:
--

 Summary: Script Console UI improvements
 Key: FELIX-5123
 URL: https://issues.apache.org/jira/browse/FELIX-5123
 Project: Felix
  Issue Type: Improvement
  Components: Script Console Plugin
Affects Versions: script-console-1.0.0
Reporter: Chetan Mehrotra
Assignee: Chetan Mehrotra
Priority: Minor
 Fix For: script-console-1.0.2


Following improvements need to be done to script console UI

# Remove timeout on executed command
# Drop the Language button



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (FELIX-5122) Script console output cannot be copied

[Chetan Mehrotra (JIRA)]

Chetan Mehrotra created FELIX-5122:
--

 Summary: Script console output cannot be copied
 Key: FELIX-5122
 URL: https://issues.apache.org/jira/browse/FELIX-5122
 Project: Felix
  Issue Type: Bug
  Components: Script Console Plugin
Affects Versions: script-console-1.0.0
Reporter: Chetan Mehrotra
Assignee: Chetan Mehrotra
 Fix For: script-console-1.0.2


Script console output cannot be copied.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (FELIX-5120) ScriptEngineManager not able to parse service file with comments at end of classname

[Chetan Mehrotra (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chetan Mehrotra resolved FELIX-5120.

Resolution: Fixed

Fixed with 1717206

> ScriptEngineManager not able to parse service file with comments at end of 
> classname
> 
>
> Key: FELIX-5120
> URL: https://issues.apache.org/jira/browse/FELIX-5120
> Project: Felix
>  Issue Type: Bug
>  Components: Script Console Plugin
>Affects Versions: script-console-1.0.0
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: script-console-1.0.2
>
>
> A service file can also have a comment like below like
> {noformat}
> #script engines supported
> com.sun.script.javascript.RhinoScriptEngineFactory #javascript
> {noformat}
> Such a service file is not parsed properly and following exception is thrown
> {noformat}
> 2015-11-30 11:23:58.375 ERROR 23215 --- [ixDispatchQueue] 
> o.a.f.webconsole.plugins.scriptconsole   : Cannot register 
> ScriptEngineFactory com.sun.script.javascript.RhinoScriptEngineFactory 
> #javascript (java.lang.ClassNotFoundException: 
> com.sun.script.javascript.RhinoScriptEngineFactory #javascript)
> java.lang.ClassNotFoundException: 
> com.sun.script.javascript.RhinoScriptEngineFactory #javascript
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366) 
> ~[na:1.7.0_55]
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355) 
> ~[na:1.7.0_55]
> at java.security.AccessController.doPrivileged(Native Method) 
> ~[na:1.7.0_55]
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354) 
> ~[na:1.7.0_55]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425) 
> ~[na:1.7.0_55]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358) 
> ~[na:1.7.0_55]
> at 
> org.apache.felix.connect.PojoSRBundle.loadClass(PojoSRBundle.java:451) 
> ~[org.apache.felix.connect-0.1.0.jar:na]
> at 
> org.apache.felix.webconsole.plugins.scriptconsole.internal.ScriptEngineManager.registerFactories(ScriptEngineManager.java:197)
>  [org.apache.felix.webconsole.plugins.scriptconsole-1.0.0.jar:na]
> at 
> org.apache.felix.webconsole.plugins.scriptconsole.internal.ScriptEngineManager.refreshScriptEngineManager(ScriptEngineManager.java:160)
>  [org.apache.felix.webconsole.plugins.scriptconsole-1.0.0.jar:na]
> at 
> org.apache.felix.webconsole.plugins.scriptconsole.internal.ScriptEngineManager.bundleChanged(ScriptEngineManager.java:111)
>  [org.apache.felix.webconsole.plugins.scriptconsole-1.0.0.jar:na]
> at 
> org.apache.felix.connect.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:821)
>  [org.apache.felix.connect-0.1.0.jar:na]
> at 
> org.apache.felix.connect.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:771)
>  [org.apache.felix.connect-0.1.0.jar:na]
> at 
> org.apache.felix.connect.felix.framework.util.EventDispatcher.run(EventDispatcher.java:993)
>  [org.apache.felix.connect-0.1.0.jar:na]
> at 
> org.apache.felix.connect.felix.framework.util.EventDispatcher.access$000(EventDispatcher.java:52)
>  [org.apache.felix.connect-0.1.0.jar:na]
> at 
> org.apache.felix.connect.felix.framework.util.EventDispatcher$1.run(EventDispatcher.java:94)
>  [org.apache.felix.connect-0.1.0.jar:na]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_55]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (FELIX-5121) Script console build failing on latest trunk

[Chetan Mehrotra (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chetan Mehrotra resolved FELIX-5121.

Resolution: Fixed

Done in 1717198 

> Script console build failing on latest trunk
> 
>
> Key: FELIX-5121
> URL: https://issues.apache.org/jira/browse/FELIX-5121
> Project: Felix
>  Issue Type: Task
>  Components: Script Console Plugin
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Fix For: script-console-1.0.2
>
>
> Current trunk build is failing as exam-maven-plugin launch is not working 
> {noformat}
> [INFO] Failsafe report directory: 
> /home/chetanm/git/apache/felix/webconsole-plugins/script-console/target/failsafe-reports
> Error: Main method not found in class org.ops4j.pax.exam.spi.PaxExamRuntime, 
> please define the main method as:
>public static void main(String[] args)
> {noformat}
> Due to this the OSGi container is not launched



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESULT] [VOTE] Apache Felix Dependency Manager Release Candidate R6

[Pierre De Rop]

Hi,

The vote has passed with the following result :

  +1 (binding): Pierre De Rop, David Bosschaert, Jan Willem Janssen
  +1 (non binding): Jamie Goodyear

I will copy this release to the Felix dist directory and
promote the artifacts to the central Maven repository.

thanks everyone for the votes;

cheers

/Pierre

[jira] [Created] (FELIX-5121) Script console build failing on latest trunk

[Chetan Mehrotra (JIRA)]

Chetan Mehrotra created FELIX-5121:
--

 Summary: Script console build failing on latest trunk
 Key: FELIX-5121
 URL: https://issues.apache.org/jira/browse/FELIX-5121
 Project: Felix
  Issue Type: Task
  Components: Script Console Plugin
Reporter: Chetan Mehrotra
Assignee: Chetan Mehrotra
 Fix For: script-console-1.0.2


Current trunk build is failing as exam-maven-plugin launch is not working 
{noformat}
[INFO] Failsafe report directory: 
/home/chetanm/git/apache/felix/webconsole-plugins/script-console/target/failsafe-reports
Error: Main method not found in class org.ops4j.pax.exam.spi.PaxExamRuntime, 
please define the main method as:
   public static void main(String[] args)
{noformat}

Due to this the OSGi container is not launched



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)