On Wed, Apr 2, 2008 at 6:22 PM, Archie Cobbs <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 2, 2008 at 11:05 AM, Xavier Hanin <[EMAIL PROTECTED]> > wrote: > > > > *Organizations.* Regarding choice of "organization" for each module: > why > > > not > > > use the name of the project as the organization for all of the ivy > > > modules? > > > That is what we do internally in our "enterprise repository". > > > > > > This seems obvious to me, but maybe I'm misunderstanding what > > > "organization" > > > is supposed to be for. I've always thought of it as referring to the > > > people > > > that created the *module* (not the *artifacts*). > > > > > > If you don't do it that way, you eliminate the possibility of multiple > > > packagers of the same stuff, which would be bad (e.g., think about how > > > many > > > different Linux distributions there are). > > > > I think I would try to follow maven 2 conventions, just for the ease of > > use > > for people coming from maven2, and because I think they are pretty good > > when > > followed. Obviously apache commons-* would be renamed since they don't > > follow the convention. For java projects, I think using the main package > > name of the main module in the project makes sense most of the time. > > > I apologize for my ignorance... Two questions: > > 1. I know little about maven. What are the "maven 2 conventions"? To use package names convention: http://maven.apache.org/guides/mini/guide-naming-conventions.html http://docs.codehaus.org/display/MAVENUSER/Choosing+a+Group+ID > > 2. What happens in ivy when two different repositories in your > settings publish the same organization, name, and version of a module? It depends on your settings, but most probably the first one will be used and the second one ignored. The couple organization#module MUST identify a module uniquely. A module's revision is identified by organization#module + revision + extra attributes if any. But for a public repository I wouldn't use extra attributes, so sticking with pure organization#module;revision as identifier should be a good choice. Xavier > > > Thanks, > -Archie > > -- > Archie L. Cobbs > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
