Here's a use case, and I think a way to make something that works. Project A wants to make use of a dependency from project B. There is, however a bug. Project B is, for whatever reason, not going to release a bugfix any time soon. Project A really doesn't want to establish a full fork.
In the good old days of open source, A would distribute a patch and leave it to their users to apply it. Now, consider a Maven project that is part of the tree of A. It's g/a/v says: 'our.fixed.version':'of-project-b':v. It uses a maven plugin to download the source of B. It applies a patch. It then uses the invoker, or anrun, or something, to build B. It then needs to attach the results so that the reactor can see them, and all is well. (It can shade or not as appropriate to circumstances). There is also a more philosophical use case that I won't bore you with. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
