Sounds like we have to (and can, as it is no regression) push
FELIX-5548 to a later release.
As I'm done with the issue I had (except maybe FELIX-5548 which I
still have to figure out when it happens) I'll cut a release of the
resolver and the framework either tonight or tomorrow.
regards,
Karl
Ok, can you or somebody else have a look at FELIX-5548 and see if that
is a blocker for a resolver release or no?
regards,
karl
On Tue, Feb 14, 2017 at 5:59 PM, Thomas Watson wrote:
> Yes, the resolver is ready to release.
>
> Tom
>
> On Tue, Feb 14, 2017 at 9:37 AM, Karl
Yes, the resolver is ready to release.
Tom
On Tue, Feb 14, 2017 at 9:37 AM, Karl Pauls wrote:
> Well, I guess I don't even have to make the method public - I'm just
> going to copy it over to the framework if need be until we have a
> better way.
>
> With that out of the
I just did this as part of FELIX-5547. With that and FELIX-5544 out of
the way I'm now going to try to get FELIX-5329 done.
When I have that finished and assuming nothing else pops-up I'm going
to cut a resolver and a framework release (hopefully tomorrow).
regards,
Karl
On Tue, Feb 14, 2017
Well, I guess I don't even have to make the method public - I'm just
going to copy it over to the framework if need be until we have a
better way.
With that out of the way, do you think the resolver is good to go for a release?
regards,
Karl
On Tue, Feb 14, 2017 at 4:24 PM, Karl Pauls
> That is currently a private static method. If the Felix framework does not
> already have the substitution wire information available then we can
> consider making this static method public so you can call it from your
> FelixResolveContext implementation. But I think if you don't already have
This is related to the fix for FELIX-5514.
The FelixResolveContext is an internal type (not something I consider real
API at this point). But its intention is to be used by the framework
(Felix and Equinox in particular) to allow the framework to do things
necessary to implement the OSGi
Hi All,
I also would like to do a test with the latest framework and resolver from
the trunk, but it looks like there is a compilation issue with the
framework (trunk):
I have rebuilt the resolver, then the framework, and I'm having this error:
[ERROR]
Great !
Let me know if you need any help...
Cheers,
Guillaume
2017-02-10 12:53 GMT+01:00 Karl Pauls :
> I can do the release next week if you don't mind, as I was planning to
> do a framework release anyhow (almost done with FELIX-5528 - just need
> a bit more testing).
>
>
+1
Also notice that I fixed resolver issue
https://issues.apache.org/jira/browse/FELIX-5514 which should get released
also
Tom.
On Feb 10, 2017 8:19 AM, "David Bosschaert"
wrote:
> That would be great, thanks Guillaume!
>
> David
>
> On 9 February 2017 at 23:43,
That would be great, thanks Guillaume!
David
On 9 February 2017 at 23:43, Guillaume Nodet wrote:
> I'd like to get FELIX-5450 and FELIX-5514 out of the door, so unless
> someone volunteer to do the resolver 1.10.2 release, i'll give it a try
> next week.
>
> Cheers,
>
I can do the release next week if you don't mind, as I was planning to
do a framework release anyhow (almost done with FELIX-5528 - just need
a bit more testing).
regards,
Karl
On Fri, Feb 10, 2017 at 8:43 AM, Guillaume Nodet wrote:
> I'd like to get FELIX-5450 and
+1 for me.
Regards
JB
On Feb 10, 2017, 03:44, at 03:44, Guillaume Nodet wrote:
>I'd like to get FELIX-5450 and FELIX-5514 out of the door, so unless
>someone volunteer to do the resolver 1.10.2 release, i'll give it a
>try
>next week.
>
>Cheers,
>Guillaume
I'd like to get FELIX-5450 and FELIX-5514 out of the door, so unless
someone volunteer to do the resolver 1.10.2 release, i'll give it a try
next week.
Cheers,
Guillaume
14 matches
Mail list logo