[
http://jira.codehaus.org/browse/MNG-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190560#action_190560
]
Brett Porter commented on MNG-4351:
-----------------------------------
if you enable checksum verification it will do this for you.
> Prevent copying of proxy config script to pom file (with XML validation?)
> -------------------------------------------------------------------------
>
> Key: MNG-4351
> URL: http://jira.codehaus.org/browse/MNG-4351
> Project: Maven 2
> Issue Type: Improvement
> Components: Settings
> Affects Versions: 2.2.1
> Environment: Cygwin on WXP Pro
> Reporter: Jeff Cadow
> Priority: Minor
> Attachments: apache-4.pom.bad
>
>
> Because I screwed up my settings.xml file, Maven copied the contents of my
> network's proxy configuration script to
> repository/org/apache/apache/4/apache-4.pom. It failed to find everything
> after that.
> To get maven to work in my proxy-protected network, I added the following to
> my settings.xml file:
> <proxies>
> <proxy>
> <active>true</active>
> <protocol>http</protocol>
> <host>proxy</host>
> <port>8083</port>
> </proxy>
> </proxies>
> That was dumb - port 8083 is where my office's proxy configuration script is.
> I should have used port 8080.
> But Maven's behavior was kinda sloppy. It quietly copied the proxy
> configuration script, which looks nothing like XML, to
> ~/.m2/repository/org/apache/apache/4/apache-4.pom. I've attached the result
> (after munging the host names) as apache-4.pom.bad.
> Maven could at least check whether retrieved files meant to be XML are
> actually valid XML and issue an error immediately when they're not. Schema
> validation would be a nice 2nd step of safeguarding.
--
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
