forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ross Gardler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FOR-839) projectInfo plugin does not list all Contributors
Date Fri, 09 Jun 2006 09:14:30 GMT
    [ http://issues.apache.org/jira/browse/FOR-839?page=comments#action_12415509 ] 

Ross Gardler commented on FOR-839:
----------------------------------

As David pointed out on IRC (Forrest Friday) the problem is in:

org.apache.forrest.plugin.input.projectInfo/resources/stylesheets/changes-to-document.xsl

The issue is wit the generation of the key to identify unique contributors:

<xsl:key name="distinct-contributor" match="changes/release/action" use="@due-to"/>

This generates one entry for each commiter in the whole file, not one per release.

David reports the he has tried:

"I tried with the other technique (using preceding:: axis) and got the same problem."

What we need is a key that selects distinct values of the combinations of release/@version
and /release/@action/@dev

I'm pretty sure that is easy to do, but I have a crying baby and a dog needing walking so
I'm off out right now. Notes left here i case I don't get back to it soon.

> projectInfo plugin does not list all Contributors
> -------------------------------------------------
>
>          Key: FOR-839
>          URL: http://issues.apache.org/jira/browse/FOR-839
>      Project: Forrest
>         Type: Bug

>   Components: Plugin: input.projectInfo
>     Versions: 0.8-dev
>     Reporter: David Crossley
>      Fix For: 0.8-dev

>
> The projectInfo plugin gathers all Contributors from the "due-to" attributes and lists
them in a Contributors section for each release. However there is a flaw. For example, "Sjur
N. Moshagen" is noted on an entry for the 0.7 release  but does not get listed. It seems that
if that person was already listed for another release (e.g. Sjur is listed for the 0.8-dev)
then they are skipped.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message