Sorry, I pasted the wrong issue.  The missing fix is:
https://issues.apache.org/jira/browse/FELIX-2419

<https://issues.apache.org/jira/browse/FELIX-2419>Chris

--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Felix :: http://felix.apache.org
Apache Directory Server :: http://directory.apache.org


On Fri, Jun 18, 2010 at 15:19, Chris Custine <[email protected]>wrote:

> Artifacts look good, but I'm not sure the fix for
> https://issues.apache.org/jira/browse/FELIX-2361 made it in to this build.
>  I still get the error and the stack trace points to the old code location.
>  The tag in svn shows the right version but the source in the staging repo
> has the old code.  Not sure what could be happening.  Anyone else seeing
> this or am I getting a stale copy from an http cache somewhere?
>
> Chris
>
> --
> Chris Custine
> FUSESource :: http://fusesource.com
> My Blog :: http://blog.organicelement.com
> Apache ServiceMix :: http://servicemix.apache.org
> Apache Felix :: http://felix.apache.org
> Apache Directory Server :: http://directory.apache.org
>
>
>
> On Fri, Jun 18, 2010 at 07:17, Guillaume Nodet <[email protected]> wrote:
>
>> I would like to call a new vote on karaf 1.6.2.
>> The only change since the 3thd attempt is the fix for the bug Gert
>> found in the features service.
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachefelix-004/
>>
>> You can use this UNIX script to download the release and verify the
>> signatures:
>> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>>
>> Usage:
>> sh check_staged_release.sh 004 /tmp/felix-staging
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 There's a problem (please provide specific comments)
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>
>

Reply via email to