<dependency> <id>commons-jelly</id> <artifactId>commons-jelly-tags-log</artifactId> <version>20030211.142821</version> </dependency>
This is still vaugely unsatisfying, as the dependency section of the project is supposed to be what the project itself needs, not what its build system requires.
Alternative suggestions most welcome.
I think the dependency approach is not that crazy if we have flags or roles for the dependencies.
Something like:
<dependency>
<id>commons-jelly</id>
<artifactId>commons-jelly-tags-log</artifactId>
<version>20030211.142821</version>
<usedIn role="maven-jelly"/>
<usedIn role="jUnit-tests"/>
</dependency>seems to be decent to me... (and the problem is the same for unit-test things).
Paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
