+ 1.Ok, after the discussion on the thread titled "[Proposal] Project deliverables definition in POM", it seems we agree on adding a <type> element in the POM for now. As not everyone has answered, I'd like to propose a vote for this. If it passes, I can implement it quickly.
Here's my +1
I Just have a question :)
We are using: <pomVersion>3</pomVersion>
When any changes to POM will be introduced should we increment it to <pomVersion>4</pomVersion>?
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>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)
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)
Michal
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
