You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Steinar Bang <sb...@dod.no> on 2007/03/07 12:15:55 UTC
Status of maven dependency analysis mojo?
Does anyone know the current status for the dependency analysis mojo?
Specifically: is there still work going on it, or is it dead? Where
can I get it from? How do I run it? (ie. what goals do I give on the
command line?)
I googled today for something to help me clean up the dependencies of
our hierarchical maven project, and I ran into the
maven-dependency-analyzer:
http://jira.codehaus.org/browse/MNG-2676
which seems to be exactly what I was looking for.
However, the SVN URLs in the above bug report don't work. I was able
to check out the maven-dependency-analyzer by inserting a "/trunk"
after "/shared".
But I wasn't able to find the maven-dependency-analyzer-plugin.
So any information about the status of this tool, or of alternative
tools, is welcome.
Thanx!
- Steinar
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Status of maven dependency analysis mojo?
Posted by Steinar Bang <sb...@dod.no>.
>>>>> "Mark Hobson" <ma...@gmail.com>:
> That exception would occur if the build directory didn't exist or is
> not a directory - in your case:
> /media/sda8/someuser/p4/depot/someproject/MAIN/com.somecompany.someproject/target
> Does that directory exist?
Yes. It contains a file called mvn-eclipse-cache.properties
(presumably generated by "mvn eclipse:eclipse"...?).
com.somecompany.someproject/pom.xml is the top POM for the
hierarchical project, and has <packaging>pom</packaging>.
> What's your environment?
Ubuntu Dapper Drake (on Intel arch)
maven 2.0.4
Sun Java 2 SDK 1.5.0_06-b05
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Status of maven dependency analysis mojo?
Posted by Mark Hobson <ma...@gmail.com>.
That exception would occur if the build directory didn't exist or is
not a directory - in your case:
/media/sda8/someuser/p4/depot/someproject/MAIN/com.somecompany.someproject/target
Does that directory exist? What's your environment?
Cheers,
Mark
On 08/03/07, Steinar Bang <sb...@dod.no> wrote:
> "mvn dependency:analyze" seemed like a good guess. And that goal
> actually seems to be there.
>
> Unfortunately I'm getting a "FATAL ERROR" (see stack trace below).
> Could it be because we're using a flattened directory structure on our
> hierarchical maven project?
>
> (the flattened structure is more eclipse friendly. That's why we're
> using it)
>
>
> /media/sda8/someuser/p4/depot/someproject/MAIN/com.somecompany.someproject$ mvn dependency:analyze
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [snip! ...]
> [INFO] Searching repository for plugin with prefix: 'dependency'.
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Somecompany Someproject
> [INFO] task-segment: [dependency:analyze]
> [INFO] ----------------------------------------------------------------------------
> [INFO] Preparing dependency:analyze
> [INFO] No goals needed for project - skipping
> [INFO] [dependency:analyze]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Cannot accept visitor on URL: file:/media/sda8/someuser/p4/depot/someproject/MAIN/com.somecompany.someproject/target
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.IllegalArgumentException: Cannot accept visitor on URL: file:/media/sda8/someuser/p4/depot/someproject/MAIN/com.somecompany.someproject/target
> at org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept(ClassFileVisitorUtils.java:74)
> at org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze(ASMDependencyAnalyzer.java:49)
> at org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses(DefaultProjectDependencyAnalyzer.java:141)
> at org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze(DefaultProjectDependencyAnalyzer.java:72)
> at org.apache.maven.plugin.dependency.AnalyzeMojo.execute(AnalyzeMojo.java:74)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 5 seconds
> [INFO] Finished at: Thu Mar 08 09:53:35 CET 2007
> [INFO] Final Memory: 12M/21M
> [INFO] ------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Status of maven dependency analysis mojo?
Posted by Steinar Bang <sb...@dod.no>.
>>>>> Steinar Bang <sb...@dod.no>:
>>>>> "Brian E. Fox" <br...@reply.infinity.nu>:
>> The merged plugin is sitting here:
>> /maven/sandbox/trunk/plugins/maven-dependency-plugin/pom.xml
>> Once alpha-2 is released, this will be merged into the dependency plugin
>> trunk.
> Ok. Thanx!
> What goals do I run to generate the reports? None of the regular
> dependency plugin goals seems to fit...?
"mvn dependency:analyze" seemed like a good guess. And that goal
actually seems to be there.
Unfortunately I'm getting a "FATAL ERROR" (see stack trace below).
Could it be because we're using a flattened directory structure on our
hierarchical maven project?
(the flattened structure is more eclipse friendly. That's why we're
using it)
/media/sda8/someuser/p4/depot/someproject/MAIN/com.somecompany.someproject$ mvn dependency:analyze
[INFO] Scanning for projects...
[INFO] Reactor build order:
[snip! ...]
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO] ----------------------------------------------------------------------------
[INFO] Building Somecompany Someproject
[INFO] task-segment: [dependency:analyze]
[INFO] ----------------------------------------------------------------------------
[INFO] Preparing dependency:analyze
[INFO] No goals needed for project - skipping
[INFO] [dependency:analyze]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Cannot accept visitor on URL: file:/media/sda8/someuser/p4/depot/someproject/MAIN/com.somecompany.someproject/target
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.IllegalArgumentException: Cannot accept visitor on URL: file:/media/sda8/someuser/p4/depot/someproject/MAIN/com.somecompany.someproject/target
at org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept(ClassFileVisitorUtils.java:74)
at org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze(ASMDependencyAnalyzer.java:49)
at org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses(DefaultProjectDependencyAnalyzer.java:141)
at org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze(DefaultProjectDependencyAnalyzer.java:72)
at org.apache.maven.plugin.dependency.AnalyzeMojo.execute(AnalyzeMojo.java:74)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5 seconds
[INFO] Finished at: Thu Mar 08 09:53:35 CET 2007
[INFO] Final Memory: 12M/21M
[INFO] ------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Status of maven dependency analysis mojo?
Posted by Steinar Bang <sb...@dod.no>.
>>>>> "Brian E. Fox" <br...@reply.infinity.nu>:
> The merged plugin is sitting here:
> /maven/sandbox/trunk/plugins/maven-dependency-plugin/pom.xml
> Once alpha-2 is released, this will be merged into the dependency plugin
> trunk.
Ok. Thanx!
What goals do I run to generate the reports? None of the regular
dependency plugin goals seems to fit...?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Status of maven dependency analysis mojo?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
The merged plugin is sitting here:
/maven/sandbox/trunk/plugins/maven-dependency-plugin/pom.xml
Once alpha-2 is released, this will be merged into the dependency plugin
trunk.
-----Original Message-----
From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
Sent: Wednesday, March 07, 2007 6:32 AM
To: Maven Users List
Subject: Re: Status of maven dependency analysis mojo?
Hi Steinar,
Moved to
https://svn.apache.org/repos/asf//maven/sandbox/trunk/shared/maven-depen
dency-analyzer/
and the plugin was merged into maven-dependency-plugin
Cheers,
Vincent
2007/3/7, Steinar Bang <sb...@dod.no>:
> Does anyone know the current status for the dependency analysis mojo?
> Specifically: is there still work going on it, or is it dead? Where
> can I get it from? How do I run it? (ie. what goals do I give on the
> command line?)
>
> I googled today for something to help me clean up the dependencies of
> our hierarchical maven project, and I ran into the
> maven-dependency-analyzer:
> http://jira.codehaus.org/browse/MNG-2676
> which seems to be exactly what I was looking for.
>
> However, the SVN URLs in the above bug report don't work. I was able
> to check out the maven-dependency-analyzer by inserting a "/trunk"
> after "/shared".
>
> But I wasn't able to find the maven-dependency-analyzer-plugin.
>
> So any information about the status of this tool, or of alternative
> tools, is welcome.
>
> Thanx!
>
>
> - Steinar
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Status of maven dependency analysis mojo?
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Steinar,
Moved to https://svn.apache.org/repos/asf//maven/sandbox/trunk/shared/maven-dependency-analyzer/
and the plugin was merged into maven-dependency-plugin
Cheers,
Vincent
2007/3/7, Steinar Bang <sb...@dod.no>:
> Does anyone know the current status for the dependency analysis mojo?
> Specifically: is there still work going on it, or is it dead? Where
> can I get it from? How do I run it? (ie. what goals do I give on the
> command line?)
>
> I googled today for something to help me clean up the dependencies of
> our hierarchical maven project, and I ran into the
> maven-dependency-analyzer:
> http://jira.codehaus.org/browse/MNG-2676
> which seems to be exactly what I was looking for.
>
> However, the SVN URLs in the above bug report don't work. I was able
> to check out the maven-dependency-analyzer by inserting a "/trunk"
> after "/shared".
>
> But I wasn't able to find the maven-dependency-analyzer-plugin.
>
> So any information about the status of this tool, or of alternative
> tools, is welcome.
>
> Thanx!
>
>
> - Steinar
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org