[*] +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 for this 
artifact. But for compatibility
those jars remain in xml-api with a Readme.html warning.


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.
For example, a stamp file "groupid/type/artifactid-version.deprecated" may be a text 
file containing the warning message
that maven can search when it downloads an artifact.

Nico.



----- Original Message ----- 
From: "Felipe Leme" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, August 03, 2004 7:02 AM
Subject: [VOTE] Options for the Jakarta Taglibs Maven repository


> 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]



Our name has changed.  Please update your address book to the following format: 
"[EMAIL PROTECTED]".

This message contains information that may be privileged or confidential and is the 
property of the Capgemini Group. It is intended only for the person to whom it is 
addressed. If you are not the intended recipient,  you are not authorized to read, 
print, retain, copy, disseminate,  distribute, or use this message or any part 
thereof. If you receive this  message in error, please notify the sender immediately 
and delete all  copies of this message.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to