Re: [pool] Dependency on Xerces
I know M2 has stuff for this (different types of dependency). I think for M1 you'd have to either use the maven.xml to tricky the plugin that builds this page, or just write the page by hand and have the navigation point to that hardcoded one. However I don't think we could do that in our current site-nav structure though, don't think M1 lets you modify the navigation links inside the project reports/info sections. So a rather useless reply I guess :) Hopefully it'll lure someone else into giving a constructive answer. Hen On 3/4/06, Stephen Colebourne [EMAIL PROTECTED] wrote: I was confused for a while because the [pool] website says it is dependent on xerces and xml-apis. Now I have downloaded the source, I can see the comment about this being for maven only. Is there any way that these can be removed? The junit one can be removed (even though the mavenites tell you not to). The way the page is generated indicates that [pool] has dependencies, when in fact it doesn't. Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pool] Dependency on Xerces
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. Arnaud On 3/5/06, Henri Yandell [EMAIL PROTECTED] wrote: I know M2 has stuff for this (different types of dependency). I think for M1 you'd have to either use the maven.xml to tricky the plugin that builds this page, or just write the page by hand and have the navigation point to that hardcoded one. However I don't think we could do that in our current site-nav structure though, don't think M1 lets you modify the navigation links inside the project reports/info sections. So a rather useless reply I guess :) Hopefully it'll lure someone else into giving a constructive answer. Hen On 3/4/06, Stephen Colebourne [EMAIL PROTECTED] wrote: I was confused for a while because the [pool] website says it is dependent on xerces and xml-apis. Now I have downloaded the source, I can see the comment about this being for maven only. Is there any way that these can be removed? The junit one can be removed (even though the mavenites tell you not to). The way the page is generated indicates that [pool] has dependencies, when in fact it doesn't. Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[all] Using maven dependency scope and comment properties WAS: Re: [pool] Dependency on Xerces
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]
Re: [all] Using maven dependency scope and comment properties WAS: Re: [pool] Dependency on Xerces
On 3/5/06, Phil Steitz [EMAIL PROTECTED] wrote: 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. Optional isn't a scope, it's just optionaltrue/optional. HTH, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pool] Dependency on Xerces
I was confused for a while because the [pool] website says it is dependent on xerces and xml-apis. Now I have downloaded the source, I can see the comment about this being for maven only. Is there any way that these can be removed? The junit one can be removed (even though the mavenites tell you not to). The way the page is generated indicates that [pool] has dependencies, when in fact it doesn't. Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
