Re: Design guidelines and SemVer

2015-02-18 Thread Benedikt Ritter
2015-02-18 13:22 GMT+01:00 Stian Soiland-Reyes : > Also, as changing Java package names is a drastic step, you would > think three times before introducing breaking changes at all. (or if > you do - do so with a big bang and "fix everything" :) ). > > So I think this specialization looks all sensi

Re: Design guidelines and SemVer

2015-02-18 Thread Stian Soiland-Reyes
Also, as changing Java package names is a drastic step, you would think three times before introducing breaking changes at all. (or if you do - do so with a big bang and "fix everything" :) ). So I think this specialization looks all sensible, specially for Apache Commons which are utility librari

Re: Design guidelines and SemVer

2015-02-17 Thread Benedikt Ritter
2015-02-18 5:09 GMT+01:00 Peter Ansell : > On 18 February 2015 at 12:28, sebb wrote: > > On 17 February 2015 at 22:56, Peter Ansell > wrote: > >> On 17 February 2015 at 21:48, sebb wrote: > >>> On 17 February 2015 at 06:13, Benedikt Ritter > wrote: > >> > >> > >> > and the maven coordina

Re: Design guidelines and SemVer

2015-02-17 Thread Peter Ansell
On 18 February 2015 at 12:28, sebb wrote: > On 17 February 2015 at 22:56, Peter Ansell wrote: >> On 17 February 2015 at 21:48, sebb wrote: >>> On 17 February 2015 at 06:13, Benedikt Ritter wrote: >> >> >> and the maven coordinates when we break binary compatibility (= bump up the maj

Re: Design guidelines and SemVer

2015-02-17 Thread sebb
On 17 February 2015 at 22:56, Peter Ansell wrote: > On 17 February 2015 at 21:48, sebb wrote: >> On 17 February 2015 at 06:13, Benedikt Ritter wrote: > > > >>> and the maven coordinates when we break binary compatibility (= bump up the >>> major version number). We do this to avoid jar hell. Th

Re: Design guidelines and SemVer

2015-02-17 Thread Peter Ansell
On 17 February 2015 at 21:48, sebb wrote: > On 17 February 2015 at 06:13, Benedikt Ritter wrote: >> and the maven coordinates when we break binary compatibility (= bump up the >> major version number). We do this to avoid jar hell. This way two versions >> of the same commons library can be in

Re: Design guidelines and SemVer

2015-02-17 Thread sebb
On 17 February 2015 at 06:13, Benedikt Ritter wrote: > Hello Peter > > 2015-02-15 22:49 GMT+01:00 Peter Ansell : > >> On 15 February 2015 at 21:29, Benedikt Ritter wrote: >> >> >> > We like to underline, that we have no experience with the RDF >> > specification. From a technical point of view w

Re: Design guidelines and SemVer

2015-02-16 Thread Benedikt Ritter
Hello Peter 2015-02-15 22:49 GMT+01:00 Peter Ansell : > On 15 February 2015 at 21:29, Benedikt Ritter wrote: > > > > We like to underline, that we have no experience with the RDF > > specification. From a technical point of view we can help to develop the > > proposed API (according to our desi

Design guidelines and SemVer

2015-02-15 Thread Peter Ansell
On 15 February 2015 at 21:29, Benedikt Ritter wrote: > We like to underline, that we have no experience with the RDF > specification. From a technical point of view we can help to develop the > proposed API (according to our design guide lines [3]). Hi Benedikt, On my personal projects I tend