Thanks!

On Fri, Mar 5, 2010 at 2:37 PM, David Bosschaert
<[email protected]> wrote:
> FELIX-2172
>
> Cheers,
>
> David
>
> On 5 March 2010 12:49, Karl Pauls <[email protected]> wrote:
>> The patch didn't make it. Can you create a jira and attach it there
>> please? We have high hopes that the new resolver in trunk will work
>> with this kind of scenarios...
>>
>> regards,
>>
>> Karl
>>
>> On Fri, Mar 5, 2010 at 1:33 PM, David Bosschaert
>> <[email protected]> wrote:
>>> Yes, it's quite simple to reproduce.
>>>
>>> 1. Check out CXF-DOSGi from http://svn.apache.org/repos/asf/cxf/dosgi/trunk
>>> 2. First simply do a build with 'mvn install' from the root to get
>>> everything ready (you may have to set MAVEN_OPTS=-Xmx512m)
>>> 3. cd into systests2/multi-bundle
>>> 4. Then run: 'mvn install -Dtest=TestDiscoveryRountrip' from there.
>>> You will see that it runs some test (which uses a fairly large number
>>> of bundles). It's currently configured to use Equinox via Pax Exam.
>>> 5. Applying the attached patch will change it to use Felix.
>>> 6. Run: 'mvn install -Dtest=TestDiscoveryRountrip' again, and you'll
>>> see that just after 'Welcome to Felix' it hangs.
>>>
>>> Cheers,
>>>
>>> David
>>>
>>> On 3 March 2010 17:30, Richard S. Hall <[email protected]> wrote:
>>>> On 3/3/10 12:13 PM, David Bosschaert wrote:
>>>>>
>>>>> Nice :) I've had lots of hangs (or extremely long resolves) in the
>>>>> CXF-DOSGi system tests, which run using Pax Exam. Does anyone know how
>>>>> to get Pax Exam to use this latest build? Currently I'm using:
>>>>>   CoreOptions.frameworks(CoreOptions.felix())
>>>>> to simply select felix...
>>>>>
>>>>
>>>> If you can find a simple way to reproduce any long resolves, let me know
>>>> since I'd like to play with them...
>>>>
>>>> -> richard
>>>>
>>>>> Thanks,
>>>>>
>>>>> David
>>>>>
>>>>> On 3 March 2010 16:55, Richard S. Hall<[email protected]>  wrote:
>>>>>
>>>>>>
>>>>>> For those using framework from trunk, I've merged work from my sandbox
>>>>>> into
>>>>>> the trunk...the changes are fairly substantial.
>>>>>>
>>>>>> The changes are not complete and the API will likely be in flux for a
>>>>>> while,
>>>>>> but the framework should be reasonably stable (i.e., still passing the
>>>>>> CT).
>>>>>> The big change for now is the introduction of a new resolver
>>>>>> implementation.
>>>>>>
>>>>>> If you are someone experiencing "hangs" from long resolver cycles, feel
>>>>>> free
>>>>>> to try the snapshot and see if it makes a difference for you. In fact,
>>>>>> any
>>>>>> usage and reporting of issues would be helpful.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> ->  richard
>>>>>>
>>>>>> p.s. Currently, I am unable to publish a snapshot, but I will try to do
>>>>>> that
>>>>>> later (for the time being you can build from trunk).
>>>>>>
>>>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Karl Pauls
>> [email protected]
>>
>



-- 
Karl Pauls
[email protected]

Reply via email to