On Oct 10, 2007, at 2:26 AM, David Jencks wrote:
0. As at present, any dependency in the c-m-p config must already
be in the pom dependencies.
1. All the (compile, runtime) scoped maven dependencies in the pom
turn into plan dependencies and geronimo-plugin.xml dependencies
2. Unless overridden the import type is "all"
3. For other import types or other customization a dependency can
be mentioned in the c-m-p config in the pom.
#1-3 look right on. I'm wondering if #0 is really necessary and
desirable. For example, if I create plugin1 that needs a service
type dependency against plugin2 then the pom could look like:
<project>
<artifactId>plugin1</artifactId>
<dependencies>
// a reference to plugin2 is not desirable here, don't
// want maven processing it as a build time dep or
// including its classes in the environment inherited
// by car-maven-plugin
</dependencies>
<build>
<plugin>
<artifactId>car-maven-plugin</artifactId>
<configuration>
<dependency>
<artifactId>plugin2</artifactId>
<import>service</import>
</dependency>
</configuration>
</plugin>
</build>
</project
Best wishes,
Paul
