[
https://issues.apache.org/jira/browse/FELIX-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588995#action_12588995
]
James Rowe commented on FELIX-532:
--
Sorry, I admit that I was trusting eclipse PDE too much
Create a standard legend for bundle subprojects to clearly indicate
compatibility statement
---
Key: FELIX-537
URL: https://issues.apache.org/jira/browse/FELIX-537
Create a really lightweight version of the HTTP Service
---
Key: FELIX-538
URL: https://issues.apache.org/jira/browse/FELIX-538
Project: Felix
Issue Type: New Feature
Reporter:
[
https://issues.apache.org/jira/browse/FELIX-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589123#action_12589123
]
Richard S. Hall commented on FELIX-538:
---
Here is the URL of the web server in my SVN s
[
https://issues.apache.org/jira/browse/FELIX-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall updated FELIX-538:
--
Component/s: HTTP Service
> Create a really lightweight version of the HTTP Service
> --
Hi,
I think we could remove those projects from our commons list that now
include osgi meta information like some of the apache commons (io etc.).
We could also remove some of the specs as they are available as osgi
bundles from geronimo.
If noone objects, I'll remove them in the next days.
I agree. The whole point of Felix Commons was to serve as a stopgap
measure until the original communities started supporting OSGi metadata.
So, there is no point in keeping stuff around once this happens.
-> richard
Carsten Ziegeler wrote:
Hi,
I think we could remove those projects from our
Dear all,
I added the UPnP documentation in the trunk/upnp/doc directory.
Now, I should generate web pages with the Felix documentation style.
How does it works? Is there any tool?
francesco
