Yoav Shapira wrote:
Hola,
I think that the commons-logging Maven POM
(http://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk/pom.xml
in SVN) should specify scope="provided" for its Servlet API
dependency. That helps users by not including the Servlet API in
packaged artifacts, such as WARs, that use commons-logging.
Is there a reason why the default scope ("compile") is used instead?
I don't think so.
The provided scope, as described at
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html,
is designed exactly for this use case.
BTW, I noticed the new optional=true parameter that's in the POM on
SVN trunk (see above URL), but not yet in the Maven repositories
(ftp://ibiblio.org/pub/packages/maven2/commons-logging/commons-logging/1.1/commons-logging-1.1.pom).
That's a good step, but it's not sufficient for this case and does
not provide the same functionality as add scope="provided."
Thanks,
Yoav
I'll play around with different scopes and see what I can come up with,
but my initial feeling is that your suggestion is correct.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
