Re: [infinispan-dev] Introducing builder subpackages

2013-06-26 Thread Dan Berindei
-1 as well, as a user you only use ConfigurationBuilder and GlobalConfigurationBuilder directly, and moving them to a subpackage would make them less accessible. If anything, I'd move these two classes to the parent package (org.infinispan.configuration), but like Sanne said there's no point in br

Re: [infinispan-dev] Introducing builder subpackages

2013-06-26 Thread Mircea Markus
On 26 Jun 2013, at 09:54, Sanne Grinovero wrote: > Please don't break the configuration API again :-( > > On 26 June 2013 06:29, Navin Surtani wrote: >> While working through ISPN-2463, and the sub-tasks I was wondering about the >> organisation of the ConfigurationBuilder classes. >> >> Curr

Re: [infinispan-dev] Introducing builder subpackages

2013-06-25 Thread Sanne Grinovero
Please don't break the configuration API again :-( On 26 June 2013 06:29, Navin Surtani wrote: > While working through ISPN-2463, and the sub-tasks I was wondering about the > organisation of the ConfigurationBuilder classes. > > Currently, they are located in org.infinispan.configuration.cache.e

[infinispan-dev] Introducing builder subpackages

2013-06-25 Thread Navin Surtani
While working through ISPN-2463, and the sub-tasks I was wondering about the organisation of the ConfigurationBuilder classes. Currently, they are located in org.infinispan.configuration.cache.etc or org.infinispan.configuration.global.etc. The actual Configuration classes are within the same