Hi all

We know there are many errors in poms on ibiblio. I would like
to help to improve some of them.

There are some areas I am interesting most. First Tomcat 5.5.x.

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.

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.
2. Should I generate sources and javadocs jars?
3. How can non-author say which dependencies shold be optional?

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.

Greg

Reply via email to