Hi, my replies are inline.
Cheers,
John
[snip]
I analyzed ALL Tomcat 5.5.9, 5.5.12 and 5.5.15 ibiblio artifacts.
What I found is:
- all 5.5.9 and 5.5.12 artifacts have empty poms - only modelVersion,
groupId, artifactId and version tags, no dependencies!!
- all 5.5.15 artifacts have NO poms (I cannot even find maven upload issue
for Tomcat 5.5.15 to check who uploaded it)
I placed first two issues on MEV:
http://jira.codehaus.org/browse/MEV-344
http://jira.codehaus.org/browse/MEV-343
I wanted someone copy empty poms from 5.5.12 to 5.5.15 changing only
version. Carlos immediately closed them with "Won't fix" status and comment
"We don't generate empty poms. If you know what the dependencies are
you can submit the pom."
I don't understand this. There are only empty poms for all Tomcat 5.5.x
artifacts.
Those empty POMs are likely a product of an early attempt to improve the
usability of the Maven 2 repository, without having to painstakingly
address the correctness. The idea was to produce something which was at
least as usable as Maven 1, which doesn't support transitive dependency
resolution. This empty POM construction was an automated process, and
the way I understand things, it's been turned off. For MEV requests,
which are meant to improve both the usability and correctness of the
repository, POMs should not be empty.
I can do an investigation (check out sources from svn, compare with distribution
sources, compile) and generate all poms with dependencies. I can even generate
sources and javadocs jars. But I don't know what is the policy.
1. Is it right to prepare pom by person which is not a product author?
When generating dependencies I may omit something that is runtime only for
example.
I'd say that getting these POMs included for maintenance in the projects
is important, but not as high a priority as maintaining the repository.
The MEV project is intended to let the community help in the maintenance
of the repository. To me, this means any user who's in a position to
know about a project's POM should be able to submit improvements. If
something turns out to be wrong, we can once again revise it.
2. Should I generate sources and javadocs jars?
I would think this is an activity for the project maintainers...it's a
little different than the POM metadata, IMO. Is this something you need
to have available in the repository?
3. How can non-author say which dependencies shold be optional?
To some extent, you can guess. If that guess is wrong, then it will be
revised by someone else who finds the error.
Personally, I'd hate to see the community paralyzed into using the
repository as-is simply because they're worried about getting something
slightly wrong, or stepping on the toes of the project dev team. Of
course, if the project publishes Maven POMs, then they need to be
involved in keeping that POM metadata as accurate as it can be; users of
those projects are in a unique position to apply pressure for this sort
of thing. ;-) However, if it's up to the Maven community to maintain a
POM, then IMO slightly wrong is still mostly right, and can be improved
upon all the more easily.
There are some other products I found their poms need improvements, and I can
suggest the improvements, but I would like to hear what do you thing about it
all
I wrote.
We can use all the help you'd like to give. :-)
Please read this guide to help in putting together MEV requests for more
efficient processing:
http://maven.apache.org/guides/mini/guide-maven-evangelism.html
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
