Yea there are advantages and disadvantages either way. A big advantage of keeping the existing repository is when I see jar packages I'm not familiar with, there is a better change I'll look into them out of curiosity. I've learned more about third-party tools since I've started using Maven on the majority of my projects. :) That is really a good thing.
At the same time a DNS layout is also beneficial for better layout scenarios. We have so many projects at my work that the groupId/artifactId is not an excellent approach, but we will make do with it. I agree with you that both ways have their advantages and disadvantages - and with the new Maven-Wagon my understanding is that both ways will be supported. :) > -----Original Message----- > From: Sonnek, Ryan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 23, 2003 2:10 PM > To: 'Maven Users List' > Subject: RE: groupId naming convention > > > I know what you mean. I'm not 100% sold on having the > reverse DNS name break into folders. I think that a flat > directory structure would also be useful, for reasons like > you mentioned (browsing for artifacts). This is how eclipse > organizes their plugins, and we have adopted this same > structure on my company's maven repository. All of our > "internal" artifacts are hosted using something like > ${REPO}/org.mozilla.rhino/jars/rhino-x.x.jar > > I could live with either scenario. > > Ryan > > -----Original Message----- > From: Steve Garcia [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 23, 2003 3:55 PM > To: 'Maven Users List' > Subject: RE: groupId naming convention > > > On Tue, 2003-12-23 at 14:37, Sonnek, Ryan wrote: > > > Is there any reason for the current groupId naming > > convention? I find > > > it unnecessary that nearly all of the artifacts on ibiblio have > > > duplicate groupIds and artifactIds. Could the groupId be > > changed to > > > use the reverse DNS name (ie: org.apache.maven)? > > > > That's what the plan is, look in the Wiki. Ben's got > > something there on that specifically I believe. > > Even though I think the DNS methodology is a good one it sure > is nice to be able to go to ibiblo.org/maven and see every > type of artifact that is up there from the repository root. > Once Maven goes to the DNS way we will have to navigate the > package structure to find out if an artifact is present. And > sometimes you don't even know the artifact package structure > so you may not find the jar you are looking for. > > For instance someome tells me to use the rhino jar, now it's > located at ${REPO}/rhino, but in the future it will be > located in ${REPO}/org/mozilla/rhino. > > > > Eclipse has used this convention for > > > naming their plugins, and it really helps organize and > > differentiate > > > between files. > > > > > > Ryan > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > -- > > jvz. > > > > Jason van Zyl > > [EMAIL PROTECTED] > > http://tambora.zenplex.org > > > > In short, man creates for himself a new religion of a > > rational and technical order to justify his work and to be > > justified in it. > > > > -- Jacques Ellul, The Technological Society > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
