Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-04 Thread Brett Porter
> That whats tough about Sun releasing jars as a standard. Where should > the api's be stored! Ultimately, I believe there are distribution > "clauses" in the lisences for these things that allow us to distribute > them in Apache software, this should also probibly apply to the > repository as

RE: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-04 Thread Carlos Sanchez
; 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]

Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-03 Thread Mark R. Diggory
Brett Porter wrote: The Maven developers have been discussing the future repository format so I can speak with reasonable authority on this. [X] +1 Put everything in one directory (such as jakarta-taglibs) Advantage: less groups on ibiblio Disadvantage: the group is going to be huge (aroun

Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-03 Thread Mark R. Diggory
-Mark 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 Lis

Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-03 Thread Mark R. Diggory
Brett Porter wrote: I thought I should discuss a little further since Mark disagrees on some points here. +1 The decision on which structure to use should be more dependent on the "type" of group structure you have. If you expect the various "subgroups" of your group to be releasing on separat

RE: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-03 Thread Brett Porter
t; 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 Devel

Re: [VOTE] Options for the Jakarta Taglibs Maven repository@cpqd.com.br

2004-08-03 Thread Felipe Leme
On Tue, 3 Aug 2004 16:29:06 +0200, "Nicolas De Loof" <[EMAIL PROTECTED]> wrote: > Just a suggestion, that may be a bad idea... I don't think it's a bad idea, but... > What about setting groupid to "taglibs/standard" ? > That may allow using a more hierarchical repository (www.ibiblio.org/maven h

RE: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-03 Thread Carlos Sanchez
ity 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

Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-03 Thread Nicolas De Loof
Just a suggestion, that may be a bad idea... What about setting groupid to "taglibs/standard" ? That may allow using a more hierarchical repository (www.ibiblio.org/maven has so much directories...) repository_root - taglibs - standard - - artifact-versi

Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-03 Thread Brett Porter
I thought I should discuss a little further since Mark disagrees on some points here. > +1 The decision on which structure to use should be more dependent on > the "type" of group structure you have. If you expect the various > "subgroups" of your group to be releasing on separate schedules and/

Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-03 Thread Brett Porter
The Maven developers have been discussing the future repository format so I can speak with reasonable authority on this. > [X] +1 Put everything in one directory (such as jakarta-taglibs) >Advantage: less groups on ibiblio >Disadvantage: the group is going to be huge (around 30-80 files o

Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-03 Thread Mark R. Diggory
Felipe Leme wrote: Hi all, As we haven't reached a common sense on how to name the groups, I think we should vote for it. The issues are: 1.Multiple directories x one directory: [ ] +1 Put everything in one directory (such as jakarta-taglibs) Advantage: less groups on ibiblio Disadvantage: th

Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-03 Thread Felipe Leme
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 grou

Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-03 Thread Felipe Leme
On Tue, 2004-08-03 at 03:44, Nicolas De Loof wrote: > MAVEN ENHANCEMENT SUGGESTION: > > Could'nt we have an automatic way to 'deprecate' some artifcat location, giving the > alternative group/artifactId to be > used ? It may been displayed by maven as a warning when downloading dependencies. > F

Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-03 Thread Felipe Leme
On Tue, 2004-08-03 at 02:21, John Casey wrote: > Just curious, but are you in control of the jakarta-taglibs builds? Yes, I am one of the committers. > understand if you're pinging the maven-dev list for best practices (I Agree, but I'm not subscribed there (and started the thread here). Could

Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-02 Thread Nicolas De Loof
[*] +1 Create one directory for group Notice some artifact allready have been uploaded on ibiblio in inconsistant directories : /xerces/jars/xmlParserApis-2.0.0/2.0.2/2.2.1 = /xml-apis/jars/xmlParserApis-2.0.0/2.0.2 Assuming 2.2.1 is only in xerces group, it looks to be the 'correct' groupid fo

Re: [VOTE] Options for the Jakarta Taglibs Maven repository

2004-08-02 Thread John Casey
Just curious, but are you in control of the jakarta-taglibs builds? I understand if you're pinging the maven-dev list for best practices (I suppose, but the maven-user list would probably be better), but if you're wanting us to actually make a change in the layout of the jakarta-taglibs organizatio