I'm not positive, but I think that <extensions> block will just make wagon-ftp available as it is needed. I think it's the maven-deploy-plugin that does the work of picking what to send. But maybe someone with more knowledge of multi-module builds can help?
Paul Jeff Mutonho wrote: > > On 10/25/06, pjungwir <[EMAIL PROTECTED]> wrote: >> >> Hi Jeff, >> >> What is the benefit of loading wagon-ftp in a profile? That <extensions> >> block doesn't per se do anything; it just makes wagon-ftp available. I >> guess >> you're loading it for the sake of the sftp:// repository in the top-level >> POM? Then why not just put <extensions> up there, too (with no profile)? >> >> Paul >> >> -- > > If I put it in the top-level POM , how will it know which ear file to > ftp to the sftp:// repository ? > My build results in two different ear files, one with a web > application and another with some ejb application.The reason for > having two different ears is that the two ears are deployed > differently and they serve different purposes. > Basically all I want to do is ftp two ear files at the end of my build > to my sftp:// repository.That's all I wanna do. > > -- > > > Jeff Mutonho > > GoogleTalk : ejbengine > Skype : ejbengine > Registered Linux user number 366042 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/ftp-wagon-Unrecognised-tag%3A-%27extensions%27-tf2496953.html#a7014831 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
