Am 04.03.11 14:43, schrieb Justin Edelson: > > It depends :) the dependency plugin can operate on project dependencies (the > copy-dependencies goal) or on dependencies declared working the plugin's > configuration (the copy goal). If you used the latter, you could run into > this same issue. > > This is certainly a regression in the sense that before > maven-launchpad-plugin was introduced the launchpad bundles were dependencies > of launchpad.builder and we used copy-dependencies. Apologies for not having > spotted this possibility at the time. > No worries :)
However, we should find a solution to this problem - in one way or the other. As soon as you are referencing snapshots this might be a problem though the chance is very low if you put the builder at the bottom of the module list in the reactor. The more I think about it, the more I think it would be nice to define the list of modules in a separate project which is then just referenced by the builder. Or the builder could references more than one of these. This would allow to define kind of "feature" poms which then are included in the final launchpad. Regards Carsten -- Carsten Ziegeler [email protected]
