> We can make it without <url> tag.
> 
> 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.

Heh. *whew*.
But having the pom in the repo as well as the jar has turned out
to be very inconsistent, and I was getting the feeling it was
more of an optional thing, outside of the control of the individual
project.xml maintainer as to if their dependencies include an
accessible pom or not.

Some examples:
http://www.ibiblio.org/maven/pmd/poms/  (no poms dir)
http://www.ibiblio.org/maven/commons-pool/poms/  (no files)
http://www.ibiblio.org/maven/commons-logging/poms/  (no files)
http://www.ibiblio.org/maven/commons-collections/poms/ (no files)
http://www.ibiblio.org/maven/commons-fileupload/poms/ (no files)
http://www.ibiblio.org/maven/xerces/poms/ (no files)
http://www.ibiblio.org/maven/xdoclet/poms/ (no files)
http://www.ibiblio.org/maven/xalan/poms/ (no files)

based off of observation, I felt using the dependency/url would
be a good place for the project.xml maintainer to specify the linking
to other projects, and if those projects happened to be built using
maven, there could be a way to get the information i wanted in a 
consistent way.

>> 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.
>
>> * Auto-determine deep dependency links.
>>    MyProject -> Struts -> Commons-Beanutils (for example)
>> * On compile, auto-notify of new upgrades to dependencies?
>>
> It's all planned since a long time.

Fantastic! Sorry, been lurking since B8, didn't see that discussion.
Guess I'll go back to working on the plugin's side, didn't mean to
derail this discussion.

Also, if there is open discussion about changes to the pom, are there
plans to address any of the requests for project.xml changes in the
jira?  (i have a personal interest in MAVEN-954, and would like to 
see more meta-data in the <developer> elements.  In a corporate
environment, phone number, department, etc.. are terribly useful.)

/* Joakim Erdfelt - Cingular Wireless */

Reply via email to