On 3/5/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > What you can do in maven 1 it's to add a comment and a scope to these > dependencies to explain that they are used only for the buildtime and not > for the runtime. > The documentation isn't yet updated. You can find it here : > http://people.apache.org/~aheritier/maven-stage-site/maven-1.x/plugins/xdoc/properties.html#Pom_Settings > In the xdoc plugin 1.9.2 I think that at least the comment property is > displayed. You'll perhaps need to wait the version 1.10 to display the > scope.
Thanks, Arnaud! This is useful. I have a question about the scope property, which I understand will not show up immediately, but I want to code it correctly. According to the docs here http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html the choices are "compile", "provided", "runtime" and "test". I don't see "optional." In [math], we have no hard dependencies, but if users want to use commons-discovery to configure class factories (overriding the defaults), they can do this as long as they have [discovery] and [logging] available. Specifying "runtime" as scope makes it look like these are hard dependencies, which they are not. In m2, this will also extend transitive closure. How should the scope of these dependencies be coded? Phil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
