Hi Ray,
so I did mention the "2.x.x " approach in the initial ticket and it
hasn't change since then [1]. But I know it's hard to always keep track
of all JIRA comments.
but I feel this is not a great approach to take.
So to me it really boils down to not counting down when moving
Hi, I just wanted to notify the community that we are working to push in a
change to felix gogo for the command, runtime and shell to move their
source and target level to java 1.7. They are currently at 1.8. Much as we
prefer 1.8 we have a near term business requirement to produce bundles
Dear adaptTo() Community,
the sale of tickets for adaptTo() 2019 is open.
This year's conference date is 2nd - 4th September; and we'll be back in
downtown Berlin at the legendary venue, the Kosmos!
https://eng.kosmos-berlin.de/
Get your Early-Bird-Ticket here: https://adapt.to/tickets
We
This is not unusual during a release but it makes building from current
source a bit difficult.
Christian
Am Do., 31. Jan. 2019 um 22:11 Uhr schrieb Raymond Auge <
raymond.a...@liferay.com>:
> Why do the modules org.apache.felix.healthcheck.core depend on
>
>
>
hm, ok! Good enough.
-Ray
On Thu, Jan 31, 2019 at 4:31 PM Karl Pauls wrote:
> org.apache.felix.healthcheck.api-2.0.0 is part of the release:
>
>
> https://repository.apache.org/content/repositories/orgapachefelix-1279/org/apache/felix/org.apache.felix.healthcheck.api/2.0.0/
>
> You have to
org.apache.felix.healthcheck.api-2.0.0 is part of the release:
https://repository.apache.org/content/repositories/orgapachefelix-1279/org/apache/felix/org.apache.felix.healthcheck.api/2.0.0/
You have to build it first - then the rest should work (it did for me).
regards,
Karl
On Thu, Jan 31,
I think the version 2.0.0 is weird when this is a new project in the
org.apache.felix namespace.
It doesn't matter that it previously had a higher version in some other
namespace.
I really recommend just making this either a 0.1.0 or 1.0.0 release. I will
not vito the release or anything if it
Why do the modules org.apache.felix.healthcheck.core depend on
org.apache.felix
org.apache.felix.healthcheck.api
2.0.0
provided
when that artifact does not exist?
I only see a 2.0.1-SNAPSHOT
Same goes for
[
https://issues.apache.org/jira/browse/FELIX-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16757631#comment-16757631
]
Thomas Watson commented on FELIX-6043:
--
This is the unfortunate consequence of embedding all the
[
https://issues.apache.org/jira/browse/FELIX-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pleeplop updated FELIX-6043:
Description:
The manifest declares org.osgi.util.function as exported but it is not embedded.
A quick fix
[
https://issues.apache.org/jira/browse/FELIX-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pleeplop updated FELIX-6043:
Attachment: (was: scr-osgi-function-dep.patch)
> ClassNotFoundException
Honestly I should have looked into the code a lot earlier but did not find
the time to do so.
I did not expect that you would propose a major version. So this put me
into quite a hurry to review the code now :-(
I now went through most of it and I agree that the API looks quite good the
way it
GitHub user pleeplop opened a pull request:
https://github.com/apache/felix/pull/177
ClassNotFoundException caused by org.osgi.util.function.Function
The manifest declares org.osgi.util.function as exported but it is not
embedded.
A quick fix is to declare the dependency with
I think testing can be done easily with the current SNAPSHOT (or the
artifacts from the staging repository if it needed to be a non-SNAPSHOT
dependency). Also I have done pretty intensive testing during the last
month (with both Felix HCs and "legacy checks" that are currently
implemented
I just looked through hc core .. I first only looked into general checks
(confused the names in my first mail).
The usage of commons lang there is much broader. So I agree it can not be
removed easily.
So let`s keep it for now. We can still make this lighter later.
Christian
Am Do., 31. Jan.
How about releasing 0.1.0 now and release a 2.0.0 in two weeks?
It would give people time to test the new project and still allow us to do
incompatible changes.
A release of 2.0.0 right now will fixate the API. If we then do a
(incompatible) change we have to create a 3.0.0 version which will
Hi Christian,
the dependencies of bundle HC core [1] are
* org.apache.felix.healthcheck.api
* slf4j-api
* javax.servlet-api
* commons-lang
I thought the same as you three weeks ago and had a try removing
commons-lang, but then for the AEM use case it does not make sense at
all since the
I just found that commons-cli and felix utils are inlined .. so I think
they are less severe.
Christian
Am Do., 31. Jan. 2019 um 17:14 Uhr schrieb Christian Schneider <
ch...@die-schneider.net>:
> Health checks core has a few dependencies that I think we should remove
> before the release:
>
>
I think it is unnecessary overhead for the user to add two dependencies
when he wants to create a check. The annotations do not have to be
exported. So they would be neutral from the bundle view of the api.
Christian
Am Do., 31. Jan. 2019 um 17:07 Uhr schrieb Georg Henzler :
> Hi Christian,
>
>
Hi Christian,
I think the API [1] is proven and in use since 2013 (I would guess >
2000 checks to exist out in the wild in code bases of various projects).
The Felix API was carefully adjusted with your feedback (e.g. the
removal of state DEBUG, FELIX-6016) to make the migration path really
Health checks core has a few dependencies that I think we should remove
before the release:
- commons-lang
Is used in quite a few places but just for very simple things. I think we
can work without it.
- commons-cli
- org.apache.felix.utils
These are used in the HttpRequestsCheck. It would be
+1 from myself as well
@Karl: Thanks for giving me the JIRA permissions, I added all versions
and assigned them to the tickets.
-Georg
On 2019-01-31 13:58, Karl Pauls wrote:
+1
Sorry it took me so long to get to it. I increased your permissions
for JIRA - can you see if you can do the
Hi Christian,
So the health check annotations are only needed at build time by the
bnd-maven-plugin, whereas the API bundle is required at runtime. It
would of course work in one bundle (and people using it would only have
to add one dependency in their pom instead of two), but on the other
[
https://issues.apache.org/jira/browse/FELIX-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated FELIX-6004:
-
Fix Version/s: healthcheck.annotations 2.0.0
> Create a health check annotation based on OSGi R7
[
https://issues.apache.org/jira/browse/FELIX-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated FELIX-6016:
-
Fix Version/s: healthcheck.api 2.0.0
> Clean up util package in Health Check API
>
[
https://issues.apache.org/jira/browse/FELIX-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated FELIX-6018:
-
Fix Version/s: healthcheck.core 2.0.0
> Servlet Filter to answer arbitrary http requests with
[
https://issues.apache.org/jira/browse/FELIX-5952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated FELIX-5952:
-
Fix Version/s: healthcheck.webconsole 2.0.0
> Felix Health Checks
> ---
>
>
[
https://issues.apache.org/jira/browse/FELIX-5952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated FELIX-5952:
-
Fix Version/s: healthcheck.core 2.0.0
healthcheck.api 2.0.0
> Felix Health
[
https://issues.apache.org/jira/browse/FELIX-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated FELIX-6011:
-
Fix Version/s: healthcheck.core 2.0.0
> Introduce tag "default" to be used if no tags are passed
[
https://issues.apache.org/jira/browse/FELIX-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated FELIX-6005:
-
Fix Version/s: healthcheck.api 2.0.0
> Introduce result status TEMPORARILY_UNAVAILABLE for
[
https://issues.apache.org/jira/browse/FELIX-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated FELIX-6010:
-
Fix Version/s: healthcheck.core 2.0.0
> Allow multiple instances of HC servlets with configured
[
https://issues.apache.org/jira/browse/FELIX-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated FELIX-6017:
-
Fix Version/s: healthcheck.core 2.0.0
> Ongoing deployment servlet filter that controls a
[
https://issues.apache.org/jira/browse/FELIX-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated FELIX-6012:
-
Fix Version/s: healthcheck.generalchecks 2.0.0
> Introduce module "generalchecks" with basic
[
https://issues.apache.org/jira/browse/FELIX-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated FELIX-6024:
-
Fix Version/s: healthcheck.generalchecks 2.0.0
> Create HttpRequestsCheck
>
[
https://issues.apache.org/jira/browse/FELIX-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated FELIX-6025:
-
Fix Version/s: healthcheck.generalchecks 2.0.0
> Create ScriptedHealthCheck
>
I think the annotations of felix health check should be part of the api.
So I propose to add them to the api project and remove the annotations
bundle.
WDYT?
Christian
--
--
Christian Schneider
http://www.liquid-reality.de
Computer Scientist
http://www.adobe.com
I think we should not yet release a stable version. Instead I propose to
release a 0.1.0.
WDYT?
Christian
Am Mo., 28. Jan. 2019 um 09:44 Uhr schrieb Georg Henzler :
> Hi all,
>
> We solved 11 issues in this release:
>
>
Pleeplop created FELIX-6043:
---
Summary: ClassNotFoundException org.osgi.util.function.Function
Key: FELIX-6043
URL: https://issues.apache.org/jira/browse/FELIX-6043
Project: Felix
Issue Type: Bug
[
https://issues.apache.org/jira/browse/FELIX-5912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls closed FELIX-5912.
-
> Handle empty package definitions in system package definitions more gracefully
>
[
https://issues.apache.org/jira/browse/FELIX-5942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls closed FELIX-5942.
-
> Felix Framework freezes when resolving classes in parallel with Java 10
>
[
https://issues.apache.org/jira/browse/FELIX-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls closed FELIX-5914.
-
> Workaround SecurityManager.getClassContext returning null on Android
>
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls closed FELIX-6035.
-
> Allow urlhandlers to create urls for jrt protocol without an add-opens
>
[
https://issues.apache.org/jira/browse/FELIX-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls closed FELIX-5978.
-
> Felix framework unable to retrieve custom URL handlers when security is on
>
[
https://issues.apache.org/jira/browse/FELIX-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert reassigned FELIX-6042:
---
Assignee: David Bosschaert
> Lists are not recognized as typed properties
>
[
https://issues.apache.org/jira/browse/FELIX-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16757206#comment-16757206
]
ASF GitHub Bot commented on FELIX-6042:
---
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/felix/pull/176
---
[
https://issues.apache.org/jira/browse/FELIX-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert resolved FELIX-6042.
-
Resolution: Fixed
Fix Version/s: utils-1.11.4
Thanks for the patch [~cfiehe]!
+1
Sorry it took me so long to get to it. I increased your permissions
for JIRA - can you see if you can do the releases yourself now?
regards,
Karl
On Mon, Jan 28, 2019 at 9:44 AM Georg Henzler wrote:
>
> Hi all,
>
> We solved 11 issues in this release:
>
Time to call the vote on the Felix Framework 6.0.2 and related
subproject releases.
* +1 votes from David Bosschaert, Carsten Ziegeler, Jean-Baptiste
Onofre, Timothy Ward, Raymond Auge, Pierre De Rop, and Karl Pauls.
* No other votes.
The vote is successful. I will make the release artifacts
+1
regards,
Karl
On Tue, Jan 29, 2019 at 4:02 PM Pierre De Rop wrote:
>
> +1
>
> Verified checksum, tested with a large project, all is working fine;
>
> thanks !
> Pierre
>
> On Tue, Jan 29, 2019 at 3:40 PM Raymond Auge
> wrote:
>
> > +1
> >
> > - Ray
> >
> > On Tue, Jan 29, 2019 at 9:03 AM
50 matches
Mail list logo
