You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by MEZk <gi...@git.apache.org> on 2015/08/18 23:45:39 UTC
[GitHub] maven-surefire pull request: [SUREFIRE-1173] Fix redirected link o...
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 <an...@gmail.com>
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[GitHub] maven-surefire pull request: [SUREFIRE-1173] Fix redirected link o...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/101
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[GitHub] maven-surefire pull request: [SUREFIRE-1173] Fix redirected link o...
Posted by Tibor17 <gi...@git.apache.org>.
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/101#issuecomment-133910961
The /components/ URL must not be visible to our users because it's an internal URL. The non-components page must be used.
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.
It's only a limitation we 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)
If the URL is redirected, please create JIRA issue in ASF INFRA team and try to advice them to fastforward to /components/ URL instead of redirecting.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[GitHub] maven-surefire pull request: [SUREFIRE-1173] Fix redirected link o...
Posted by MEZk <gi...@git.apache.org>.
Github user MEZk commented on the pull request:
https://github.com/apache/maven-surefire/pull/101#issuecomment-132497955
@asfbot
Thank you for your answer. We've just wanted to be sure that it it not our mistake, because we will use maven linkcheck plugin to check each link in commit during development.
After adding slash at the end, the link for maven surfire plugin is:
http://maven.apache.org/surefire/maven-surefire-plugin/
link for maven surfire report plugin:
http://maven.apache.org/surefire/maven-surefire-report-plugin/
link for maven failsafe plugin:
http://maven.apache.org/surefire/maven-failsafe-plugin/
and others are reported as direct.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org