Enter a JIRA issue at http://jira.codehaus.org/browse/MEV
I've found that there are a HELL of a lot of problems with POMs. Many of them are either minimal with no dependencies or contain EVERY dependency without regard to scope. Spring 1.1.5, for instance, is minimal and does not declare aopalliance. dom4j 1.6 OTOH is everything and the kitchen sink. I would suggest that the maven2 team get a little more strict on the quality of the POMs they accept - the quality of those POMs directly affects people's overall perception of the quality of maven2 itself. -----Original Message----- From: Orjan Austvold [mailto:[EMAIL PROTECTED] Sent: Thursday, September 22, 2005 4:34 PM To: Maven Users List Subject: [m2] commons-lang and commons-codec includes junit for scope compile This is probably not the right list to post this message to, but... Both commons-lang (2.1) and commons-codec (1.3) include junit for scope compile. Beside the "broader scope" warning for maven this breaks one of my plugins which collects dependencies for runtime. I know that adding an exclusion to the dependency will fix this for me, but I find that annoying :-) Could the poms for those artifacts be replaced at ibiblio? Best regards, Ørjan -- Ørjan Austvold - Senior Software Architect www.colibria.com - putting the presence into messaging --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]