Hello all,
I would like to call for a vote on the Dependency Manager toplevel release
R4.
We solved the following issues:
Release Notes - Felix - Version org.apache.felix.dependencymanager-r4
** Bug
* [FELIX-4907] - ConfigurationDependency calls updated(null) when
component is stopped.
[
https://issues.apache.org/jira/browse/FELIX-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop resolved FELIX-4877.
--
Resolution: Fixed
Updated bundle version to 4.0.2
> DM Annotations should detect service type u
[
https://issues.apache.org/jira/browse/FELIX-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop resolved FELIX-4876.
--
Resolution: Fixed
Updated bundle version to 4.0.2
> DM Annotations bnd plugin compatibility wit
[
https://issues.apache.org/jira/browse/FELIX-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop resolved FELIX-4907.
--
Resolution: Fixed
Thanks, I have committed the patches, and updated the
ConfigurationDependency
[
https://issues.apache.org/jira/browse/FELIX-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop resolved FELIX-4913.
--
Resolution: Fixed
> DM Optional callbacks may sometimes be invoked twice
> -
[
https://issues.apache.org/jira/browse/FELIX-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop resolved FELIX-4910.
--
Resolution: Fixed
Fixed in the trunk.
> ComponentExecutorFactory does not allow to return null
Thanks Pierre, that did the trick! I didn't realise that this page was
going through the same 'intuitive' cms that is used for the rest of
the website...
David
On 4 June 2015 at 16:00, Pierre De Rop wrote:
> Hello David,
>
> I think you just have to publish the site from
> https://cms.apache.org
Hello David,
I think you just have to publish the site from
https://cms.apache.org/felix/publish
(if yo click on Diff, you will see your last commit, so, just submit it, it
should work ... hopefully).
cheers;
/Pierre
On Thu, Jun 4, 2015 at 4:42 PM, David Bosschaert wrote:
> Hmmm, I guess nobo
At Karaf we basically just copy over the artifacts from nexus staging
to apache, where we then svn add & checkin the resources.
We're only working with a few dozen files however per release. Not
sure if there is anything automated out there...
Cheers,
Jamie
On Thu, Jun 4, 2015 at 12:12 PM, David
Hmmm, I guess nobody has a smarter way to do this ;) So I went ahead
and did my manual thing again... I guess I could write a little shell
script to do it...
I uploaded the artifacts (configadmin 1.8.6) to
https://dist.apache.org/repos/dist/release/felix and updated the
content/downloads.list in
h
[
https://issues.apache.org/jira/browse/FELIX-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sateesh updated FELIX-4911:
---
Priority: Major (was: Blocker)
> Ipojo war file not generating the manipulated class
> --
[
https://issues.apache.org/jira/browse/FELIX-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572508#comment-14572508
]
Pierre De Rop commented on FELIX-4913:
--
Commited the patch in 1683504.
Now, a hashta
12 matches
Mail list logo
