d just give a try to rerun it...
Kind regards
Karl Heinz Marbaise
On 21/03/18 23:02, Henrik Eriksson wrote:
Hello,
Running mvn dependency:analyze fails with the follwing exception:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze
(default-cli) on p
ns
> maven-dependency-plugin
>
>
> org.ow2.asm
> asm
> 6.1
>
>
>
>
> and just give a try to rerun it...
>
> Kind regards
> Karl Heinz Marbaise
>
>
> On 21/03/18 23:02, Henrik Eriksson wrote:
>
>> Hello,
&g
Marbaise
On 21/03/18 23:02, Henrik Eriksson wrote:
Hello,
Running mvn dependency:analyze fails with the follwing exception:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze
(default-cli) on project utils: Execution default-cli of goal
Hello,
Running mvn dependency:analyze fails with the follwing exception:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze
(default-cli) on project utils: Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze
k/reference/optimizing-sect-dependency-
> plugin.html <http://books.sonatype.com/mvnex-book/reference/
> optimizing-sect-dependency-plugin.html>
>
> "A good rule of thumb in Maven is to always declare explicit dependencies
> for classes referenced in your code.”
>
> From time
t; for classes referenced in your code.”
>
> From time to time I run dependency:analyze -DignoreNonCompile=true
> -DoutputXML=true
>
> > On 18 Jan 2018, at 07:31, Debraj Manna <subharaj.ma...@gmail.com> wrote:
> >
> > Cross-posting from stackoverflow
> > <
n your code.”
From time to time I run dependency:analyze -DignoreNonCompile=true
-DoutputXML=true
> On 18 Jan 2018, at 07:31, Debraj Manna <subharaj.ma...@gmail.com> wrote:
>
> Cross-posting from stackoverflow
> <https://stackoverflow.com/questions/48315863/how-does-mvn-dependen
Cross-posting from stackoverflow
<https://stackoverflow.com/questions/48315863/how-does-mvn-dependencyanalyze-work>
Can someone let me know how does mvn dependency:analyze work ? An output of mvn
dependency:analyze in one of my project shows
[WARNING] Used undeclared dependencies found:[W
the Java code. The
> dependency is declared in POM but comes also as a transitive dependency.
>
> When running 'dependency:analyze' it is marked as 'unused declared'. When
> I remove the dependency from the POM, and run
> 'dependency:analyze' again it is marked as 'used und
Hi!
Maybe I was too unclear about the specific problem.
I've got a project that has org.slf4j:slf4j-api:1.7.12 as dependency as it uses
the Logger in the Java code. The
dependency is declared in POM but comes also as a transitive dependency.
When running 'dependency:analyze' it is marked
Maybe because
a) your project uses dependencies which were never declared explicitly
in any of your POMs and
b) at least some of your modules have dependencies declared which are
not actually used in your code?
What do you think?
--
Alexander Kriegisch
https://scrum-master.de
Hi!
When I run 'mvn dependency:analyse' on my project several dependencies get
mentioned in the 'Used undeclared
dependencies' as well as in the 'Unused declared dependencies' section. Any
idea why?
Best regards
Kristof Meixner
Hello,
you see this a lot with runtime dependencies (which should probably be
ignored during analyze anyway), so I mostly just ignore these in the
output. It would be a cool thing, if you could suppress warnings for gavs
directly in the analyze goal, so you see new stuff coming up more easily.
Hi,
This may fall into the “How the hell is Maven supposed to know?” category,
but one of the dependencies that dependency:analyze lists when I run it on
my WAR project is
[WARNING] Unused declared dependencies found:
…
[WARNING]
org.springframework.security:spring-security-taglibs:jar:3.1.1
, 2014 at 3:54 PM, laredotornado-3 laredotorn...@gmail.comwrote:
Hi,
This may fall into the How the hell is Maven supposed to know? category,
but one of the dependencies that dependency:analyze lists when I run it on
my WAR project is
[WARNING] Unused declared dependencies found:
...
[WARNING
This may fall into the “How the hell is Maven supposed to know?” category,
Yes, it most certainly does.
[WARNING]
org.springframework.security:spring-security-taglibs:jar:3.1.1.RELEASE:compile
...
Anyway, not sure if the plugin can be configured to detect these kind of
things, but a guy can
On Wed, Feb 12, 2014 at 08:11:29AM +1030, Barrie Treloar wrote:
[snip]
I think Maven is missing a scope, it needs to break up test into two
phases; testCompile and testRuntime instead of having one scope which
means both.
This means that the analyze code can't tell what stuff is needed for
On 13 February 2014 00:20, Mark H. Wood mw...@iupui.edu wrote:
On Wed, Feb 12, 2014 at 08:11:29AM +1030, Barrie Treloar wrote:
[snip]
I think Maven is missing a scope, it needs to break up test into two
phases; testCompile and testRuntime instead of having one scope which
means both.
[del]
Hi,
I’m using Maven 3.1.1 on Mac 10.9.1. When I ran “mvn dependency:analyze” on
my project, I got results that included:
[WARNING] Unused declared dependencies found:
…
[WARNING]junit:junit:jar:4.11:test
So I commented out the above junit dependency in my pom
On 12 February 2014 07:41, laredotornado-3 laredotorn...@gmail.com wrote:
Hi,
I'm using Maven 3.1.1 on Mac 10.9.1. When I ran mvn dependency:analyze on
my project, I got results that included:
[WARNING] Unused declared dependencies found:
...
[WARNING
:
Hi,
I'm using Maven 3.1.1 on Mac 10.9.1. When I ran mvn
dependency:analyze on
my project, I got results that included:
[WARNING] Unused declared dependencies found:
...
[WARNING]junit:junit:jar:4.11:test
So I commented out the above junit dependency
I've a situation in which 2.5.1 of m-d-p:analyze is reporting 'unused
declared dependencies' that are not unused, in fact, removing them and
running maven 3.0.4 has the immediate and dramatic effect of making
the compile fail. Is there something I don't understand here about
what those goals are
Well, for starters this plugin analyzes the binary code and not the
source code. This means that reported unused declared dependencies
might in fact be used when compiling the source code. Here's a few
examples;
* static constants - the compiler optimizes this by replacing the
constant references
Hi,
I'm trying to analyze my dependencies, but encountered Invalid signature
file digest for Manifest main attributes issue.
I know it should be caused by signed jar is changed.
But you know there are lot of dependency jars there. Is there a tool to
identify which signed jar is changed?
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
From: yunfeng.w...@ebay.com
To: users@maven.apache.org
Subject: mvn dependency:analyze failed:Invalid signature
But you know there are lot of dependency jars there. Is there a tool to
identify which signed jar is changed?
Did you try adding -X for debug ouput?
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
Subject: RE: mvn dependency:analyze failed:Invalid signature file digest for
Manifest main attributes
the manifest.mf contains a MD5-Digest which looks like
Manifest-Version: 1.0
Name: bibparse-1.04/META-INF/MANIFEST.MF
Digest-Algorithms: SHA MD5
SHA-Digest: +ZeuKiF1Qrq/ym6omfGMSD5tel0=
MD5-Digest
BuildPluginManager.java:101)
... 20 more
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: 2012年10月17日 12:00
To: Maven Users List
Subject: Re: mvn dependency:analyze failed:Invalid signature file digest for
Manifest main attributes
But you know there are lot
the
jar actually works is another question).
I did a dependency:analyze, and got the following result:
[INFO] [dependency:analyze]
[WARNING] Unused declared dependencies found:
[WARNING]com.wutka:jox:jar:1.16:compile
[WARNING]junit:junit:jar:3.8.1:test
[INFO
simpler.
I've finally found all of my dependencies, added them into the
pom.xml, and got everything to compile and build the jar. (whether the
jar actually works is another question).
I did a dependency:analyze, and got the following result:
[INFO] [dependency:analyze]
[WARNING] Unused
for.
Cheers,
Brett
2008/9/16 Barry Kaplan grou...@memelet.com:
We have setup some poms only for the purpose of declaring dependencies (eg,
unit-test which depends junit, hamcrest, mockito, etc). Dependent projects
declare the dependency using typepom/type.
When I perform dependency:analyze
the dependency using typepom/type.
When I perform dependency:analyze-only on a project that depends on this pom
unit-test is marked as Unused declared dependencies found.
Is there a way for maven to not get confused in this case?
--
View this message in context:
http://www.nabble.com
I have been using the dependency:analyze successfully and I find it
works the way I expect (especially when migrating older code to Maven).
That said, there are a couple of things to take into consideration:
- Analysis is based on compiled .class files, so sometimes, a
compile-time
Hi,
I was recommended to use dependency:analyze by this list -
It's nice, but doesn't really work imho -
Many dependencies that are def. required at runtime, it interprets as not
required - while others that are not required imho - it says the project would
need them.
Any ideas why
I have been using the dependency:analyze successfully and I find it
works the way I expect (especially when migrating older code to Maven).
That said, there are a couple of things to take into consideration:
- Analysis is based on compiled .class files, so sometimes, a
compile-time dependency
to mvn2
b) I neither like a requirement to have to touch (botch) an otherwise perfectly
working application just to make it's deployment work
Any ideas / alternatives on this?
p.s.: When I created class files from my jsps - do I have to adjust
configuration so that dependency:analyze also
-mappings generated by the plugin)
Any ideas / alternatives on this?
p.s.: When I created class files from my jsps - do I have to adjust
configuration so that dependency:analyze also analyzes those? Maybe you got
some example?
By default, the .class files it generates will be included
users@maven.apache.org
Sent: Saturday, March 01, 2008 8:24 PM
Subject: Re: dependency:analyze
On Sat, 2008-03-01 at 19:41 +0100, [EMAIL PROTECTED] wrote:
- For Web apps, do not forget to compile the JSPs into .class files
and
include those in the analysis to get the real picture.
Oooh
constant from my first project.
I am having issues with the dependency:analyze goal...
In all my projects, i fail the build if there is either an unused declared
dependency or an used undeclared dependency using
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
Hi!
I am trying to analyze dependencies of a quite complex Maven project.
Obviouosly there is
http://maven.apache.org/plugins/maven-dependency-plugin/index.html
But is the stuff mentioned here:
http://www.mail-archive.com/users@maven.apache.org/msg61356.html
the same?
If not, what happened
It was merged into the dependency plugin, so yes they are the same.
-Original Message-
From: Torsten Schlabach [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 25, 2007 10:29 AM
To: users@maven.apache.org
Subject: Dependency analysis: dependency:analyze and
dependency-analyzer:analyze
Ah, now I see what you mean. This does indeed look strange, especially
the wording of the message. On the other hand, it is just an INFO and
not a WARNING like the other problems found by the dependency:analyze
goal. I don't know if this behavior is intended. The message may be
even
useful
On 6/30/07, Brian E. Fox [EMAIL PROTECTED] wrote:
Ah, now I see what you mean. This does indeed look strange, especially
the wording of the message. On the other hand, it is just an INFO and
not a WARNING like the other problems found by the dependency:analyze
goal. I don't know if this behavior
On 6/29/07, Heinrich Nirschl [EMAIL PROTECTED] wrote:
On Thu, 2007-06-28 at 10:20 +0930, Barrie Treloar wrote:
When I run dependency:analyze on my module I get:
[INFO] Found Resolved Dependency / DependencyManagement mismatches:
[INFO] Ignoring Direct Dependencies.
[INFO
On Fri, 2007-06-29 at 21:26 +0930, Barrie Treloar wrote:
On 6/29/07, Heinrich Nirschl [EMAIL PROTECTED] wrote:
On Thu, 2007-06-28 at 10:20 +0930, Barrie Treloar wrote:
When I run dependency:analyze on my module I get:
[INFO] Found Resolved Dependency / DependencyManagement mismatches
by the dependency:analyze
goal. I don't know if this behavior is intended. The message may be even
useful, because there may be something wrong in the project if a certain
dependency is excluded from one module but pulled in by another. If I
exclude it once it is very likely that I don't want it in my
On Sat, 2007-06-30 at 11:12 +0930, Barrie Treloar wrote:
I'm excluding it because EasyConf specifies a different version and I
need to override it.
Doesn't just pinning the version in dependencyManagement in such
situations work? It should not be necessary to exclude the wrong
version. However,
On Thu, 2007-06-28 at 10:20 +0930, Barrie Treloar wrote:
When I run dependency:analyze on my module I get:
[INFO] Found Resolved Dependency / DependencyManagement mismatches:
[INFO] Ignoring Direct Dependencies.
[INFO] javax.servlet:servlet-api:jar was excluded in DepMgt, but
version 2.3
When I run dependency:analyze on my module I get:
[INFO] Found Resolved Dependency / DependencyManagement mismatches:
[INFO] Ignoring Direct Dependencies.
[INFO] javax.servlet:servlet-api:jar was excluded in DepMgt, but
version 2.3 has been found in the dependency tree.
mvn site's Dependency
Hi,
How can I get the dependency:analyze goal to include the class files
that result from the compilation of the JSPs in the actual analysis?
Is there a configuration parameter to indicate additional target
directories to look into? Am I missing something?
Thanks in advance for sharing your
50 matches
Mail list logo
