[
http://jira.codehaus.org/browse/MNG-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SebbASF closed MNG-4097.
------------------------
Resolution: Fixed
My bad, sorry.
I misunderstood "provided" as documented in
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
{quote}
provided
This is much like compile, but indicates you expect the JDK or a container to
provide the dependency at runtime. For example, when building a web application
for the Java Enterprise Edition, you would set the dependency on the Servlet
API and related Java EE APIs to scope provided because the web container
provides those classes. This scope is only available on the compilation and
test classpath, and is not transitive.
{quote}
to mean that the user had to provide the dependency, whereas in fact Maven uses
the repository to find it.
> Dependency scope needs to include compile-only
> ----------------------------------------------
>
> Key: MNG-4097
> URL: http://jira.codehaus.org/browse/MNG-4097
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Reporter: SebbASF
>
> It seems there is currently no proper way to express compile-only
> dependencies, e.g. annotation jars or API-only jars.
> Using scope "compile" with optional "true" partially solves this, but the jar
> still ends up polluting other phases, e.g. dependency lists and OSGI
> manifests.
--
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
