Isn't the deployment of XSDs part of the release process ?
Tristan
On 14/05/2014 01:36, Sanne Grinovero wrote:
The testing configuration files seem to point to this URL:
http://www.infinispan.org/schemas/infinispan-config-7.0.xsd
But I'm getting a 404 when attempting to find it.
It would
On Tue, May 13, 2014 at 6:40 PM, Radim Vansa rva...@redhat.com wrote:
On 05/13/2014 03:58 PM, Dan Berindei wrote:
On Mon, May 12, 2014 at 1:54 PM, Radim Vansa rva...@redhat.com wrote:
@Dan: It's absolutely correct to do the further writes in order to make
the cache consistent, I am not
yes, the release process put the schema here:
http://docs.jboss.org/infinispan/schemas/
Pedro
On 05/14/2014 07:50 AM, Tristan Tarrant wrote:
Isn't the deployment of XSDs part of the release process ?
Tristan
On 14/05/2014 01:36, Sanne Grinovero wrote:
The testing configuration files seem
Hi,
I'm proud to announce the Alpha4 release of Infinispan 7.0.0.
More info in
http://blog.infinispan.org/2014/05/infinispan-700alpha4-is-out.html
Regards,
Pedro
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
I don't see a lot of value in doing core-only releases. Releases are
expensive because we have to update the website and documentation, and we
have to announce the release everywhere. Releasing only the core won't
change that.
Also, we don't try to maintain backwards compatibility between
+1 for moving Infinispan lucene directory out
But why move Query components out? And which ones did you have in mind?
On 05/14/2014 12:50 AM, Sanne Grinovero wrote:
This is a reboot of the thread previously started on both the
infinispan-dev and the hibernate-dev mailing list as Handling of
On 14 May 2014 12:20, Dan Berindei dan.berin...@gmail.com wrote:
I don't see a lot of value in doing core-only releases. Releases are
expensive because we have to update the website and documentation, and we
have to announce the release everywhere. Releasing only the core won't
change that.
On 14 May 2014 09:58, Pedro Ruivo pe...@infinispan.org wrote:
yes, the release process put the schema here:
http://docs.jboss.org/infinispan/schemas/
Thanks, I'll use that. But shouldn't we have it at the URL I posted too??
And is it really expected that we don't parse old-style configuration
On 14 May 2014 13:19, Adrian Nistor anis...@redhat.com wrote:
+1 for moving Infinispan lucene directory out
But why move Query components out? And which ones did you have in mind?
Because it depends on the Directory, but also on Hibernate Search, so
it mandates a specific version of Apache
Let's not overload the subject here.
We can first approach the problem like Dan mentions by doing a tag for core in
git and release in maven.
Then every other Infinispan bit is tagged and released as one and depend on
that core tag. That makes for 1 marketing release (website, blog ect).
You
Hi Sanne,
I have added the 7.0 schemas to infinispan.org/schemas.
About the 6.0 parsing, yes I think it was supposed to be not parsed :P I
think I saw some warning about this change but I can't find it (so maybe
I was dreaming). So, agree with you. we need an upgrade guide (however,
the
On 14 May 2014 14:00, Pedro Ruivo pe...@infinispan.org wrote:
Hi Sanne,
I have added the 7.0 schemas to infinispan.org/schemas.
Thanks!
About the 6.0 parsing, yes I think it was supposed to be not parsed :P I
think I saw some warning about this change but I can't find it (so maybe
I was
12 matches
Mail list logo
