Okay, I see.
The question is then, why it complains about 'unused' runtime
dependencies as it just cannot know?
Am 04.05.2010 21:26, schrieb Brian Fox:
It can't if they are truely runtime only. The analyze goal does static
bytecode analysis of your code and all of your dependencies. It then
compares the list to figure out what's present but not used etc.
On Tue, May 4, 2010 at 2:53 PM, Christoph Kutzinski<ku...@gmx.de> wrote:
Thanks
I didn't know that this switch existed.
I'm still wondering how dependency:analyze could ever know if a runtime
dependency is used or not!?
Christoph
Am 04.05.2010 19:20, schrieb Justin Edelson:
Sorry, that wasn't clear... I should have written "these goals only look
at the classes used at compile time."
To get rid of this warning, set ignoreNonCompile to true. I'm unclear
why this isn't the default.
Justin
On 5/4/10 12:41 PM, Christoph Kutzinski wrote:
On a related note:
if it only takes compile-time dependencies into account, how does it come
that it warns about unused runtime dependencies in my project:
[WARNING] Unused declared dependencies found:
[WARNING]
org.hibernate:hibernate-commons-annotations:jar:3.3.0.ga:runtime
Christoph
-------- Original-Nachricht --------
Datum: Tue, 04 May 2010 12:12:37 -0400
Von: Justin Edelson<justinedel...@gmail.com>
An: Maven Users List<users@maven.apache.org>
Betreff: Re: Does maven-dependency-plugin consider Spring bean
definitions?
If you're referring to dependency:analyze (and its kin), the answer is
no - these goals only look at the compile-time dependencies; they do not
execute your code. So any dependency accessed via reflection (which
would include Spring) would be missed.
Justin
On 5/4/10 11:43 AM, vanyatka wrote:
Hey,
Trying to organize project dependencies, however not sure if
maven-dependency-plugin will take into account beans that are defined
in
spring application context, but might not be referenced from source
code.
The example can be Quartz Scheduler, which is defined in spring context
and
runs beans by schedule. Such dependencies still have to included in pom
(in
order to be packaged).
I'll try to check and post answer here, basically created this thread
so
that anyone else can find a quick answer )
-Ivan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
