[jira] Commented: (MPLINKCHECK-5) linkcheck plugin uses global proxy settings. There is no way to perform check using a proxy while still having a non-proxied project

[ji...@codehaus.org]

The following comment has been added to this issue:

     Author: Carlos Sanchez
    Created: Fri, 9 Jul 2004 12:06 PM
       Body:
Why don't use proxy and set remote repository to the machine inside the intranet?
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MPLINKCHECK-5?page=comments#action_21572

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPLINKCHECK-5

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPLINKCHECK-5
    Summary: linkcheck plugin uses global proxy settings. There is no way to perform check using a proxy while still having a non-proxied project
       Type: Improvement

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-linkcheck-plugin

   Assignee: 
   Reporter: Florin Vancea

    Created: Wed, 21 May 2003 8:19 AM
    Updated: Fri, 9 Jul 2004 12:06 PM
Environment: Maven running behind a proxy but "remote-repo" is "inside", therefore no need for proxy.

Description:
Suppose the following setup:
- local network behind a proxy
- one "remote repository" running on a local machine, mirror of ibiblio
- Maven builds get the resources from the above "remote repository", hence no need for proxy settings in the projects. Actually, setting a proxy would only slow things down.

When running "site:generate" linkcheck kicks in, but sees no proxy and fails trying to reach outside links like "http://maven.apache.org/".

If we set a proxy the general build process is slowed unnecessarily.
If not, goals like "site:generate" are slooooow to run due to timeouts in linkcheck.

AFAIK there is no (obvious/direct/simple) way to have "no proxy" when building and "some proxy" when linkchecking.

Suggestion 1:
allow linkcheck to use its own set of proxy settings if the "normal" ones are not found. Some property like "maven.linkcheck.proxy.host=192.168.0.1".

Suggestion 2:
Use automatically proxy settings from the environment (global env, not Maven's). These would be users's settings for browsing the Net anyway, so these are probably the best choice anyway.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org