river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Reedy <dennis.re...@gmail.com>
Subject Re: svn commit: r1591133 - in /river/jtsk/skunk/qa_refactor/trunk/modularize/apache-river: ./ dist/ river-dl/ river-lib/ river-platform/ river-resources/ river-services/mahalo/mahalo-dl/ river-services/mahalo/mahalo-service/ river-services/mercury/mercury-...
Date Wed, 30 Apr 2014 00:09:33 GMT
Hi Greg,

The accepted convention is if the project is a multiple module project, it
should append a new identifier to the parent's groupId. In the case of
river-services, a todo item (for right now) is to add poms for outrigger,
mahalo, etc ...

http://maven.apache.org/guides/mini/guide-naming-conventions.html

Dennis

On Tue, Apr 29, 2014 at 7:37 PM, Greg Trasuk <trasukg@stratuscom.com> wrote:

>
> Shouldn’t the group id be just ‘org.apache.river’ for all of them, instead
> of ‘org.apache.river.mahalo’, ‘org.apache.river.outrigger’, etc?
>
> Cheers,
>
> Greg Trasuk.
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message