Michal Maczka wrote:
>>As Ben noted, we may need to have dependencies with varying 'transitive'
>>status per kind. For example it is very common that a library is
>>required for compiling and running your project, but at the same time
>>only for running your project dependencies. Suppose we have:
> I don't understand.
A descriptor of a hypotetical web application toolkit, in it's master
project. The toolkit has three sub projects: a jar, a tld and web
contnent drop (js/css).
<project>
<groupId>footolkit.org</groupId>
<artifactId>footoolkit</artifactId>
<vesrion>1.0</version>
<dependencies>
<dependency>
<groupId>footolkit.org</groupId>
<artifactId>footoolkit-classes</artifactId>
<version>${pom.version}</version>
<type>jar</type>
<kind>war.bundle.transitive</kind>
<kind>compilation.transitive</kind>
</dependency>
<dependency>
<groupId>footolkit.org</groupId>
<artifactId>footoolkit-tags</artifactId>
<version>${pom.version}</version>
<type>tld</type>
<kind>war.bundle.transitive</kind>
</dependency>
<dependency>
<groupId>footolkit.org</groupId>
<artifactId>footoolkit-content</artifactId>
<version>${pom.version}</version>
<type>web-content</type>
<kind>war.bundle.transitive</kind>
</dependency>
</dependencies>
</project>
Then in a war project you declare a dependency on 'footolkit' and get
compile dependency footoolkit-classes, and get the jar, tld and
web-content stuff bundled in your war without any further hassle.
Makes sense now?
R.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
