I like that approach as well, if there is no objections I'll do it like
that.
-Georg
On 2019-02-12 07:07, Christian Schneider wrote:
+1 for using markup files in github for documentation.
It is a bit inconvenient as long as we are not on git natively .. but I
hope this soon changes.
[
https://issues.apache.org/jira/browse/FELIX-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766579#comment-16766579
]
Thomas Watson commented on FELIX-6056:
--
OK, I think we should change to not export promises or
+1 for using markup files in github for documentation.
It is a bit inconvenient as long as we are not on git natively .. but I
hope this soon changes.
Christian
Am Di., 12. Feb. 2019 um 14:00 Uhr schrieb Bertrand Delacretaz <
bdelacre...@apache.org>:
> Hi Georg,
>
> On Mon, Jan 28, 2019 at
[
https://issues.apache.org/jira/browse/FELIX-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766042#comment-16766042
]
Peter Kriens commented on FELIX-6056:
-
Yes, the API dependency is unfortunate since very few bundles
[
https://issues.apache.org/jira/browse/FELIX-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls reassigned FELIX-6043:
-
Assignee: Thomas Watson
> ClassNotFoundException org.osgi.util.function.Function
>
[
https://issues.apache.org/jira/browse/FELIX-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766024#comment-16766024
]
Thomas Watson commented on FELIX-6056:
--
Also see FELIX-6043. I'm perfectly fine having promises be
Peter Kriens created FELIX-6056:
---
Summary: SCR exports promises
Key: FELIX-6056
URL: https://issues.apache.org/jira/browse/FELIX-6056
Project: Felix
Issue Type: Bug
Components:
Hi Georg,
On Mon, Jan 28, 2019 at 12:50 AM Georg Henzler wrote:
> ...I would like to
> move the documentation in the markdown file [3] to the correct location
> which I believe is a sub page "Apache Felix Health Checks" underneath
> [4],...
Many projects today just use those Markdown files in
