You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Douglas Ferguson <do...@douglasferguson.us> on 2009/04/28 07:48:18 UTC
https://issues.apache.org/jira/browse/WICKET-847
So, is this fixed in 1.3.6?
https://issues.apache.org/jira/browse/WICKET-847
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: https://issues.apache.org/jira/browse/WICKET-847
Posted by Johan Compagner <jc...@gmail.com>.
no that one isnt in 1.3.5
The commit is done by igor together with:
WICKET-1916, WICKET-1998
On Tue, Apr 28, 2009 at 09:43, Steve Swinsburg
<s....@lancaster.ac.uk>wrote:
> Comparing the commits attached to the Jira to what is in the 1.3.5 tag in
> svn shows it's not.
>
> I'm a little confused by that, does the committers not fix in trunk, merge
> back to the appropriate branches (1.3.x) then cut tags from the branches
> (1.3.5, 1.3.6)?
>
> Steve
>
>
> On 28/04/2009, at 8:36 AM, Martijn Dashorst wrote:
>
> The commit was before 1.3.5 was cut, so IMO it should be already in 1.3.5.
>>
>> Martijn
>>
>> On Tue, Apr 28, 2009 at 9:31 AM, Jeremy Thomerson
>> <je...@wickettraining.com> wrote:
>>
>>> There's a comment that says that it's actually NOT in 1.3.5 - implying
>>> that the fix version is incorrect. But Igor's comment seems to
>>> indicate that it WAS fixed.
>>>
>>> I don't know which is true, but whoever really wants to know should
>>> just try it and see - and then comment on the jira to make it clear.
>>>
>>> --
>>> Jeremy Thomerson
>>> http://www.wickettraining.com
>>>
>>>
>>>
>>>
>>> On Tue, Apr 28, 2009 at 2:26 AM, Steve Swinsburg
>>> <s....@lancaster.ac.uk> wrote:
>>>
>>>> The fix version for that issue says 1.3.5 so unless people use Jira
>>>> incorrectly, it's in 1.3.5. Likewise for the previous issue that people
>>>> want
>>>> to hold up the 1.3.6 release for, it has a fix version of 1.3.6 so
>>>> should be
>>>> in 1.3.6 already.
>>>>
>>>>
>>>> --Steve
>>>>
>>>> On 28/04/2009, at 6:48 AM, Douglas Ferguson wrote:
>>>>
>>>> So, is this fixed in 1.3.6?
>>>>>
>>>>> https://issues.apache.org/jira/browse/WICKET-847
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.3.5 is released
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
Re: https://issues.apache.org/jira/browse/WICKET-847
Posted by Steve Swinsburg <s....@lancaster.ac.uk>.
Comparing the commits attached to the Jira to what is in the 1.3.5 tag
in svn shows it's not.
I'm a little confused by that, does the committers not fix in trunk,
merge back to the appropriate branches (1.3.x) then cut tags from the
branches (1.3.5, 1.3.6)?
Steve
On 28/04/2009, at 8:36 AM, Martijn Dashorst wrote:
> The commit was before 1.3.5 was cut, so IMO it should be already in
> 1.3.5.
>
> Martijn
>
> On Tue, Apr 28, 2009 at 9:31 AM, Jeremy Thomerson
> <je...@wickettraining.com> wrote:
>> There's a comment that says that it's actually NOT in 1.3.5 -
>> implying
>> that the fix version is incorrect. But Igor's comment seems to
>> indicate that it WAS fixed.
>>
>> I don't know which is true, but whoever really wants to know should
>> just try it and see - and then comment on the jira to make it clear.
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>>
>>
>>
>> On Tue, Apr 28, 2009 at 2:26 AM, Steve Swinsburg
>> <s....@lancaster.ac.uk> wrote:
>>> The fix version for that issue says 1.3.5 so unless people use Jira
>>> incorrectly, it's in 1.3.5. Likewise for the previous issue that
>>> people want
>>> to hold up the 1.3.6 release for, it has a fix version of 1.3.6 so
>>> should be
>>> in 1.3.6 already.
>>>
>>>
>>> --Steve
>>>
>>> On 28/04/2009, at 6:48 AM, Douglas Ferguson wrote:
>>>
>>>> So, is this fixed in 1.3.6?
>>>>
>>>> https://issues.apache.org/jira/browse/WICKET-847
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.5 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
Re: https://issues.apache.org/jira/browse/WICKET-847
Posted by Martijn Dashorst <ma...@gmail.com>.
The commit was before 1.3.5 was cut, so IMO it should be already in 1.3.5.
Martijn
On Tue, Apr 28, 2009 at 9:31 AM, Jeremy Thomerson
<je...@wickettraining.com> wrote:
> There's a comment that says that it's actually NOT in 1.3.5 - implying
> that the fix version is incorrect. But Igor's comment seems to
> indicate that it WAS fixed.
>
> I don't know which is true, but whoever really wants to know should
> just try it and see - and then comment on the jira to make it clear.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Tue, Apr 28, 2009 at 2:26 AM, Steve Swinsburg
> <s....@lancaster.ac.uk> wrote:
>> The fix version for that issue says 1.3.5 so unless people use Jira
>> incorrectly, it's in 1.3.5. Likewise for the previous issue that people want
>> to hold up the 1.3.6 release for, it has a fix version of 1.3.6 so should be
>> in 1.3.6 already.
>>
>>
>> --Steve
>>
>> On 28/04/2009, at 6:48 AM, Douglas Ferguson wrote:
>>
>>> So, is this fixed in 1.3.6?
>>>
>>> https://issues.apache.org/jira/browse/WICKET-847
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: https://issues.apache.org/jira/browse/WICKET-847
Posted by Jeremy Thomerson <je...@wickettraining.com>.
There's a comment that says that it's actually NOT in 1.3.5 - implying
that the fix version is incorrect. But Igor's comment seems to
indicate that it WAS fixed.
I don't know which is true, but whoever really wants to know should
just try it and see - and then comment on the jira to make it clear.
--
Jeremy Thomerson
http://www.wickettraining.com
On Tue, Apr 28, 2009 at 2:26 AM, Steve Swinsburg
<s....@lancaster.ac.uk> wrote:
> The fix version for that issue says 1.3.5 so unless people use Jira
> incorrectly, it's in 1.3.5. Likewise for the previous issue that people want
> to hold up the 1.3.6 release for, it has a fix version of 1.3.6 so should be
> in 1.3.6 already.
>
>
> --Steve
>
> On 28/04/2009, at 6:48 AM, Douglas Ferguson wrote:
>
>> So, is this fixed in 1.3.6?
>>
>> https://issues.apache.org/jira/browse/WICKET-847
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: https://issues.apache.org/jira/browse/WICKET-847
Posted by Steve Swinsburg <s....@lancaster.ac.uk>.
The fix version for that issue says 1.3.5 so unless people use Jira
incorrectly, it's in 1.3.5. Likewise for the previous issue that
people want to hold up the 1.3.6 release for, it has a fix version of
1.3.6 so should be in 1.3.6 already.
--Steve
On 28/04/2009, at 6:48 AM, Douglas Ferguson wrote:
> So, is this fixed in 1.3.6?
>
> https://issues.apache.org/jira/browse/WICKET-847
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>