Vadim Gritsenko wrote:
Georg Sauer-Limbach wrote:
There is the problem that changes to the database that are made
via the local interface (command line) are not reflected in a
running server instance, i.e. in Tomcat. Maybe this makes a
candidate for nice-to-fix?
No, this one does not. But brin
Natalia Shilenkova wrote:
Any idea when the release thing may happen? I have at least a couple
of patches in progress, would like to get them included before
release.
I think release should happen sometime after we decide on some release plan ;-)
I'll try to draft one soon...
Vadim
Natalia
Any idea when the release thing may happen? I have at least a couple
of patches in progress, would like to get them included before
release.
Natalia
On 3/7/07, Vadim Gritsenko <[EMAIL PROTECTED]> wrote:
But release 1.1 must happen with Java 1.3, there is no any other way. After 1.1
is out, we c
Sounds good.
Todd
On 3/7/07, Vadim Gritsenko <[EMAIL PROTECTED]> wrote:
Todd Byrne wrote:
> Shouldn't we go for broke and move to 1.5 ? 1.5 has a bunch of language
> features that very nice, and has been out sense 2004-09-29
That is tempting... :)
But release 1.1 must happen with Java 1.3, t
Todd Byrne wrote:
Shouldn't we go for broke and move to 1.5 ? 1.5 has a bunch of language
features that very nice, and has been out sense 2004-09-29
That is tempting... :)
But release 1.1 must happen with Java 1.3, there is no any other way. After 1.1
is out, we can discuss minimum Java versi
Shouldn't we go for broke and move to 1.5 ? 1.5 has a bunch of language
features that very nice, and has been out sense 2004-09-29
Todd
On 3/6/07, Vadim Gritsenko <[EMAIL PROTECTED]> wrote:
Georg Sauer-Limbach wrote:
>
>>> Speaking of next version... Are there any plans for new release?...
>>
Georg Sauer-Limbach wrote:
Speaking of next version... Are there any plans for new release?...
There are also other loose ends - like document caching, meta data
handling, etc - which is good to have fixed before release.
There is the problem that changes to the database that are made
via th
Speaking of next version... Are there any plans for new release?...
There are also other loose ends - like document caching, meta data
handling, etc - which is good to have fixed before release.
There is the problem that changes to the database that are made
via the local interface (command l
Natalia Shilenkova wrote:
Speaking of next version... Are there any plans for new release?
There were no special plans, but we should make some.
It
certainly has been a while since last release. Is there anything
outstanding?
I see that there is an indexing related patch from you in bugzill
On 2/24/07, Vadim Gritsenko <[EMAIL PROTECTED]> wrote:
All done now. At least no legal problem will prevent us releasing next version.
Vadim
Speaking of next version... Are there any plans for new release? It
certainly has been a while since last release. Is there anything
outstanding?
Natal
All done now. At least no legal problem will prevent us releasing next version.
Vadim
[EMAIL PROTECTED] wrote:
I don't have anything outstanding.
Todd
On Thu, 22 Feb 2007, Vadim Gritsenko wrote:
Hi all,
Xindice is still using older version of license headers, the correct version can
be f
I don't have anything outstanding.
Todd
On Thu, 22 Feb 2007, Vadim Gritsenko wrote:
> Hi all,
>
> Xindice is still using older version of license headers, the correct version
> can
> be found here [1]. I'll try to update headers sometime this week (end), which
> means I'll be touching lots
Hi all,
Xindice is still using older version of license headers, the correct version can
be found here [1]. I'll try to update headers sometime this week (end), which
means I'll be touching lots of files.
If any of you folks (Todd? :) have local uncommitted changes, and such updates
will dis
13 matches
Mail list logo
