On Mon, Jun 27, 2011 at 9:44 AM, Benson Margulies <[email protected]> wrote: > OK, bear of little brain time here. If I use install:install-file on a > file URL, I can turn around after that and use the resulting thing as > a <repository>?
No, you'd want deploy:deploy-file, however I wouldn't try that with a snapshot, I'm not sure it would get the timestamped snapshot filename and metadata quite right, and in any case it isn't going to test what a user would be reporting. I would set up project A that uses dependency B. In B, configure distributionManagement to file://path/to/remote/repo . When you deploy that snapshot, use a separate local repository so you don't step on the one you're using with A to test the snapshot download. Now build A normally, and it should retrieve the snapshot. Then deploy a new snapshot of B (again using the separate local repo.) Build A using whatever setting is supposed to NOT retrieve snapshots, and see if it does. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
