[ 
https://issues.apache.org/jira/browse/MPIR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935007#comment-16935007
 ] 

Sebb commented on MPIR-385:
---------------------------

I see the patch fixes the code by adding a new method.

However, this used to work in version 2.9, so the correct code was present then.
Given that this issue has affected two parts of the pom (this and developer 
mails), it seems likely that there was a change that affected both.

Seems to me it would be better to establish why the formatting broke for both 
parts and fix that.
There may be other formatting issues that have yet to be found that depend on 
the code that was changed.

> Emails in mailing list section of pom are improperly handled
> ------------------------------------------------------------
>
>                 Key: MPIR-385
>                 URL: https://issues.apache.org/jira/browse/MPIR-385
>             Project: Maven Project Info Reports Plugin
>          Issue Type: Bug
>          Components: mailing-lists
>    Affects Versions: 3.0.0, 3.0.1
>            Reporter: Sebb
>            Priority: Major
>              Labels: regression
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The generated file mailing-lists.html contains email names of the form:
> <td><a href="test-subscr...@maven.apache.org">Subscribe</a></td>
> instead of
> <td><a href="mailto:test-subscr...@maven.apache.org";>Subscribe</a></td>
> Since the protocol is omitted, browsers assume it is the same as the page, 
> i.e. http[s].
> Easy to demonstrate:
> clone the repo
> mvn clean integration-test
> examine target/test-harness/mailing-lists/mailing-lists.html
> To show that it worked previously, checkout the tag 
> maven-project-info-reports-plugin-2.9
> and try the test again.
> examine the file target/test-harness/mailing-lists/mail-lists.html
> There don't appear to be any tests to check whether the table entries are 
> correctly generated.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to