Update, I have figured out what my problem was. I had entered my <proxy> element directly within my <settings> element in my xml, instead of nesting it inside of a <proxies> element. This brings me to a new question though. Shouldn't the xml be checked against a schema or DTD before maven continues with its invocation?
Thanks, Pepper Jobe SAS Institute -----Original Message----- From: Pepper Jobe [mailto:[EMAIL PROTECTED] Sent: Monday, August 29, 2005 8:37 PM To: [email protected] Subject: [m2] Proxy Settings Test Team, This is my first time posting to this list, so my apologies if I am not following suggested practices or formats. I have downloaded the maven-2.0-alpha-3-bin.zip for windows from your site and followed the installation instructions. I have also configured my settings.xml file in my {home}/.m2 directory. I am behind a firewall at work, and therefore needed to set up a proxy entry in the settings.xml file. Assuming that all of this was set up correctly, I tried a: $>m2 archetype:create -DgroupId=com.company.app -DartifactId=my-app Just to see what it does. Unfortunately, as I found by using the -e option, maven can't find the RELEASE maven-archetype-plugin, according to the stack trace. I navigated in my web browser to the http://repo1.maven.org/maven2/plugins URL, and was able to navigate to the org/apache/maven/plugins/maven-archetype-plugin directory with no problems. This leads me to believe that the proxy settings that maven is picking up from my settings.xml file may not be working correctly. Is there an easy way to test my suspicions? Thanks, Pepper Jobe SAS Institute --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
