[
https://jira.codehaus.org/browse/MNG-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-4351:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> Prevent copying of proxy config script to pom file (with XML validation?)
> -------------------------------------------------------------------------
>
> Key: MNG-4351
> URL: https://jira.codehaus.org/browse/MNG-4351
> Project: Maven
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
