I don't have the stack trace anymore, but it was throwing a null pointer in the wagon-ftp at line 118, which is where it attempts to trim the username and password. This happens using maven directly if I don't define a username and pword. We also saw it not using the settings.xml when we defined our repositories there because it was unable to deploy. When we moved the repository setting to the pom, we got to the wagon exception. We then reconfigured the ant file to also contain the repository and login info and it works that way.
-----Original Message----- From: Edwin Punzalan [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 18, 2005 4:48 AM To: Maven Users List Subject: Re: maven ant not finding settings.xml? Can you send us the stack trace or the output so we can better comment on it? Thanks. Brian E. Fox wrote: >Hello, >We have reproduced this problem on beta 3 and rc1: > >We are using an ant script to call maven deploy to auto deploy jar, pom >and md5's and sh1's for 3rd party libraries to our remote repository. >The maven deploy ant task isn't using the settings to find our mirrors >or repositories for download. We have a parent pom that it should find, >but it's not. The settings.xml is in maven/conf and in HOME/.m2/ > >Is this a bug, or do we need to do something else for it to find the >settings? > > > --------------------------------------------------------------------- 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]
