I generally prefer one groupId matching the git repository somehow (e.g. org.apache.commons.rdf), but +1 to the below and be aligned with the rest of (modern) Commons. Also we won't have that many modules. On 28 Mar 2015 16:51, "Gary Gregory" <garydgreg...@gmail.com> wrote:
> On Sat, Mar 28, 2015 at 9:40 AM, Benedikt Ritter <brit...@apache.org> > wrote: > > > 2015-03-28 16:37 GMT+01:00 Sergio Fernández <wik...@apache.org>: > > > > > Hi Benedikt, > > > > > > that question came to me while working on COMMONSRDF-2... > > > > > > Personally I see Apache Commons as our current target for graduation. > > > Therefore I'd prefer to use those coordinates already in incubation > > (that's > > > considered a best practices to avoid issues on graduation). But of > course > > > anybody else could have other opinion. > > > > > > In that case, how does Commons manages different artifacts per > component? > > > Because we currently have three (parent, api and simple imp). So my > idea > > > was to put all together under org.apache.commons.rdf groupId, but we > can > > > also stay at org.apache.commons and solve it at the artifacts' level. > > > > > > > > > Apache Commons VFS 2 uses the following pattern [1]: > > > > parent: > > org.apache.commons:commons-vfs-2-project > > core: > > org.apache.commons:commons-vfs-2 > > examples: > > org.apache.commons:commons-vfs-2-examples > > > > So for Commons RDF I would recommend the following: > > > > parent: > > org.apache.commons:commons-rdf-parent > > api: > > org.apache.commons:commons-rdf-api > > impl: > > org.apache.commons:commons-rdf-impl > > > > Would that work for you? > > > > Looks good to me. > > G > > > > > Benedikt > > > > [1] https://github.com/apache/commons-vfs > > > > > > > > > > Thanks for bringing here this discussion and your valuable feedback. > > > > > > Cheers, > > > > > > > > > On 28/03/15 14:13, Benedikt Ritter wrote: > > > > > >> Hi guys, > > >> > > >> there is a discussion in COMMONSRDF-2 [1] about the maven coordinates > > for > > >> incubation releases of Commons RDF. I may have missed something, but > my > > >> last information was, that Commons RDF has not yet decided whether it > > >> want's to join Apache Commons or go TLP in the end. So the situation > > looks > > >> like the following to me: > > >> > > >> As long as Commons RDF has not decided to join Apache Commons in the > > end, > > >> Commons RDF should not use the Apache Commons groupid. So maven > > >> coordinates > > >> should be: > > >> > > >> <groupid>org.apache.commonsrdf</groupid> > > >> <artifactid>commons-rdf</artifactid> > > >> > > >> If Commons RDF has already decided not to go TLP and to join Apache > > >> Commons > > >> after incubation, the coordinates should be (have i missed that > > decision? > > >> Sorry!): > > >> > > >> <groupid>org.apache.commons</groupid> > > >> <artifactid>commons-rdf</artifactid> > > >> > > >> Regards, > > >> Benedikt > > >> > > >> [1] https://issues.apache.org/jira/browse/COMMONSRDF-2 > > >> > > >> > > > -- > > > Sergio Fernández > > > Partner Technology Manager > > > Redlink GmbH > > > m: +43 660 2747 925 > > > e: sergio.fernan...@redlink.co > > > w: http://redlink.co > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > -- > > http://people.apache.org/~britter/ > > http://www.systemoutprintln.de/ > > http://twitter.com/BenediktRitter > > http://github.com/britter > > > > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory >
