You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2003/08/04 18:16:39 UTC

[jira] Updated: (MAVEN-128) Allow more than one mailing list archive in Maven project file

The following issue has been updated:

    Updater: dion gillard (mailto:dion@apache.org)
       Date: Mon, 4 Aug 2003 11:15 AM
    Changes:
             environment changed to 
             timeoriginalestimate changed from 0
             timeestimate changed from 0 minutes
             Fix Version changed to 1.1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-128&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-128


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-128
    Summary: Allow more than one mailing list archive in Maven project file
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
   Fix Fors:
             1.1

   Assignee: 
   Reporter: Andrew Stevens

    Created: Wed, 2 Oct 2002 10:57 AM
    Updated: Mon, 4 Aug 2003 11:15 AM

Description:
In the schema for the Maven project descriptor, it only allows for one archive sub-element in each mailingList element.  We have some mailing lists which are archived in a few places, in particular Sourceforge's "official" archives, and Geocrawler (which has frequently been keeping up to date better recently).  It would be nice if all these archive locations could be specified for the lists in the descriptor.

Changing the schema to have
  <xs:element name="mailingList">
    <xs:complexType>
      <xs:sequence>
        <xs:element ref="name"/>
        <xs:element ref="subscribe"/>
        <xs:element ref="unsubscribe"/>
        <xs:element ref="archive" minOccurs="0" maxOccurs="unbounded"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>
would allow this, though I don't know where this actually gets used i.e. what other implications to templates etc. there might be.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org