Sorry for the mistake. I have got an email from Herve who told me how to fix this issue and the reasons for the solution:
no, don't add /component to the url, but add a slash at end: <url>http://maven.apache.org/surefire/</url> I tried to document it in http://maven.apache.org/developers/website/deploy-component-reference-documentation.html "Notice: content is in fact published to /components/ directory, and rewrite rules in .htaccess detect files not found in main site to try /components/ content instead." and it's only a limitation I could not avoid that makes http://maven.apache.org/surefire do a visible unwanted redirect to http://maven.apache.org/components/surefire/ but with http://maven.apache.org/surefire/ it's not visible: it's the intended effect (and everything is necessary because of CMS staging feature, that we workarounded previously with a extpaths.txt that took more than 15 minutes to execute: but with the new .htaccess trick, CMS publishing is as fast as expected = near immediate) Regards, Hervé On Tue, Aug 18, 2015 at 11:45 PM, edwardmlyte-2 [via Maven] < ml-node+s40175n5842262...@n5.nabble.com> wrote: > GitHub user MEZk opened a pull request: > > https://github.com/apache/maven-surefire/pull/101 > > [SUREFIRE-1173] Fix redirected link on plugin's website > > Fix link in accordance with [SUREFIRE-1173]( > https://issues.apache.org/jira/browse/SUREFIRE-1173) > > You can merge this pull request into a Git repository by running: > > $ git pull https://github.com/MEZk/maven-surefire i1173-fix-link > > Alternatively you can review and apply these changes as the patch at: > > https://github.com/apache/maven-surefire/pull/101.patch > > To close this pull request, make a commit to your master/trunk branch > with (at least) the following in the commit message: > > This closes #101 > > ---- > commit fa62a1fc4a05c84567b36ccb570362e3219506c8 > Author: Andrei Selkin <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=5842262&i=0>> > Date: 2015-08-18T21:44:11Z > > [SUREFIRE-1173] Fix redirected link on plugin's website > > ---- > > > --- > If your project is set up for it, you can reply to this email and have > your > reply appear on GitHub as well. If your project does not have this feature > enabled and wishes so, or if the feature is enabled but not working, > please > contact infrastructure at [hidden email] > <http:///user/SendEmail.jtp?type=node&node=5842262&i=1> or file a JIRA > ticket > with INFRA. > --- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > <http:///user/SendEmail.jtp?type=node&node=5842262&i=2> > For additional commands, e-mail: [hidden email] > <http:///user/SendEmail.jtp?type=node&node=5842262&i=3> > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://maven.40175.n5.nabble.com/GitHub-maven-surefire-pull-request-SUREFIRE-1173-Fix-redirected-link-o-tp5842262.html > To start a new topic under Maven Developers, email > ml-node+s40175n142166...@n5.nabble.com > To unsubscribe from Maven Developers, click here > <http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=142166&code=dGlib3JkaWdhbmFAYXBhY2hlLm9yZ3wxNDIxNjZ8LTI4OTQ5MjEwMg==> > . > NAML > <http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://maven.40175.n5.nabble.com/Re-GitHub-maven-surefire-pull-request-SUREFIRE-1173-Fix-redirected-link-o-tp5842278.html Sent from the Maven Developers mailing list archive at Nabble.com.
