On 04/04/07, Jason Dillon [EMAIL PROTECTED] 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
On Apr 4, 2007, at 1:34 AM, Mark Hobson wrote:
On 04/04/07, Jason Dillon [EMAIL PROTECTED] 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.
On 04/04/07, Jason Dillon [EMAIL PROTECTED] 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
On Apr 4, 2007, at 2:06 AM, Mark Hobson wrote:
On 04/04/07, Jason Dillon [EMAIL PROTECTED] 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
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]
