History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: MPLINKCHECK-5
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Arnaud Heritier
Reporter: Florin Vancea
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Maven 1.x LinkCheck Plugin

linkcheck plugin uses global proxy settings. There is no way to perform check using a proxy while still having a non-proxied project

Created: 21/May/03 08:19 AM   Updated: 14/Jan/06 07:46 PM
Component/s: None
Affects Version/s: None
Fix Version/s: 1.4

Time Tracking:
Not Specified

Environment: Maven running behind a proxy but "remote-repo" is "inside", therefore no need for proxy.


 Description  « Hide
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.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Carlos Sanchez - 09/Jul/04 12:06 PM
Why don't use proxy and set remote repository to the machine inside the intranet?

Arnaud Heritier - 27/Dec/05 11:15 AM
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}

Arnaud Heritier - 14/Jan/06 07:46 PM
Fixed