Re: [Neo] RFC: Potentially breaking changes in the upcoming 1.0 release

2010-01-08 Thread Johan Svensson
Hi, After some discussions following the input here we decided to go with no explicit .api package but an explicit .impl package (for implementation that is not supposed to be public). The 1.0 release will then look like this: o neo component renamed to kernel - old core API

Re: [Neo] RFC: Potentially breaking changes in the upcoming 1.0 release

2010-01-08 Thread Laurent Laborde
On Fri, Jan 8, 2010 at 11:52 AM, Johan Svensson jo...@neotechnology.com wrote: Hi, After some discussions following the input here we decided to go with no explicit .api package but an explicit .impl package (for implementation that is not supposed to be public). The 1.0 release will then

Re: [Neo] RFC: Potentially breaking changes in the upcoming 1.0 release

2010-01-08 Thread Tobias Ivarsson
On Fri, Jan 8, 2010 at 11:56 AM, Laurent Laborde kerdez...@gmail.comwrote: On Fri, Jan 8, 2010 at 11:52 AM, Johan Svensson jo...@neotechnology.com wrote: Hi, After some discussions following the input here we decided to go with no explicit .api package but an explicit .impl package (for

[Neo] RFC: Potentially breaking changes in the upcoming 1.0 release

2010-01-06 Thread Tobias Ivarsson
Hi all! For our upcoming final 1.0 release we are thinking about restructuring the components and package names to make them at least closer to something we would want to live with for a considerable future. The main affected component at this point is the Neo4j kernel, even if other components

Re: [Neo] RFC: Potentially breaking changes in the upcoming 1.0 release

2010-01-06 Thread Craig Taverner
Ivarsson Sent: Wednesday, January 06, 2010 3:28 PM To: Neo user discussions Subject: [Neo] RFC: Potentially breaking changes in the upcoming 1.0 release Hi all! For our upcoming final 1.0 release we are thinking about restructuring the components and package names to make them at least closer

Re: [Neo] RFC: Potentially breaking changes in the upcoming 1.0 release

2010-01-06 Thread Peter Neubauer
Hi there, from an OSGi perspective, everything between bundles is handled on package level. From that perspective, separation of api and impl (and others) is better separated via org.neo4j.api and org.neo4j.impl etc. Otherwise, e.g. the org.neo4j.* would be exported from the bundle containing the

Re: [Neo] RFC: Potentially breaking changes in the upcoming 1.0 release

2010-01-06 Thread Tobias Ivarsson
On Wed, Jan 6, 2010 at 10:36 PM, Mattias Persson matt...@neotechnology.comwrote: 2010/1/6 Rick Bullotta rick.bullo...@burningskysoftware.com: It's a relatively minor thing to fix in our code. I would suggest reconsidering the retro façade, however - it really doesn't buy you much and

Re: [Neo] RFC: Potentially breaking changes in the upcoming 1.0 release

2010-01-06 Thread Peter Neubauer
Thanks Andreas for the input, I guess if Stuart McCulloch is doing it in PaxConstruct, we can stop arguing :) So, no problems from the OSGi side for root-package-APIs :) Cheers, /peter neubauer COO and Sales, Neo Technology GTalk: neubauer.peter Skype peter.neubauer Phone +46