[VOTE] Apache Felix Dependency Manager Release R8
Hi all, Second attempt to release Dependency Manager. Some new features in this release: "configuration types" and a new "DM-lambda" library, which is described here: http://felix.staging.apache.org/documentation/subprojects/apache-felix-dependency-manager/guides/dm-lambda.html The R8 now requires the usage of a recent JAVA8 jdk (the new version has been built and tested with latest version 1.8.74) The following issues were solved: ** Bug * [FELIX-5146] - Service adapters turn on autoconf even if callbacks are used * [FELIX-5147] - Bundle Adapter auto configures class fields even if callbacks are used * [FELIX-5153] - DM4 calls stop before ungetService() on ServiceFactory components * [FELIX-5155] - Adapter/Aspect extra service dependencies injected twice if using callback instance * [FELIX-5178] - Make some component parameters as volatile * [FELIX-5181] - Only log info/debug if dm annotation log parameter is enabled * [FELIX-5187] - No errog log when configuration dependency callback is not found * [FELIX-5188] - No error log when a factory pid adapter update callback is not found * [FELIX-5192] - ConfigurationDependency race condition when component is stopped * [FELIX-5193] - Factory Pid Adapter race condition when component is stopped * [FELIX-5200] - Factory configuration adapter not restarted ** Improvement * [FELIX-5126] - Build DM using Java 8 * [FELIX-5164] - Add support for callback instance in Aspects * [FELIX-5177] - Support injecting configuration proxies * [FELIX-5180] - Support for Java8 Repeatable Properties in DM annotations. * [FELIX-5182] - Cleanup DM samples * [FELIX-5201] - Improve how components are displayed with gogo shell ** New Feature * [FELIX-4689] - Create a more fluent syntax for the dependency manager builder 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 r8 /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
[jira] [Updated] (FELIX-5146) Service adapters turn on autoconf even if callbacks are used
[
https://issues.apache.org/jira/browse/FELIX-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop updated FELIX-5146:
-
Fix Version/s: (was:org.apache.felix.dependencymanager-r7)
org.apache.felix.dependencymanager-r8
> Service adapters turn on autoconf even if callbacks are used
>
>
> Key: FELIX-5146
> URL: https://issues.apache.org/jira/browse/FELIX-5146
> Project: Felix
> Issue Type: Bug
> Components: Dependency Manager
>Affects Versions: org.apache.felix.dependencymanager-r1
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
>Priority: Minor
> Fix For: org.apache.felix.dependencymanager-r8
>
>
> in the previous DM 3 version, when you specify a service adapter without an
> autoconfig field and with some callbacks (and with or without a callback
> instance object), then auto config mode (on fields in the adapter class) is
> turned off.
> This is good, because mixing callbacks and auto-config mode (on class fields)
> may lead to bugs difficult to diagnose.
> in dm4, there is a mistake: when you specify a service adapter without an
> autoconfig field, but with callbacks on a callback instance, like this for
> example:
> {code}
> ServiceAdapterCallbackInstance callbackInstance =
> new ServiceAdapterCallbackInstance(e);
> m.createAdapterService(OriginalService.class, null, null, /* no autoconfig
> field */,
> callbackInstance, "set", "changed","unset", null, true)
> {code}
> then the adapter class fields are auto-configured, even if no auto config
> class field have been specified and if some callbacks have been specified.
> We should go back to the previous DM 3 behavior, which makes more sense: if
> some callbacks are defined and there is no autoconfig field, then do not
> enable auto-config mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5180) Support for Java8 Repeatable Properties in DM annotations.
[
https://issues.apache.org/jira/browse/FELIX-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop updated FELIX-5180:
-
Fix Version/s: (was:org.apache.felix.dependencymanager-r7)
org.apache.felix.dependencymanager-r8
> Support for Java8 Repeatable Properties in DM annotations.
> --
>
> Key: FELIX-5180
> URL: https://issues.apache.org/jira/browse/FELIX-5180
> Project: Felix
> Issue Type: Improvement
> Components: Dependency Manager Annotations
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
>Priority: Minor
> Fix For: org.apache.felix.dependencymanager-r8
>
>
> Currently, component properties can be declared in DM annotations using a
> "properties" attribute which accepts an array of @Property annotations.
> But since we are now using java8 for the R7 version, if would be nicer to
> support repeatable @Property annotations.
> For example:
> {code}
> @Component(provides=MyService.class)
> @Property(name="v1", value="s")
> @Property(name="v2", value={"s1", "s2"})
> @Property(name="v3", values={"s1", "s2"})
> public class MyServiceImpl implements MyService, Runnable {
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5164) Add support for callback instance in Aspects
[ https://issues.apache.org/jira/browse/FELIX-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5164: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > Add support for callback instance in Aspects > > > Key: FELIX-5164 > URL: https://issues.apache.org/jira/browse/FELIX-5164 > Project: Felix > Issue Type: Improvement > Components: Dependency Manager >Affects Versions: dependencymanager-3.2.0 >Reporter: Pierre De Rop >Assignee: Pierre De Rop > Fix For: org.apache.felix.dependencymanager-r8 > > > In the context of the new dependencymanager-lambda library, we need to be > able to specify an external callback instance for DM aspects (the same kind > of callback instances that are already supported by DM adapters). > The intent of this issue is to add support for such external callback > instance when using aspects; so a new method in DependencyManager interface > should be added take takes in parameter such callback instance. The callback > instance, if specified, will be invoked with "add/change/remove/swap" > callbacks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-5126) Build DM using Java 8
[ https://issues.apache.org/jira/browse/FELIX-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5126: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > Build DM using Java 8 > - > > Key: FELIX-5126 > URL: https://issues.apache.org/jira/browse/FELIX-5126 > 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-r7 >Reporter: Pierre De Rop >Assignee: Pierre De Rop > Fix For: org.apache.felix.dependencymanager-r8 > > > In the context of the new DM-lambda API (see FELIX-4689), the DM project must > now be built on top of Java 8. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-5177) Support injecting configuration proxies
[ https://issues.apache.org/jira/browse/FELIX-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5177: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > Support injecting configuration proxies > --- > > Key: FELIX-5177 > URL: https://issues.apache.org/jira/browse/FELIX-5177 > Project: Felix > Issue Type: Improvement > Components: Dependency Manager, Dependency Manager Annotations, > Dependency Manager Lambda, Dependency Manager Runtime >Reporter: J.W. Janssen >Assignee: Pierre De Rop > Fix For: org.apache.felix.dependencymanager-r8 > > Attachments: FELIX-5177.patch > > > DM supports mandatory configurations, but does not allow anything other than > a dictionary to be passed to the callback. In other DI frameworks (like DS) > it is possible to use type-safe configurations and let those be injected > instead of plain dictionaries. > It would be great if DM also would support this, as it would remove lots of > configuration boiler plate code from our projects. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-5201) Improve how components are displayed with gogo shell
[
https://issues.apache.org/jira/browse/FELIX-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop updated FELIX-5201:
-
Fix Version/s: (was:org.apache.felix.dependencymanager-r7)
org.apache.felix.dependencymanager-r8
> Improve how components are displayed with gogo shell
>
>
> Key: FELIX-5201
> URL: https://issues.apache.org/jira/browse/FELIX-5201
> Project: Felix
> Issue Type: Improvement
> Components: Dependency Manager
>Affects Versions: dependencymanager-3.2.0
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
>Priority: Minor
> Fix For: org.apache.felix.dependencymanager-r8
>
>
> When listing DM components with the gogo DM shell, components which are
> instantiated using a factory with Component.setFactory(...) method are
> displayed using the DM internal ComponentImpl class name.
> For example:
> {code}
> [0] org.apache.felix.dm.impl.ComponentImpl@3891771e registered
> org.osgi.service.cm.ConfigurationAdmin service required available
> {code}
> Now when a factory object is used as the component definition, it's not good
> to use the ComponentImpl classname as the component name and display it from
> gogo shell.
> Instead, the factory object instance itself should be displayed (or the
> component instance if it is already instantiated by the factory).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5182) Cleanup DM samples
[ https://issues.apache.org/jira/browse/FELIX-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5182: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > Cleanup DM samples > -- > > Key: FELIX-5182 > URL: https://issues.apache.org/jira/browse/FELIX-5182 > Project: Felix > Issue Type: Improvement > Components: Dependency Manager Samples >Affects Versions: org.apache.felix.dependencymanager-r1 >Reporter: Pierre De Rop >Assignee: Pierre De Rop >Priority: Minor > Fix For: org.apache.felix.dependencymanager-r8 > > > The DM samples should be reworked and there should be a bndrun descriptor for > each individual example, in order to allow to run the examples separately. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4689) Create a more fluent syntax for the dependency manager builder
[
https://issues.apache.org/jira/browse/FELIX-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop updated FELIX-4689:
-
Fix Version/s: (was:org.apache.felix.dependencymanager-r7)
org.apache.felix.dependencymanager-r8
> Create a more fluent syntax for the dependency manager builder
> --
>
> Key: FELIX-4689
> URL: https://issues.apache.org/jira/browse/FELIX-4689
> Project: Felix
> Issue Type: New Feature
> Components: Dependency Manager
>Reporter: Christian Schneider
>Assignee: Pierre De Rop
> Fix For: org.apache.felix.dependencymanager-r8
>
> Attachments: FELIX-4689-1.patch
>
>
> I wonder if the DependencyManager API could be made a bit more fluent.
> Technically it already uses the fluent builder pattern
> but all the builder verbs still look a lot like traditional setters.
> I know what I propose is mostly syntactic sugar but I think the result
> looks more readable and crisp. See below for some ideas.
> There is the concern about auto adding the component() to manager as it would
> acrivate the not fully configured component. We could perhaps overcome this
> by adding the component to a list of pending components first and then moving
> them to the active components after the init method.
> The camel DSL solves this similarly.
> This is from samples.dependonservice:
> public void init(BundleContext context, DependencyManager manager)
> throws Exception {
> manager.add(createComponent()
> .setImplementation(DataGenerator.class)
> .add(createServiceDependency()
> .setService(Store.class)
> .setRequired(true)
> )
> .add(createServiceDependency()
> .setService(LogService.class)
> .setRequired(false)
> )
> );
> }
> Why not make it look like this:
> public void init(BundleContext context, DependencyManager manager)
> throws Exception {
> component()
> .implementation(DataGenerator.class)
> .add(serviceDependency(Store.class).required())
> .add(serviceDependency(LogService.class))
> );
> );
> }
> component() could create and add the component.
> Or for configuration:
> public void init(BundleContext context, DependencyManager manager)
> throws Exception {
> manager.add(createComponent()
> .setImplementation(Task.class)
> .add(createConfigurationDependency()
> .setPid("config.pid")
> // The following is optional and allows to display our
> configuration from webconsole
> .setHeading("Task Configuration")
> .setDescription("Configuration for the Task Service")
> .add(createPropertyMetaData()
> .setCardinality(0)
> .setType(String.class)
> .setHeading("Task Interval")
> .setDescription("Declare here the interval used to
> trigger the Task")
> .setDefaults(new String[] {"10"})
> .setId("interval";
> }
> could be:
> public void init(BundleContext context, DependencyManager manager)
> throws Exception {
> component().implementation(Task.class)
> .configuration("config.pid")
> .add(meta("Task Configuration)
> .description("Configuration for the Task Service")
> .add(property("interval")
> .cardinality(0)
> .type(String.class)
> .heading("Task Interval")
> .description("Declare here the interval used
> to trigger the Task")
> .default("10"))
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5147) Bundle Adapter auto configures class fields even if callbacks are used
[ https://issues.apache.org/jira/browse/FELIX-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5147: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > Bundle Adapter auto configures class fields even if callbacks are used > -- > > Key: FELIX-5147 > URL: https://issues.apache.org/jira/browse/FELIX-5147 > Project: Felix > Issue Type: Bug > Components: Dependency Manager >Affects Versions: org.apache.felix.dependencymanager-r1 >Reporter: Pierre De Rop >Assignee: Pierre De Rop >Priority: Minor > Fix For: org.apache.felix.dependencymanager-r8 > > > When a bundle adapter is used with some callbacks (with or without a callback > instance), then any fields in the adapter class with type=Bundle are > auto-injected. > Normally, auto-configuration should be turned off when callbacks are used, > exactly in the same manner it is done with regular service dependencies, or > with service adapters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-5181) Only log info/debug if dm annotation log parameter is enabled
[ https://issues.apache.org/jira/browse/FELIX-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5181: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > Only log info/debug if dm annotation log parameter is enabled > - > > Key: FELIX-5181 > URL: https://issues.apache.org/jira/browse/FELIX-5181 > Project: Felix > Issue Type: Bug > Components: Dependency Manager Runtime >Affects Versions: dependencymanager.runtime-3.2.0 >Reporter: Pierre De Rop >Assignee: Pierre De Rop >Priority: Minor > Fix For: org.apache.felix.dependencymanager-r8 > > > Currently, the DM annotation runtime logs info/debug messages to any > available log service, even if the > "org.apache.felix.dependencymanager.runtime.log" system property is not set, > or is set to "false". > When such property is not configured or is set to "false", then the dm > runtime should only log error/warn messages, and not info/debug. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-5178) Make some component parameters as volatile
[ https://issues.apache.org/jira/browse/FELIX-5178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5178: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > Make some component parameters as volatile > -- > > Key: FELIX-5178 > URL: https://issues.apache.org/jira/browse/FELIX-5178 > Project: Felix > Issue Type: Bug > Components: Dependency Manager, Dependency Manager Lambda >Affects Versions: org.apache.felix.dependencymanager-r1 >Reporter: Pierre De Rop >Assignee: Pierre De Rop > Fix For: org.apache.felix.dependencymanager-r8 > > > Currently, all parameters passed to components/dependencies API are stored in > non volatile variables, because internally, we are using a concurrent queue, > which ensures "safe publication" regarding memory visibility. > Now, this is all fine, except for the following case: > - The application creates and initialize a Component from one thread T1. > - Then later, from thread T2, the application starts the component (adds it > to a DependencyManager object). > In this case, we should declare all API parameters in volatile attributes in > order to ensure safe visibility from T2 thread, when accessing to parameters > that were set in the original T1 thread. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-5155) Adapter/Aspect extra service dependencies injected twice if using callback instance
[ https://issues.apache.org/jira/browse/FELIX-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5155: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > Adapter/Aspect extra service dependencies injected twice if using callback > instance > --- > > Key: FELIX-5155 > URL: https://issues.apache.org/jira/browse/FELIX-5155 > Project: Felix > Issue Type: Bug > Components: Dependency Manager >Affects Versions: dependencymanager-3.0.0 >Reporter: Pierre De Rop >Assignee: Pierre De Rop > Fix For: org.apache.felix.dependencymanager-r8 > > > In the context of the new DM-lambda library, we found the following issue: > When an aspect or an adapter is defined on an existing service, and if such > aspect (or adapter) declares some extra service dependencies, and if one of > these extra dependencies are using an external callback instance (in order to > inject the extra dependency into the adapter or aspect instance), then the > callback instance is invoked twice: > The first time, the callback instance is wrongly called by the internal > aspect (or adapter) AbstractDecorator component, and the second time it is > correctly called in order to inject the dependency into the callback instance. > I have written a test case which reproduces this issue and will commit it > soon. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-5187) No errog log when configuration dependency callback is not found
[ https://issues.apache.org/jira/browse/FELIX-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5187: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > No errog log when configuration dependency callback is not found > > > Key: FELIX-5187 > URL: https://issues.apache.org/jira/browse/FELIX-5187 > Project: Felix > Issue Type: Bug > Components: Dependency Manager >Affects Versions: dependencymanager-2.0.1 >Reporter: Pierre De Rop >Assignee: Pierre De Rop > Fix For: org.apache.felix.dependencymanager-r8 > > > if a configuration dependency is defined using a non-existing callback method > name, then currently, no error is logged and the callback is simply not > invoked when a configuration becomes available. > An error log must be displayed in such case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-5153) DM4 calls stop before ungetService() on ServiceFactory components
[ https://issues.apache.org/jira/browse/FELIX-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5153: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > DM4 calls stop before ungetService() on ServiceFactory components > - > > Key: FELIX-5153 > URL: https://issues.apache.org/jira/browse/FELIX-5153 > Project: Felix > Issue Type: Bug > Components: Dependency Manager >Reporter: Bram de Kruijff >Assignee: Pierre De Rop >Priority: Critical > Fix For: org.apache.felix.dependencymanager-r8 > > > When you remove a ServiceFactory component DM4 will call the stop method > before the the framework has called ungetService() for all service instances. > This seems to be a regression from DM3 and breaks any implementation that > relies on previous behavior for cleanup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-5193) Factory Pid Adapter race condition when component is stopped
[ https://issues.apache.org/jira/browse/FELIX-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5193: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > Factory Pid Adapter race condition when component is stopped > > > Key: FELIX-5193 > URL: https://issues.apache.org/jira/browse/FELIX-5193 > Project: Felix > Issue Type: Bug > Components: Dependency Manager >Affects Versions: dependencymanager-3.2.0 >Reporter: Pierre De Rop >Assignee: Pierre De Rop > Fix For: org.apache.felix.dependencymanager-r8 > > > When a factory pid adapter component is being removed (stopped), and at the > same time the factory configuration is updated, the handling of the factory > configuration update > may take place while the factory pid component is being destroyed. > The factory conf update must be handled synchronously, but from the factory > pid adapter component internal executor queue, in order to avoid all sort of > racy problems. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-5188) No error log when a factory pid adapter update callback is not found
[ https://issues.apache.org/jira/browse/FELIX-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5188: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > No error log when a factory pid adapter update callback is not found > > > Key: FELIX-5188 > URL: https://issues.apache.org/jira/browse/FELIX-5188 > Project: Felix > Issue Type: Bug >Affects Versions: dependencymanager-2.0.1 >Reporter: Pierre De Rop >Assignee: Pierre De Rop > Fix For: org.apache.felix.dependencymanager-r8 > > > No errors are logged when a factory pid adapter is wrongly configured with an > update callback that does not exist. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-5200) Factory configuration adapter not restarted
[
https://issues.apache.org/jira/browse/FELIX-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop updated FELIX-5200:
-
Fix Version/s: (was:org.apache.felix.dependencymanager-r7)
org.apache.felix.dependencymanager-r8
> Factory configuration adapter not restarted
> ---
>
> Key: FELIX-5200
> URL: https://issues.apache.org/jira/browse/FELIX-5200
> Project: Felix
> Issue Type: Bug
> Components: Dependency Manager
>Affects Versions: org.apache.felix.dependencymanager-r1
>Reporter: Pierre De Rop
>Assignee: Pierre De Rop
> Fix For: org.apache.felix.dependencymanager-r8
>
>
> When a factory pid adapter is losing one of its required service
> dependencies, it is stopped, but when the lost dependency comes up again, the
> configuration adapter instance is not re-created and re-started.
> Example:
> * A factory configuration adapter has a required dependency on a "Required"
> service.
> * The factory configuration is created, the "Required" service is
> registered, so a factory configuration adapter INSTANCE1 is then created.
> * Now the "Required" service is unregistered: the INSTANCE1 is then stopped.
> * And when the "Required" service comes up again, then a new factory config
> adapter INSTANCE2 should be re-created, updated and started, But since R1
> this is not the case anymore.
> The bug is located in the AbstractDecorator.stop() method, this method
> currently does this:
> {code}
> public void stop() {
> for (Component component : m_services.values()) {
> m_manager.remove(component);
> }
> }
> {code}
> Clearly, this is a bug because the "m_services" list is not cleared, so when
> the AbstractDecorator.updated(String, Dictionary) method is called again, it
> finds again some old stale components, and updates them instead of
> re-creating new adapter instances.
> In DM3, the list was correctly cleared:
> {code}
> public void stop() {
> Object[] components;
> synchronized (m_services) {
> components = m_services.values().toArray();
> m_services.clear();
> }
> for (int i = 0; i < components.length; i++) {
> m_manager.remove((Component) components[i]);
> }
> }
> {code}
> I will add a test case soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5192) ConfigurationDependency race condition when component is stopped
[ https://issues.apache.org/jira/browse/FELIX-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-5192: - Fix Version/s: (was:org.apache.felix.dependencymanager-r7) org.apache.felix.dependencymanager-r8 > ConfigurationDependency race condition when component is stopped > > > Key: FELIX-5192 > URL: https://issues.apache.org/jira/browse/FELIX-5192 > Project: Felix > Issue Type: Bug > Components: Dependency Manager >Affects Versions: org.apache.felix.dependencymanager-r1 >Reporter: Pierre De Rop >Assignee: Pierre De Rop > Fix For: org.apache.felix.dependencymanager-r8 > > > When a component is being removed (stopped) and at the same time a > configuration is updated or removed, then it may be possible that > the configuration dependency invokes the updated callback after the component > instance has been destroyed and nullified. > So far, this was never observed because we did not log any warnings when a > configuration callback was unavailable, but now we log a warn (see > FELIX-5187). > The fix to do is simply to check if the configuration dependency is started > before invoking the update callback method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] felix pull request: FELIX-5203 Remove unused org.apache.felix.http...
Github user cpilsworth closed the pull request at: https://github.com/apache/felix/pull/55 --- 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. ---
[jira] [Commented] (FELIX-5203) Remove unused org.apache.felix.http.debug configuration property
[
https://issues.apache.org/jira/browse/FELIX-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174486#comment-15174486
]
ASF GitHub Bot commented on FELIX-5203:
---
Github user cpilsworth closed the pull request at:
https://github.com/apache/felix/pull/55
> Remove unused org.apache.felix.http.debug configuration property
>
>
> Key: FELIX-5203
> URL: https://issues.apache.org/jira/browse/FELIX-5203
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
>Affects Versions: http.jetty-3.1.6
>Reporter: Chris Pilsworth
>Assignee: Carsten Ziegeler
>Priority: Minor
> Labels: configuration
> Fix For: http.jetty-3.2.0
>
>
> The {{org.apache.felix.http.jetty}} bundle has a "Debug Logging" boolean
> property ({{org.apache.felix.http.debug}}) which is unused. This property
> is only used by the internal {{JettyConfig.isDebug}} method, which is in turn
> unused.
> Jetty debug logging is now handed by filtering the logger category.
> See:
> [http://www.mail-archive.com/users%40felix.apache.org/msg17122.html]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] felix pull request: FELIX-5203 Remove unused org.apache.felix.http...
GitHub user cpilsworth opened a pull request: https://github.com/apache/felix/pull/55 FELIX-5203 Remove unused org.apache.felix.http.debug property from http service The `org.apache.felix.http.jetty` bundle has a "Debug Logging" boolean property (`org.apache.felix.http.debug`) which is unused. This property is only used by the internal JettyConfig.isDebug method, which is in turn is unused. Jetty debug logging is now handed by filtering the logger category. See: http://www.mail-archive.com/users%40felix.apache.org/msg17122.html You can merge this pull request into a Git repository by running: $ git pull https://github.com/cpilsworth/felix fix/felix-5203-remove-unused-debug-flag Alternatively you can review and apply these changes as the patch at: https://github.com/apache/felix/pull/55.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 #55 commit 25ed38cf0ec55611a2ae6d7acbcd48f2ed2fe725 Author: Chris Pilsworth Date: 2016-03-01T15:56:15Z FELIX-5203 Remove unused org.apache.felix.http.debug property from http service --- 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. ---
[GitHub] felix pull request: Obr capability attribute fix
Github user skahmann closed the pull request at: https://github.com/apache/felix/pull/52 --- 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. ---
[jira] [Resolved] (FELIX-5203) Remove unused org.apache.felix.http.debug configuration property
[
https://issues.apache.org/jira/browse/FELIX-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-5203.
-
Resolution: Fixed
Thanks for your patch, Chris. It's applied with rev 1733098
> Remove unused org.apache.felix.http.debug configuration property
>
>
> Key: FELIX-5203
> URL: https://issues.apache.org/jira/browse/FELIX-5203
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
>Affects Versions: http.jetty-3.1.6
>Reporter: Chris Pilsworth
>Assignee: Carsten Ziegeler
>Priority: Minor
> Labels: configuration
> Fix For: http.jetty-3.2.0
>
>
> The {{org.apache.felix.http.jetty}} bundle has a "Debug Logging" boolean
> property ({{org.apache.felix.http.debug}}) which is unused. This property
> is only used by the internal {{JettyConfig.isDebug}} method, which is in turn
> unused.
> Jetty debug logging is now handed by filtering the logger category.
> See:
> [http://www.mail-archive.com/users%40felix.apache.org/msg17122.html]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (FELIX-5203) Remove unused org.apache.felix.http.debug configuration property
[
https://issues.apache.org/jira/browse/FELIX-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned FELIX-5203:
---
Assignee: Carsten Ziegeler
> Remove unused org.apache.felix.http.debug configuration property
>
>
> Key: FELIX-5203
> URL: https://issues.apache.org/jira/browse/FELIX-5203
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
>Affects Versions: http.jetty-3.1.6
>Reporter: Chris Pilsworth
>Assignee: Carsten Ziegeler
>Priority: Minor
> Labels: configuration
> Fix For: http.jetty-3.2.0
>
>
> The {{org.apache.felix.http.jetty}} bundle has a "Debug Logging" boolean
> property ({{org.apache.felix.http.debug}}) which is unused. This property
> is only used by the internal {{JettyConfig.isDebug}} method, which is in turn
> unused.
> Jetty debug logging is now handed by filtering the logger category.
> See:
> [http://www.mail-archive.com/users%40felix.apache.org/msg17122.html]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5203) Remove unused org.apache.felix.http.debug configuration property
[
https://issues.apache.org/jira/browse/FELIX-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-5203:
Fix Version/s: http.jetty-3.2.0
> Remove unused org.apache.felix.http.debug configuration property
>
>
> Key: FELIX-5203
> URL: https://issues.apache.org/jira/browse/FELIX-5203
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
>Affects Versions: http.jetty-3.1.6
>Reporter: Chris Pilsworth
>Priority: Minor
> Labels: configuration
> Fix For: http.jetty-3.2.0
>
>
> The {{org.apache.felix.http.jetty}} bundle has a "Debug Logging" boolean
> property ({{org.apache.felix.http.debug}}) which is unused. This property
> is only used by the internal {{JettyConfig.isDebug}} method, which is in turn
> unused.
> Jetty debug logging is now handed by filtering the logger category.
> See:
> [http://www.mail-archive.com/users%40felix.apache.org/msg17122.html]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FELIX-5203) Remove unused org.apache.felix.http.debug configuration property
[
https://issues.apache.org/jira/browse/FELIX-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173950#comment-15173950
]
ASF GitHub Bot commented on FELIX-5203:
---
GitHub user cpilsworth opened a pull request:
https://github.com/apache/felix/pull/55
FELIX-5203 Remove unused org.apache.felix.http.debug property from http
service
The `org.apache.felix.http.jetty` bundle has a "Debug Logging" boolean
property (`org.apache.felix.http.debug`) which is unused. This property is only
used by the internal JettyConfig.isDebug method, which is in turn is unused.
Jetty debug logging is now handed by filtering the logger category.
See:
http://www.mail-archive.com/users%40felix.apache.org/msg17122.html
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cpilsworth/felix
fix/felix-5203-remove-unused-debug-flag
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/felix/pull/55.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 #55
commit 25ed38cf0ec55611a2ae6d7acbcd48f2ed2fe725
Author: Chris Pilsworth
Date: 2016-03-01T15:56:15Z
FELIX-5203 Remove unused org.apache.felix.http.debug property from http
service
> Remove unused org.apache.felix.http.debug configuration property
>
>
> Key: FELIX-5203
> URL: https://issues.apache.org/jira/browse/FELIX-5203
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
>Affects Versions: http.jetty-3.1.6
>Reporter: Chris Pilsworth
>Priority: Minor
> Labels: configuration
>
> The {{org.apache.felix.http.jetty}} bundle has a "Debug Logging" boolean
> property ({{org.apache.felix.http.debug}}) which is unused. This property
> is only used by the internal {{JettyConfig.isDebug}} method, which is in turn
> unused.
> Jetty debug logging is not handed by filtering the logger category.
> See:
> [http://www.mail-archive.com/users%40felix.apache.org/msg17122.html]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5203) Remove unused org.apache.felix.http.debug configuration property
[
https://issues.apache.org/jira/browse/FELIX-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Pilsworth updated FELIX-5203:
---
Description:
The {{org.apache.felix.http.jetty}} bundle has a "Debug Logging" boolean
property ({{org.apache.felix.http.debug}}) which is unused. This property is
only used by the internal {{JettyConfig.isDebug}} method, which is in turn
unused.
Jetty debug logging is now handed by filtering the logger category.
See:
[http://www.mail-archive.com/users%40felix.apache.org/msg17122.html]
was:
The {{org.apache.felix.http.jetty}} bundle has a "Debug Logging" boolean
property ({{org.apache.felix.http.debug}}) which is unused. This property is
only used by the internal {{JettyConfig.isDebug}} method, which is in turn
unused.
Jetty debug logging is not handed by filtering the logger category.
See:
[http://www.mail-archive.com/users%40felix.apache.org/msg17122.html]
> Remove unused org.apache.felix.http.debug configuration property
>
>
> Key: FELIX-5203
> URL: https://issues.apache.org/jira/browse/FELIX-5203
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
>Affects Versions: http.jetty-3.1.6
>Reporter: Chris Pilsworth
>Priority: Minor
> Labels: configuration
>
> The {{org.apache.felix.http.jetty}} bundle has a "Debug Logging" boolean
> property ({{org.apache.felix.http.debug}}) which is unused. This property
> is only used by the internal {{JettyConfig.isDebug}} method, which is in turn
> unused.
> Jetty debug logging is now handed by filtering the logger category.
> See:
> [http://www.mail-archive.com/users%40felix.apache.org/msg17122.html]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5203) Remove unused org.apache.felix.http.debug configuration property
[
https://issues.apache.org/jira/browse/FELIX-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Pilsworth updated FELIX-5203:
---
Description:
The {{org.apache.felix.http.jetty}} bundle has a "Debug Logging" boolean
property ({{org.apache.felix.http.debug}}) which is unused. This property is
only used by the internal {{JettyConfig.isDebug}} method, which is in turn
unused.
Jetty debug logging is not handed by filtering the logger category.
See:
[http://www.mail-archive.com/users%40felix.apache.org/msg17122.html]
was:
The org.apache.felix.http.jetty bundle has a "Debug Logging" boolean property
(org.apache.felix.http.debug) which is unused. This property is only used by
the internal JettyConfig.isDebug method, which is in turn unused.
Jetty debug logging is not handed by filtering the logger category.
See:
http://www.mail-archive.com/users%40felix.apache.org/msg17122.html
> Remove unused org.apache.felix.http.debug configuration property
>
>
> Key: FELIX-5203
> URL: https://issues.apache.org/jira/browse/FELIX-5203
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
>Affects Versions: http.jetty-3.1.6
>Reporter: Chris Pilsworth
>Priority: Minor
> Labels: configuration
>
> The {{org.apache.felix.http.jetty}} bundle has a "Debug Logging" boolean
> property ({{org.apache.felix.http.debug}}) which is unused. This property
> is only used by the internal {{JettyConfig.isDebug}} method, which is in turn
> unused.
> Jetty debug logging is not handed by filtering the logger category.
> See:
> [http://www.mail-archive.com/users%40felix.apache.org/msg17122.html]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FELIX-5196) Capabilities not matching because of case
[ https://issues.apache.org/jira/browse/FELIX-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173943#comment-15173943 ] Stephen Kahmann commented on FELIX-5196: PR: https://github.com/apache/felix/pull/54 > Capabilities not matching because of case > - > > Key: FELIX-5196 > URL: https://issues.apache.org/jira/browse/FELIX-5196 > Project: Felix > Issue Type: Bug > Components: Bundle Repository (OBR) >Affects Versions: bundlerepository-2.0.6 >Reporter: Stephen Kahmann > > RequirementImpl is not matching Capabilities because it is using a filter > that ignores case. The Filter lowercases the keys, but this is also not done > when trying to match them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-5203) Remove unused org.apache.felix.http.debug configuration property
Chris Pilsworth created FELIX-5203: -- Summary: Remove unused org.apache.felix.http.debug configuration property Key: FELIX-5203 URL: https://issues.apache.org/jira/browse/FELIX-5203 Project: Felix Issue Type: Improvement Components: HTTP Service Affects Versions: http.jetty-3.1.6 Reporter: Chris Pilsworth Priority: Minor The org.apache.felix.http.jetty bundle has a "Debug Logging" boolean property (org.apache.felix.http.debug) which is unused. This property is only used by the internal JettyConfig.isDebug method, which is in turn unused. Jetty debug logging is not handed by filtering the logger category. See: http://www.mail-archive.com/users%40felix.apache.org/msg17122.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-5196) Capabilities not matching because of case
[ https://issues.apache.org/jira/browse/FELIX-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173920#comment-15173920 ] Stephen Kahmann commented on FELIX-5196: Updated with recent bundlerepository commits and ready for review. > Capabilities not matching because of case > - > > Key: FELIX-5196 > URL: https://issues.apache.org/jira/browse/FELIX-5196 > Project: Felix > Issue Type: Bug > Components: Bundle Repository (OBR) >Affects Versions: bundlerepository-2.0.6 >Reporter: Stephen Kahmann > > RequirementImpl is not matching Capabilities because it is using a filter > that ignores case. The Filter lowercases the keys, but this is also not done > when trying to match them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-5189) OBR R5 Capabilities are not Properly being Parsed
[ https://issues.apache.org/jira/browse/FELIX-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173909#comment-15173909 ] ASF GitHub Bot commented on FELIX-5189: --- Github user skahmann closed the pull request at: https://github.com/apache/felix/pull/52 > OBR R5 Capabilities are not Properly being Parsed > - > > Key: FELIX-5189 > URL: https://issues.apache.org/jira/browse/FELIX-5189 > Project: Felix > Issue Type: Bug > Components: Bundle Repository (OBR) >Affects Versions: bundlerepository-2.0.6 >Reporter: Stephen Kahmann >Assignee: Richard S. Hall > Fix For: bundlerepository-2.0.8 > > > Capabilities are not correctly being parsed for the R5 spec. The > "osgi.wiring.package" attribute is being compared to "package" which always > fails to match. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] felix pull request: Fix Provide-Capability
Github user asfgit closed the pull request at: https://github.com/apache/felix/pull/53 --- 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. ---
[jira] [Resolved] (FELIX-5195) Provide-Capability not being processed for Resources
[ https://issues.apache.org/jira/browse/FELIX-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved FELIX-5195. - Resolution: Fixed Fix Version/s: bundlerepository-2.0.8 Many thanks for your patch [~skahmann]! I've applied it in https://svn.apache.org/viewvc?view=revision&revision=1733051 > Provide-Capability not being processed for Resources > > > Key: FELIX-5195 > URL: https://issues.apache.org/jira/browse/FELIX-5195 > Project: Felix > Issue Type: Bug > Components: Bundle Repository (OBR) >Affects Versions: bundlerepository-2.0.6 >Reporter: Stephen Kahmann >Assignee: David Bosschaert > Fix For: bundlerepository-2.0.8 > > > Capabilities provided using Provide-Capability are not being added to > Resources. PR Created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (FELIX-5195) Provide-Capability not being processed for Resources
[ https://issues.apache.org/jira/browse/FELIX-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-5195 started by David Bosschaert. --- > Provide-Capability not being processed for Resources > > > Key: FELIX-5195 > URL: https://issues.apache.org/jira/browse/FELIX-5195 > Project: Felix > Issue Type: Bug > Components: Bundle Repository (OBR) >Affects Versions: bundlerepository-2.0.6 >Reporter: Stephen Kahmann >Assignee: David Bosschaert > > Capabilities provided using Provide-Capability are not being added to > Resources. PR Created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [CANCEL] [VOTE] Apache Felix Dependency Manager Release R7
Hi Bram; Thanks ! I look look into it before redoing the release. regards /pierre On Tue, Mar 1, 2016 at 11:13 AM, Bram Pouwelse wrote: > Hi Pierre, > > The license-gradle-plugin [1] might be a useful gradle plugin to help > prevent this in the future, we use it in the Amdatu builds (must admit that > sometimes it's annoying as it fails the build when you forgot to add a > license header ;) ) > > Regards, > Bram > > 1: https://github.com/hierynomus/license-gradle-plugin > > On Tue, Mar 1, 2016 at 11:02 AM Pierre De Rop > wrote: > > > I'm canceling the vote for the DM r7 release because I forgot to include > > the license files in the new org.apache.felix.dependencymanager.lambda > > bundle. > > > > I will restart a vote with a new r8 version. > > > > regards; > > /Pierre > > >
Re: [CANCEL] [VOTE] Apache Felix Dependency Manager Release R7
Hi Pierre, The license-gradle-plugin [1] might be a useful gradle plugin to help prevent this in the future, we use it in the Amdatu builds (must admit that sometimes it's annoying as it fails the build when you forgot to add a license header ;) ) Regards, Bram 1: https://github.com/hierynomus/license-gradle-plugin On Tue, Mar 1, 2016 at 11:02 AM Pierre De Rop wrote: > I'm canceling the vote for the DM r7 release because I forgot to include > the license files in the new org.apache.felix.dependencymanager.lambda > bundle. > > I will restart a vote with a new r8 version. > > regards; > /Pierre >
[CANCEL] [VOTE] Apache Felix Dependency Manager Release R7
I'm canceling the vote for the DM r7 release because I forgot to include the license files in the new org.apache.felix.dependencymanager.lambda bundle. I will restart a vote with a new r8 version. regards; /Pierre
Re: [VOTE] Apache Felix Dependency Manager Release R7
ok, thanks Marcel. I will restart the vote today. On Tue, Mar 1, 2016 at 10:38 AM, Marcel Offermans < marcel.offerm...@luminis.nl> wrote: > Hello Pierre, > On 1 March 2016 at 10:01:01, Pierre De Rop (pierre.de...@gmail.com) wrote: > > (I don't know if I *must* wait for 72 hours before canceling and > restarting > the vote, or if I can restart it today ?) > No need to wait, just start a new vote today. > > Greetings, Marcel > > > >
Re: [VOTE] Apache Felix Dependency Manager Release R7
Hello Pierre, On 1 March 2016 at 10:01:01, Pierre De Rop (pierre.de...@gmail.com) wrote: (I don't know if I *must* wait for 72 hours before canceling and restarting the vote, or if I can restart it today ?) No need to wait, just start a new vote today. Greetings, Marcel
Re: [VOTE] Apache Felix Dependency Manager Release R7
oops, I realize I forgot to include the license files in the org.apache.felix.dependencymanager.lambda-1.0.0.jar bundle. I'm afraid I have to vote -1 for myself ! -1: the official Apache license files are missing from the new dm-lambda library. (I don't know if I *must* wait for 72 hours before canceling and restarting the vote, or if I can restart it today ?) apologies ... /Pierre On Sun, Feb 28, 2016 at 11:11 PM, Pierre De Rop wrote: > Hello all, > > We would like to call for a vote on the Dependency Manager toplevel > release R7. > > Apart from being a maintenance release, the r7 release includes some new > features > like "configuration types" and a new "DM-lambda" library, which is > described here: > > > http://felix.staging.apache.org/documentation/subprojects/apache-felix-dependency-manager/guides/dm-lambda.html > > The R7 now requires the usage of a recent JAVA8 jdk (the new version has > been built and tested with latest version 1.8.74) > > The following issues were solved: > > ** Bug > * [FELIX-5146] - Service adapters turn on autoconf even if callbacks > are used > * [FELIX-5147] - Bundle Adapter auto configures class fields even if > callbacks are used > * [FELIX-5153] - DM4 calls stop before ungetService() on > ServiceFactory components > * [FELIX-5155] - Adapter/Aspect extra service dependencies injected > twice if using callback instance > * [FELIX-5178] - Make some component parameters as volatile > * [FELIX-5181] - Only log info/debug if dm annotation log parameter is > enabled > * [FELIX-5187] - No errog log when configuration dependency callback > is not found > * [FELIX-5188] - No error log when a factory pid adapter update > callback is not found > * [FELIX-5192] - ConfigurationDependency race condition when component > is stopped > * [FELIX-5193] - Factory Pid Adapter race condition when component is > stopped > * [FELIX-5200] - Factory configuration adapter not restarted > > ** Improvement > * [FELIX-5126] - Build DM using Java 8 > * [FELIX-5164] - Add support for callback instance in Aspects > * [FELIX-5177] - Support injecting configuration proxies > * [FELIX-5180] - Support for Java8 Repeatable Properties in DM > annotations. > * [FELIX-5182] - Cleanup DM samples > * [FELIX-5201] - Improve how components are displayed with gogo shell > > ** New Feature > * [FELIX-4689] - Create a more fluent syntax for the dependency > manager builder > > > 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 r7 /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 >
