Carlos Sanchez wrote:
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 well.Hi,
I just think that jstl shouldn't be mixed with concrete implementations.
The point in keeping this separate from the taglibs is that they can be maintained as to not have multiple copies in the repository. For instance, if tomcat releases jasper with jstl included and taglibs releases standard with the jstl ja included too, then there are two copies of the jar present in the repository. Where, if they both list them separately as a dependency, then we can maintain just a single copy of the jar in the repository as a separate project, both can reference it as a dependency, thus I think its important that it be separate, just like the servletapi.
About the other issues with group names maybe we should consider theLike Brett said, we just don't have the transition to those naming conventions stablized yet (sigh) is a very painfull transition that is being held off because it will impact so many projects when it happens. So his argument that we should just use "taglibs" for now is valid in that it may all change in the near future when we attempt this transition. I'll retract my statement that they should be separate project directories (taglibs-standard, taglibs-jndi, etc) because if we are consolidating commons into one directory structure as a goal then other projects should follow this theme.
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
-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 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]
-- Mark R. Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
