[
https://jira.codehaus.org/browse/SUREFIRE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313078#comment-313078
]
Herve Boutemy edited comment on SUREFIRE-924 at 11/8/12 1:00 AM:
-----------------------------------------------------------------
done in
[a2929af1a62c02e2ecbc54621c5c93f6911638d6|http://git-wip-us.apache.org/repos/asf/maven-surefire/commit/a2929af1]
was (Author: hboutemy):
done in
[a2929af1|http://git-wip-us.apache.org/repos/asf/maven-surefire/commit/a2929af1]
> generate every Surefire artifact site in /surefire and redirect previous
> /plugins/maven-(surefire|failsafe|surefire-report)-plugin
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-924
> URL: https://jira.codehaus.org/browse/SUREFIRE-924
> Project: Maven Surefire
> Issue Type: Task
> Components: documentation, Maven Failsafe Plugin, Maven Surefire
> Plugin, Maven Surefire Report Plugin
> Affects Versions: 2.12.4
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Fix For: 2.13
>
>
> Surefire generates site content dispatched in misc locations:
> - /surefire
> - /plugins/maven-surefire-plugin
> - /plugins/maven-failsafe-plugin
> - /plugins/maven-surefire-report-plugin
> This will cause problems when we switch to svnpubsub+maven-scm-publish-plugin
> because this won't represent one unique svn commit
> the build should deploy everything in /surefire and the site redirect from
> /plugins/<surefure plugins locations> to /surefire/<*>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
