On 3/3/11, Bertrand Delacretaz <[email protected]> wrote:
> On Thu, Mar 3, 2011 at 2:34 PM, Justin Edelson <[email protected]>
> wrote:
>> On Mar 3, 2011, at 4:55 AM, Carsten Ziegeler <[email protected]> wrote:
>>
>>> 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?
> ...
>> Correct.
>
> Could this be changed at the plugin level?
> Can a Maven plugin inject additional dependencies?
>
> -Bertrand
>
Not as far as I know. By the time the plugin executes, the project
model (including the dependency graph) has already been generated.
The problem right now is that there's a dependency from
testing/samples/integration-tests to launchpad/builder:
<dependency>
<groupId>org.apache.sling</groupId>
<artifactId>org.apache.sling.launchpad</artifactId>
<classifier>standalone</classifier>
<version>6-SNAPSHOT</version>
</dependency>
Would it be possible to move the testing samples to the samples
directory? Alternatively, there's probably a way to restructure the
testing aggregator pom, but it seems to me samples don't belong in the
main source tree.
Justin
