You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@beehive.apache.org by Adam Jenkins <ma...@adamjenkins.net> on 2005/09/04 07:18:08 UTC
BEEHIVE-843 status?
Hi All,
What's the status of jira issue BEEHIVE-843 ... there seems to be a
patch submitted but no comments after that. Has it made it into beehive
yet (I have some code that would benefit from the issue fix).
Cheers
Adam
Re: BEEHIVE-843 status?
Posted by Rich Feit <ri...@gmail.com>.
FYI, I think that your patch could go in first, then be refactored for
code sharing (if that turns out to be a possibility). So hopefully it
goes in immediately after we branch.
Rich
Carlin Rogers wrote:
>Hi Adam,
>
>I didn't notice a patch for BEEHIVE-843. Are you thinking of 863? If so, the
>implementation of BEEHIVE-863 is really a new feature and would most likely
>get checked into the main trunk by a committer after the branch for the V1
>release. You should also note that the patch for 863 will probably need some
>modifications as far as the JavaScript goes and looking at possible reuse of
>some JavaScript used in datagrid. If it's not 863 you're talking about, I do
>know there are a couple of other small patches for bugs that will also be
>committed after the branch. Most of the changes being committed now are for
>doc, etc.
>
>Kind regards,
>Carlin
>
>
>On 9/3/05, Adam Jenkins <ma...@adamjenkins.net> wrote:
>
>
>>Hi All,
>>
>>What's the status of jira issue BEEHIVE-843 ... there seems to be a
>>patch submitted but no comments after that. Has it made it into beehive
>>yet (I have some code that would benefit from the issue fix).
>>
>>Cheers
>>Adam
>>
>>
>>
>>
>
>
>
Re: BEEHIVE-843 status? !! my bad...839
Posted by Adam Jenkins <ma...@adamjenkins.net>.
Sorry, my bad...I meant BEEHIVE-839...the patch says it applies to 839
and 843, but it's attached to 839
On Mon, 2005-09-05 at 22:46 -0600, Carlin Rogers wrote:
> Hi Adam,
>
> I didn't notice a patch for BEEHIVE-843. Are you thinking of 863? If
> so, the implementation of BEEHIVE-863 is really a new feature and
> would most likely get checked into the main trunk by a committer after
> the branch for the V1 release. You should also note that the patch for
> 863 will probably need some modifications as far as the JavaScript
> goes and looking at possible reuse of some JavaScript used in
> datagrid. If it's not 863 you're talking about, I do know there are a
> couple of other small patches for bugs that will also be committed
> after the branch. Most of the changes being committed now are for doc,
> etc.
>
> Kind regards,
> Carlin
>
>
> On 9/3/05, Adam Jenkins <ma...@adamjenkins.net> wrote:
> Hi All,
>
> What's the status of jira issue BEEHIVE-843 ... there seems to
> be a
> patch submitted but no comments after that. Has it made it
> into beehive
> yet (I have some code that would benefit from the issue fix).
>
> Cheers
> Adam
>
>
Re: BEEHIVE-843 status?
Posted by Carlin Rogers <ca...@gmail.com>.
Hi Adam,
I didn't notice a patch for BEEHIVE-843. Are you thinking of 863? If so, the
implementation of BEEHIVE-863 is really a new feature and would most likely
get checked into the main trunk by a committer after the branch for the V1
release. You should also note that the patch for 863 will probably need some
modifications as far as the JavaScript goes and looking at possible reuse of
some JavaScript used in datagrid. If it's not 863 you're talking about, I do
know there are a couple of other small patches for bugs that will also be
committed after the branch. Most of the changes being committed now are for
doc, etc.
Kind regards,
Carlin
On 9/3/05, Adam Jenkins <ma...@adamjenkins.net> wrote:
>
> Hi All,
>
> What's the status of jira issue BEEHIVE-843 ... there seems to be a
> patch submitted but no comments after that. Has it made it into beehive
> yet (I have some code that would benefit from the issue fix).
>
> Cheers
> Adam
>
>