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
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 :
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 :
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
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
