[ http://jira.codehaus.org/browse/MEV-392?page=comments#action_65445 ]
Simon Kitching commented on MEV-392: ------------------------------------ Yeah, commons-logging is definitely a difficult beast to create a maven pom for :-) The commons-logging-api jar really should be called commons-logging-tomcat; IMO, it's not something for general use. Sorry about the name, but that's historical and can't easily be changed now. I don't see any benefits from anyone declaring a dependency on this api jar vs the complete jar (once the dependencies are marked optional); the size difference is trivial. commons-logging-adapters.jar should be the dependency for any code that will be deployed into a container that provides commons-logging.jar or commons-logging-api.jar at the container level. Yes, we know that's not terribly elegant, but blame the Java class resolution rules for that. In all other cases, commons-logging.jar is the correct dependency for projects. As Joerg notes, all dependencies should be optional [except the servlet-api dependency which probably should be *both* optional and provided :-]. Regards, Simon (a commons logging maintainer) > bad dependencies in commons-logging-1.1.pom > ------------------------------------------- > > Key: MEV-392 > URL: http://jira.codehaus.org/browse/MEV-392 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Olivier Lamy > > > Hi, > I have trouble concerning dependencies in commons-logging 1.1 > <dependency> > <groupId>javax.servlet</groupId> > <artifactId>servlet-api</artifactId> > <version>2.3</version> > </dependency> > scope must be provided > <dependency> > <groupId>avalon-framework</groupId> > <artifactId>avalon-framework</artifactId> > <version>4.1.3</version> > </dependency> > as 1.0.4 scope must be optionnal > <dependency> > <groupId>logkit</groupId> > <artifactId>logkit</artifactId> > <version>1.0.1</version> > </dependency> > as 1.0.4 scope must be optionnal -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
