Michal Maczka wrote:We can make it without <url> tag.
Other thinng I was thinking of is to introduce <javadocUrl> element
javadocUrl will point to URL when project's javadocs are accessible. This can be used for liniking project's javadocs with javadocs of other projects
(http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javadoc.html#link)
I've been toying with a "intra-maven" concept for a while now (in an effort to understand the maven internals better).
If we leave the <url> in the dependency, we could make all maven generated sites auto-link to each other.
For example it is just enough to put download URL of javamail to http://www.ibblio.org/maven/javamail/poms/javamail-1.1.pom
and every project can profit from this.
Anyway - I am _not_ proposing that we should drop <url> tag.
What I was hoping to do: * Auto-identify mavenized projects in the dependency report.
Maveized = Those which (can) have POM in your local repository or even some kind of POM database.
Not those which are using Maven as their build system.
* Auto-link javadoc from other mavenized projects.
That's why I want to have standard javadoc tag in POM.
It's all planned since a long time.* Auto-determine deep dependency links. MyProject -> Struts -> Commons-Beanutils (for example) * On compile, auto-notify of new upgrades to dependencies?
Michal
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
