Hi, I just think that jstl shouldn't be mixed with concrete implementations.
About the other issues with group names maybe we should consider the repository layout. Currently anyone can request an upload to any group and I think this won't scale well and can lead to conflict problems. Having strict naming conventions will avoid problems like those happening now with jakarta-taglibs. A solution could be adding the domain or package name in some way, e.g. apache.jakarta.taglibs apache-jakarta-taglibs apache/jakarta/taglibs Anything after the domain name would be responsability of the domain owner. Regards Carlos Sanchez A Coruņa, Spain Oness Project http://oness.sourceforge.net > -----Original Message----- > From: Felipe Leme [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 03, 2004 1:19 PM > To: Maven Developers List > Subject: Re: [VOTE] Options for the Jakarta Taglibs Maven repository > > Oops, forgot my votes: > > > 1.Multiple directories x one directory: > > [X ] +1 Create one directory for group (ex: > taglibs-standard, > taglibs-request). > > Advantages: easier to locate artifacts; consistent with > the way > Jakarta Commons is organized > > > 3.Where to put jstl.jar > > [X] +1 On existing group jstl > > Advantage: no replication of existing directory; > better separation > > between specification (JSTL) and implementation (Jakarta > Standard > Taglibs) > > For this one, I changed my mind after Carlos' messages... > > > -- Felipe > > > --------------------------------------------------------------------- > 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]
