On 2/28/06, Grzegorz Słowikowski <[EMAIL PROTECTED]> wrote: 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)
It would have been synced from the Apache repository, not uploaded. I'm not sure about "we don't generate empty poms" though. Has that changed? If there was no pom we used to get a minimal one so Maven 2 would at least "work" even without transitive dependencies. > 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. For an Apache project with missing poms, I think the best thing is to convince the developers to put the files in dist/java-repository where they will sync over to ibiblio. Less work for Carlos that way. :) If you have time to create the poms and open a Bugzilla 'enhancement' ticket with Tomcat, I'll watch for it and help. -- Wendy
