> Make a parent over A and B. I think you mean an aggregating project.
> Build from the parent. > Set a dependency from B to A. > Changes in A will go into B. In this case I would stress that this is only appropriate if A and B are related and it is appropriate to (always) build them together. A different solution would be to use an IDE that will use workspace resolution instead of repository resolution. It would then use the current code base instead of what's in the repository. I know that Eclipse with m2e supports this, but there might be others as well. This would be my suggestion. IMHO, you don't want to have to do a Maven build whenever you do a small code change but rather have that happen in runtime (codetime?). /Anders > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
