Hi Ludo,
Could you please send us some details on the REST admin dev tests?
I would like to
- reproduce the issue to be able to fix it
- make it part of our test machinery, so that we avoid such a last
minute surprise in the future
If there is any hudson job responsible for the test, can we get access
to that job definition?
(i.e. if the hudson instance running that job is secured, could you add
japod username
or allow jp149343 user from LDAP see the job configuration there?)
Thanks,
~Jakub
On 06/18/2010 08:57 PM, Paul Sandoz wrote:
>
> On Jun 18, 2010, at 8:03 PM, Ludovic Champenois wrote:
>
>> On 6/18/10 10:53 AM, Jane Young wrote:
>>> Just reverted: svn rev 37904.
>>>
>>
>> Many thanks.
>>
>> On my side I was able to also avoid the cnf exception by avoiding the
>> 2 calls to getMediaTypeMappings:
>>
>> ResourceConfig rc = new DefaultResourceConfig(classes);
>> // rc.getMediaTypeMappings().put("xml",
>> MediaType.APPLICATION_XML_TYPE);
>> // rc.getMediaTypeMappings().put("json",
>> MediaType.APPLICATION_JSON_TYPE);
>>
>> in our lazy initializer.
>> It's better if Jakub csan take a look at that early next week. Seems
>> to be an osgi dependency declaration issue on Jersey side.
>>
>
> It might be because we changed the distribution in GF to use the
> individual jersey modules instead of the jersey-bundle.
>
> So the OSGI dependencies of the REST admin module might need to be
> updated to reflect that.
>
> Paul.