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 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
This is a reboot of the thread previously started on both the
infinispan-dev and the hibernate-dev mailing list as Handling of
mutual dependency with Infinispan [1].
We discussed further during the Hibernate fortnightly meeting [2], and
came to the conclusion that we need Infinispan to change how
