Colin Sampaleanu wrote:
Well you may be making the distinction between scopes and profiles,
but for some cases it seems to me to be a rather arbitrary difference,
and Ivy's configurations at least can to a decent extent be used for
both.
I'm not sure about that - I think we've got both sc
Brett Porter wrote:
Colin Sampaleanu wrote:
There are some creative ways to get flexible and less verbose with
scopes. In Ivy for example, scopes can inherit from each other, first
of all. Secondly, when declaring configs (scopes) of dependencies
that you need, and declaring configs (scopes)
Colin Sampaleanu wrote:
There are some creative ways to get flexible and less verbose with
scopes. In Ivy for example, scopes can inherit from each other, first
of all. Secondly, when declaring configs (scopes) of dependencies that
you need, and declaring configs (scopes) that you expose, you
Colin Sampaleanu wrote:
I will say I don't agree with your statement in one of those messages
that in a container deployment, the fact that the container APIs are
provided by the container doesn't mean the code still doesn't have a
dependency on the servlet apis (and presumably still needs to
Brett Porter wrote:
Colin Sampaleanu wrote:
Thanks Brett,
These days I don't normally track the discussion on a daily basis on
the dev or user lists, so had not see any, in a cursory look.
Filtering on 'scope' in the subject I've found "A dependency with
compile scope in pom.xml still adds
I found some of the discussion in "Re: [jira] Commented: (MNG-415) allow
exclusion of certain depend encies from inclusion in an archive". Some
interesting stuff. I will say I don't agree with your statement in one
of those messages that in a container deployment, the fact that the
container AP
Colin Sampaleanu wrote:
Thanks Brett,
These days I don't normally track the discussion on a daily basis on
the dev or user lists, so had not see any, in a cursory look.
Filtering on 'scope' in the subject I've found "A dependency with
compile scope in pom.xml still adds jar to war lib in m2?
Thanks Brett,
These days I don't normally track the discussion on a daily basis on the
dev or user lists, so had not see any, in a cursory look. Filtering on
'scope' in the subject I've found "A dependency with compile scope in
pom.xml still adds jar to war lib in m2?", but that's not really a
Colin,
This has been discussed recently on both the user and dev lists, and
there are pros and cons to both approaches.
This is the case of servlet API/J2EE, and perhaps some libraries
provided by the final JDK but not compiling JDK. It's not that they are
compile-only - it's that they -may-
I was taking a look at the description of the Scope support in Maven 2:
http://maven.apache.org/maven2/dependencies.html
but am confused as to hove Maven 2 handles dependencies which are needed
only for compiling, but _not_ at runtime.
Consider the example of the servlet apis (or really any ot
10 matches
Mail list logo
