Indeed, our use case for purge-local-repository is a bit dodgy and definitely sub-optimal.
Our project depends on various corporate libraries which are not "Mavenized". In order to use these libraries, we frequently use deploy:deploy-file to drop them on our repository, with a fixed version (given that new versions are duly tested and obsolete older versions). Clearly, this is not the best way of doing things, but it was by far the easiest solution for us, and we expected it to be somewhat sustainable. The purge-local-repo goal (with the right set of exclusions) was used in order to ensure the latest versions of there corporate libraries were used whenever we release a new version of the project. I configured an execution as it was the first idea I had in order to have the goal run once for a multi-module build. Now, since it doesn't seem to work all that well, it probably won't be too hard finding another way around, so I suppose we can say my problem is closed. But I'm still curious as to why this problem occurred, can anyone fill me in on that ? No biggie if it's not possible, but I do wonder what I did wrong there (aside from the management of non-maven libraries ;) ) ! Anyway, thanks for your insight, Wayne ! Philippe -- View this message in context: http://maven.40175.n5.nabble.com/Different-behavior-when-building-a-project-as-a-module-or-stand-alone-tp5607081p5612860.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
