The following comment has been added to this issue:
Author: Felipe Leme
Created: Wed, 4 Aug 2004 11:54 AM
Body:
By next version you mean 1.1, right?
I will try to change it anyway (even if you don't apply the changes now), so I can get
more familiar with Maven core.
But I agree the change on the POM must be better discussed, as it may break backwards
compatibility. For instance, if it's changed to have a <archives> section, then the
new mail-lists.xml won't work with old POMS, unless we use a pomVersion #if statement.
Something like this:
#if ($project.pomVersion < 4 )
#displayLink("Archive" $list.archive)
#else
#forEach( $archive in $list.archives)
#displayLink("Archive" $archive)<br>
#end
#end
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-128?page=comments#action_22736
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/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
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
model additions
Fix Fors:
1.1
Assignee:
Reporter: Andrew Stevens
Created: Wed, 2 Oct 2002 10:57 AM
Updated: Wed, 4 Aug 2004 11:54 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
