The runtime scope in my opinion make more sense since you don't need the
provided dependencies in your artifact when you deploy it.
On 12/6/05, Matthew Beermann <[EMAIL PROTECTED]> wrote:
>
> The guide here:
> http://maven.apache.org/guides/mini/guide-manifest.htmlmentions the
> option, as a co
The guide here: http://maven.apache.org/guides/mini/guide-manifest.html
mentions the option, as a configuration flag under
maven-jar-plugin. It works great - but WHICH classpath is it going to add to
the manifest? The compile scope makes the most sense to me, at least as a
default...
--M
