So this means that the bundles/modules listed in bundles/list.xml are not taken into account when Maven builds the dependency tree to calculate the build order for a multi project build, right?
Regards Carsten Justin Edelson wrote > There's not much we can do about this within the launchpad plugin. > IIUC, plugins aren't consulted when building the module sequence list. > What might work is to add launchpad.content as a dependency > (scope=provided? or test?). I'm a bit surprised you're having this > issue as launchpad/content is before launchpad/builder in the module > list in the root pom. > > I don't have time right now to look at this, but should later this > evening. Can you file a JIRA and assign it to me? > > Justin > > On Wed, Mar 2, 2011 at 12:29 PM, Felix Meschberger <[email protected]> wrote: >> Hi all, >> >> When doing a full build like this: >> >> * Remove all Sling SNAPSHOT from your local maven repo >> * mvn -o clean install >> >> The Launchpad Builder will fail, because the Launchpad Content will only >> be built after the builder ... >> >> It looks like the launchpad plugin properly fails builds for missing >> artifacts but it does not properly support build order for multimodule >> builds. >> >> This happens for me with Maven 3.0.2. >> >> Can we do something about this ? >> >> Regards >> Felix >> >> > -- Carsten Ziegeler [email protected]
