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 organization on ibiblio, you're talking to the wrong
people...the taglibs people are able to control that.
just FYI.
-j
On Tue, 2004-08-03 at 01:02, 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: the group is going to be huge (around 30-80 files on
> each artifact sub-dir)
> [ ] +1 Create one directory for group (ex: taglibs-standard,
> taglibs-request).
> Advantages: easier to locate artifacts; consistent with the way
> Jakarta Commons is organized
> [ ] +0 Doesn't matter for me
>
> 2.(In case one directory wins previous poll)
> [ ] +1 Use new directory 'jakarta-taglibs
> Advantage: better identify which taglibs that group refers too
> Disadvantage: replication of existing directory ('taglibs')
> [ ] +1 Use existing directory 'taglibs'
> Advantage: no replication of existing directory
> Disadvantage: name is too generic
> [ ] +0 Doesn't matter for me
>
> 3.Where to put jstl.jar
> [ ] +1 Wherever standard.jar is
> Advantage: jstl.jar is created by Jakarta Standard Taglibs
> Disadvantage: it's a JCP API of its own; replication of existing
> directory ('jstl')
> [ ] +1 On existing group jstl
> Advantage: no replication of existing directory; better separation
> between specification (JSTL) and implementation (Jakarta Standard
> Taglibs)
> Disadvantage: jar is created by another project (there is no JSTL
> project on Jakarta/ASF); inconsistent with another groups (like
> servletapi)
> [ ] +1 On new group jstlapi
> Advantage: consistent with another groups (like servletapi); better
> separation between specification (JSTL) and implementation (Jakarta
> Standard Taglibs)
> Disadvantage: jar is created by another project (there is no JSTL
> project on Jakarta/ASF), replication of existing directory ('jstl');
> ugly name
> [ ] +0 Doesn't matter for me
>
>
> Notice that this is note a typical committer-issue-vote (it's not even
> totally related to the Maven project itself), but I rather listen your
> opinions now then decide the structure myself and have to handle the
> consequences later (specially because we cannot change it once it's
> uploaded to ibiblio).
>
> Regards,
>
> Felipe
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
John Casey
[EMAIL PROTECTED]
CommonJava Open Components Project
http://www.commonjava.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
