I've writing a plugin which, among other things, needs to rewrite a project's dependencies on the fly. In particular, it needs to change their scope to "system" and point them to a file, and it needs to do this after the transitive dependencies are resolved. (Yes, I know this is weird. No, there isn't another way. Just trust me on this.) Everything works great, until I encounter the Clover plugin. It prints out some debugging information showing the value of project.getArtifacts(), and for some reason, all of the transitive dependencies have vanished! It's behaving as if the dependency resolution started over from scratch with the system-scoped dependencies (whose transitive dependencies of course cannot be located). Does anyone know why this is happening, and how I can stop it? Essentially, I'm trying to take transitive dependencies and turn them into "first-order" system dependencies, in such a way that they will "stick" and be seen as such by later plugins in the lifecycle. --Matthew Beermann
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
