I want to propose following changes in POM:

a) Add <javadoc> tag which points to a place where javadoc of given project
is accessible (URL)
    I should be on the same level as <url> tag.

   This can be used e.g. by javadoc plugin.



b) <comment> tag inside of <dependency> tag
   I quite frequently use XML comments  (<!-- --> )
   to describe why do I need a given dependency, or why e.g. I use version
1.1 when 1.3 is already
   out. I think it would be nice to see such comments in reports.

c) I would like also to remove in future <url> tag from <dependency>. This
information can be easily
   accessed from POM of given artifact. I have rewritten xdoc plugin and now
if there is a POM
   of given dependency present in a local repository, dependency report is
able to retrieve artifact's description
   and url from it. Still <url> tag wins if user has provided it.

   All we need is to have much more POMS in the repository!!

   a) What about creating area in Maven Wiki where users will be able to
edit/ submit new POMS.

   b) What about officially do not let any new artifact to be put to ibiblio
repository
   without the POM which describe it? So basically being very strict about
the rules
   described in http://maven.apache.org/repository-upload.html
   and every time upload both: artifact and its POM? Maybe even the set of
mandatory tags in POM
   should be extended?

   I can easily hook POM deployment to artifact:install, artifact:deploy
goals, so if any of those two goals
   is called POM is also installed/deployed.



regards

Michal




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to