You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason Dillon <ja...@planet57.com> on 2007/04/04 02:09:14 UTC

dependency:analyze needs target/ ?

Why does dependency:analyze need target dirs?  This barfs all over  
the place for modules of type pom... making this goal unusable.

<snip>
[INFO] Preparing dependency:analyze
[INFO] [enforcer:enforce {execution: default}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [dependency:analyze]
[INFO]  
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]  
------------------------------------------------------------------------
[INFO] Cannot accept visitor on URL: file:/Users/jason/ws/geronimo/ 
tck-2.0/target
[INFO]  
------------------------------------------------------------------------
[INFO] Trace
java.lang.IllegalArgumentException: Cannot accept visitor on URL:  
file:/Users/jason/ws/geronimo/tck-2.0/target
         at  
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
(ClassFileVisitorUtils.java:74)
         at  
org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.an 
alyze(ASMDependencyAnalyzer.java:49)
         at  
org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnal 
yzer.buildDependencyClasses(DefaultProjectDependencyAnalyzer.java:141)
         at  
org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnal 
yzer.analyze(DefaultProjectDependencyAnalyzer.java:72)
         at  
org.apache.maven.plugin.dependency.AnalyzeMojo.checkDependencies 
(AnalyzeMojo.java:115)
         at org.apache.maven.plugin.dependency.AnalyzeMojo.execute 
(AnalyzeMojo.java:90)
         at org.apache.maven.plugin.DefaultPluginManager.executeMojo 
(DefaultPluginManager.java:443)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
(DefaultLifecycleExecutor.java:539)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa 
l(DefaultLifecycleExecutor.java:493)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal 
(DefaultLifecycleExecutor.java:463)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle 
Failures(DefaultLifecycleExecutor.java:311)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( 
DefaultLifecycleExecutor.java:278)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute 
(DefaultLifecycleExecutor.java:143)
         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 
334)
         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
         at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
         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: 27 seconds
[INFO] Finished at: Tue Apr 03 17:07:01 PDT 2007
[INFO] Final Memory: 17M/32M
[INFO]  
------------------------------------------------------------------------
</snip>

--jason

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: dependency:analyze needs target/ ?

Posted by Jason Dillon <ja...@planet57.com>.
On Apr 4, 2007, at 2:06 AM, Mark Hobson wrote:
> On 04/04/07, Jason Dillon <ja...@planet57.com> wrote:
>> Hey, I was using 2.0-alpha-3 before, but after changing to 2.0-
>> alpha-4 I still get similar problems.  Not every module that isn't
>> type "pom" creates a target directory.  The plugin should really skip
>> any scanning of stuff under target if that directory does not exist.
>
> Sure, I have some local changes to maven-dependency-analyzer to make
> it more passive for these situations, I'll aim to submit them shortly.
> I assume I can reproduce your problem by running dependency:analyze
> at the top-level of Germino?

Yup, that will do it :-)

--jason


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: dependency:analyze needs target/ ?

Posted by Mark Hobson <ma...@gmail.com>.
On 04/04/07, Jason Dillon <ja...@planet57.com> wrote:
> Hey, I was using 2.0-alpha-3 before, but after changing to 2.0-
> alpha-4 I still get similar problems.  Not every module that isn't
> type "pom" creates a target directory.  The plugin should really skip
> any scanning of stuff under target if that directory does not exist.

Sure, I have some local changes to maven-dependency-analyzer to make
it more passive for these situations, I'll aim to submit them shortly.
 I assume I can reproduce your problem by running dependency:analyze
at the top-level of Germino?

Cheers,

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: dependency:analyze needs target/ ?

Posted by Jason Dillon <ja...@planet57.com>.
On Apr 4, 2007, at 1:34 AM, Mark Hobson wrote:
> On 04/04/07, Jason Dillon <ja...@planet57.com> wrote:
>> Why does dependency:analyze need target dirs?  This barfs all over
>> the place for modules of type pom... making this goal unusable.
>
> It requires target dirs because it processes the class files.  Your
> problem looks like MDEP-73, try maven-dependency-plugin 2.0-alpha-4
> and see that fixes it.

Hey, I was using 2.0-alpha-3 before, but after changing to 2.0- 
alpha-4 I still get similar problems.  Not every module that isn't  
type "pom" creates a target directory.  The plugin should really skip  
any scanning of stuff under target if that directory does not exist.

--jason



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: dependency:analyze needs target/ ?

Posted by Mark Hobson <ma...@gmail.com>.
On 04/04/07, Jason Dillon <ja...@planet57.com> wrote:
> Why does dependency:analyze need target dirs?  This barfs all over
> the place for modules of type pom... making this goal unusable.

It requires target dirs because it processes the class files.  Your
problem looks like MDEP-73, try maven-dependency-plugin 2.0-alpha-4
and see that fixes it.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org