I hope that's not the case, it would imply that the tag was generated
from trunk and not from the 5-2-maint branch.

On Thu, Mar 31, 2011 at 4:03 PM, David Rees <[email protected]> wrote:
> Thanks - just found that - was confused by the 5.2.5 tag deletion in
> the mail archives.
>
> The question is:  The tag itself appears to have the fix for TAP5-1378
> but the release doesn't?  (at least the issue described by TAP5-1378
> still doesn't work for me)
>
> -Dave
>
> On Thu, Mar 31, 2011 at 3:43 PM, Kalle Korhonen
> <[email protected]> wrote:
>> The tag is at 
>> http://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/5.2.5/
>>
>> Kalle
>>
>> On Thu, Mar 31, 2011 at 3:38 PM, David Rees <[email protected]> wrote:
>>> On Wed, Mar 30, 2011 at 10:22 AM, Igor Drobiazko
>>> <[email protected]> wrote:
>>>> Also this one is only fixed for 5.3.0:
>>>>
>>>> https://issues.apache.org/jira/browse/TAP5-1378
>>>
>>> I can confirm that TAP5-1378 is not fixed in 5.2.5.  It's a show-stopper.
>>>
>>> Is the only way to get this fix to use 5.2-SNAPSHOT builds?
>>>
>>> I also don't see that the source for 5.2.5 was tagged anywhere.
>>>
>>> I would have expected to see that here:
>>> http://svn.apache.org/viewvc/tapestry/tapestry5/tags/releases/
>>>
>>> I'm a bit confused as the ticket indicates that the changes were
>>> committed to the 5.2-maint branch?  If so - from what tree was the
>>> 5.2.5 release built from?  It's impossible to tell since the release
>>> wasn't tagged.
>>>
>>> -Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>



-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to