[ http://jira.codehaus.org/browse/MPLINKCHECK-5?page=all ]

Arnaud Heritier updated MPLINKCHECK-5:
--------------------------------------

    Fix Version: 1.4

We'll add some properties to the plugin :
maven.linkcheck.proxy.host=${maven.proxy.host}
maven.linkcheck.proxy.port=${maven.proxy.port}
maven.linkcheck.proxy.username=${maven.proxy.username}
maven.linkcheck.proxy.password=${maven.proxy.password}
maven.linkcheck.proxy.ntlm.host=${maven.proxy.ntlm.host}
maven.linkcheck.proxy.ntlm.domain=${maven.proxy.ntlm.domain}

> linkcheck plugin uses global proxy settings. There is no way to perform check 
> using a proxy while still having a non-proxied project
> ------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: MPLINKCHECK-5
>          URL: http://jira.codehaus.org/browse/MPLINKCHECK-5
>      Project: maven-linkcheck-plugin
>         Type: Improvement

>  Environment: Maven running behind a proxy but "remote-repo" is "inside", 
> therefore no need for proxy.
>     Reporter: Florin Vancea
>     Assignee: Arnaud Heritier
>     Priority: Minor
>      Fix For: 1.4

>
>
> 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.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to