Vincent Massol wrote:



-----Original Message-----
From: Michal Maczka [mailto:[EMAIL PROTECTED]
Sent: 13 November 2003 10:44
To: Maven Developers List
Subject: Re: [VOTE] Adding type element in POM



[snip]




When any changes to POM will be introduced should we increment it to
<pomVersion>4</pomVersion>?



+1. The pom:validate should use this information to validate the POM and we should have the different XSD version files distributed with Maven.



I have few more prosition for things which can be added to POM.

I personally think that <url> tag inside <dependecy> element is not so
much needed (as it can be found  in  POM  database)
but very freqently I need  to document  "why  I need this artifact" or
"why this particular version is used" etc.

<dependency>
<groupId>forehead</groupId>
<artifactId>forehead</artifactId>
<version>1.0</version>
<type>jar</type>
<comment>We want to replace forehead with classworlds</comment>
</dependency>



What do you want to do with <comment>? Put it in the dependency report?




Yes. IMHO This will make project documentation more complete. I




Of course <url> is not hurting and can stay.

One more proposition (I think Jason was thinking about it)

What about renaming
<currentVersion> element to <version> so we have perfect match


between


POM and Dependency
( pom.groupId = dep.groupId, pom.artifactId = dep.artifactId,


pom.type


= dep.type, pom.version=dep.version)



+1 but we should deprecate <currentVersion> and not remove it right away.




Sure!!


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)

How is this different from all other Maven reports. They are all in
well-defined places, including the javadoc one, no? For Javadoc, for any
project, it is:

${pom.siteAddress}/apidocs/index.html



URL of javadocs is "fixed" only for projects which were built with Maven.
POM is an universal project descriptor and can be used without maven - you can create and publish (via repository) a POM for any project -
even for such projects which do not use maven (e.g. xerces, ant, xalan, struts ).



Michal




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



Reply via email to