On 3/13/07, Thorsten Heit <[EMAIL PROTECTED]> wrote:
As long as I execute Maven commands in a directory which already contains a pom.xml, everything works as expected: Building, compiling, deploying etc. When I execute Maven commands in an empty directory, say, "mvn archetype:create -DgroupId=foo -DartifactId=bar", Maven obviously ignores my proxy settings and doesn't find plugins anymore:
Archetype does not use settings.xml : http://jira.codehaus.org/browse/ARCHETYPE-59 You can use -DremoteRepositories=... to tell it where to find repositories and other artifacts, (but that won't help you _override_ the url for the central repo.) While Maven does pick up a pom.xml in the current directory [1], I don't think it's universally true that settings.xml is ignored unless there is a pom.xml file present. For example, try mvn deploy:deploy-file, which does not require pom.xml, but will use <server> from settings.xml for userid/password/privateKey. [1] and thus you may have found a workaround for ARCHETYPE-59 -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
