No problem Adrian, it was reported hours ago !<div>I don't expect bugs to be fixed within hours ;-)</div><div><br></div><div>And, as we wrote before, this is not really a bug... we are only solidifying things here and I was not expecting to receive so much exceptions when connecting to S3 (yeah, you heard me Amazon).</div>
<div><br></div><div>Keep up the good work...</div><div><br></div><div>phil</div><div><br></div><div>P.S.: my own Hudson internally release versions of my project to an external repository... when I restart the server, it picks up the latest release (And I really mean release - not deploy, so I can't use snapshots.. I will have to wait for the next ispn version anyway.. no hurry)<br>
<br><div class="gmail_quote">On Wed, May 26, 2010 at 11:41 PM, Adrian Cole <span dir="ltr"><<a href="mailto:ferncam1@gmail.com">ferncam1@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Phil,<br>
<br>
wrt jclouds<br>
<br>
Sorry the bug you've mentioned is not already fixed in beta-6. When<br>
it is fixed in snapshot, you "could" override the maven dependency in<br>
infinispan with the new version. Beta-7 is likely a few weeks away.<br>
I can look into this bug this weekend.<br>
<font color="#888888"><br>
-Adrian<br>
</font><div><div></div><div class="h5"><br>
On Wed, May 26, 2010 at 3:17 PM, Philippe Van Dyck <<a href="mailto:pvdyck@gmail.com">pvdyck@gmail.com</a>> wrote:<br>
> A-mazing...<br>
> FYI, with 4.1.0.BETA1 and jclouds 1.0-beta-5, when S3 resets the connection,<br>
> I have the same behavior we talked about about the lock not being released.<br>
><br>
> The issue is reported here<br>
> : <a href="http://code.google.com/p/jclouds/issues/detail?id=268" target="_blank">http://code.google.com/p/jclouds/issues/detail?id=268</a><br>
> Can't wait to test your fix Manik !<br>
> Cheers,<br>
> Phil<br>
> P.S.: BTW, there is a snapshot (???) in the release maven repository ...<br>
> shouldn't it be in the ... snapshot repo ?<br>
> On Wed, May 26, 2010 at 11:08 PM, Manik Surtani <<a href="mailto:manik@jboss.org">manik@jboss.org</a>> wrote:<br>
>><br>
>> On 26 May 2010, at 17:58, Philippe Van Dyck wrote:<br>
>><br>
>> Is it still possible to upgrade to jclouds beta 6 before the release ?<br>
>><br>
>> Yup jclouds beta6 is in trunk already.<br>
>><br>
>> cheers,<br>
>> philippe<br>
>> On Wed, May 26, 2010 at 4:04 PM, Manik Surtani <<a href="mailto:manik@jboss.org">manik@jboss.org</a>> wrote:<br>
>>><br>
>>> On 26 May 2010, at 14:49, Mircea Markus wrote:<br>
>>><br>
>>> ><br>
>>> > On 26 May 2010, at 15:29, Manik Surtani wrote:<br>
>>> ><br>
>>> >> Guys,<br>
>>> >><br>
>>> >> So we've decided to release Radegast BETA2 tomorrow rather than CR1,<br>
>>> >> as it gives folks more time to feed back stuff. Hopefully there won't be<br>
>>> >> any work done on Radegast between BETA2 and CR1 except fixing issues people<br>
>>> >> may report.<br>
>>> >><br>
>>> >> And for this purpose, I propose branching trunk to a 4.1 branch, after<br>
>>> >> we tag BETA2:<br>
>>> >><br>
>>> >> <a href="http://anonsvn.jboss.org/repos/infinispan/branches/4.1.x" target="_blank">http://anonsvn.jboss.org/repos/infinispan/branches/4.1.x</a><br>
>>> >><br>
>>> >> This way trunk can contain the 5.0 codebase, and people can start<br>
>>> >> working on 5.0 features.<br>
>>> >><br>
>>> > so that we release from 4.1.x and after releasing merge into trunk? or<br>
>>> > merge into trunk before releasing?<br>
>>><br>
>>> I presume you are referring to post-BETA2 releases - in that case, merge<br>
>>> to trunk first (since commits/changes for 4.1.x releases will be on that<br>
>>> branch)<br>
>>><br>
>>> >> Thoughts, opinions?<br>
>>> >><br>
>>> >> Cheers,<br>
>>> >> Manik<br>
>>> >> --<br>
>>> >> Manik Surtani<br>
>>> >> <a href="mailto:manik@jboss.org">manik@jboss.org</a><br>
>>> >> Lead, Infinispan<br>
>>> >> Lead, JBoss Cache<br>
>>> >> <a href="http://www.infinispan.org" target="_blank">http://www.infinispan.org</a><br>
>>> >> <a href="http://www.jbosscache.org" target="_blank">http://www.jbosscache.org</a><br>
>>> >><br>
>>> >><br>
>>> >><br>
>>> >><br>
>>> >><br>
>>> >> _______________________________________________<br>
>>> >> infinispan-dev mailing list<br>
>>> >> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> >> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>> ><br>
>>> ><br>
>>> > _______________________________________________<br>
>>> > infinispan-dev mailing list<br>
>>> > <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> > <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>>><br>
>>> --<br>
>>> Manik Surtani<br>
>>> <a href="mailto:manik@jboss.org">manik@jboss.org</a><br>
>>> Lead, Infinispan<br>
>>> Lead, JBoss Cache<br>
>>> <a href="http://www.infinispan.org" target="_blank">http://www.infinispan.org</a><br>
>>> <a href="http://www.jbosscache.org" target="_blank">http://www.jbosscache.org</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> infinispan-dev mailing list<br>
>>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>><br>
>> _______________________________________________<br>
>> infinispan-dev mailing list<br>
>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>><br>
>> --<br>
>> Manik Surtani<br>
>> <a href="mailto:manik@jboss.org">manik@jboss.org</a><br>
>> Lead, Infinispan<br>
>> Lead, JBoss Cache<br>
>> <a href="http://www.infinispan.org" target="_blank">http://www.infinispan.org</a><br>
>> <a href="http://www.jbosscache.org" target="_blank">http://www.jbosscache.org</a><br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> infinispan-dev mailing list<br>
>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
><br>
<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br></div>