What steps will reproduce the problem? 1. Create a multi module project. 2. Configure the maven-annotation-plugin in the parent POM
What is the expected output? What do you see instead?
We get a build error because there is no source directory and no source files in the parent POM module. That's the case for every module with packaging pom it would in your view make sense to skip execution for such projects.
Please provide any additional information below.
We configure the maven-annotation-plugin in the parent POM because we want to execute it for every module.
Attached you'll find a simple patch that implements this.
Comment #1
Posted on Apr 11, 2010 by Quick Rabbitthx
i'll apply pacth asap
Comment #2
Posted on Apr 11, 2010 by Quick Rabbitpatch applied on 1.3.2 version
Comment #3
Posted on Apr 11, 2010 by Happy MonkeyAwesome, thanks a lot.
Comment #4
Posted on Oct 12, 2011 by Happy LionI don't know, have you thought about adding an ERROR message maybe? I was trying to use this plugin with a POM project for a site, where I needed to generate documentation based on source in other directories, and this "fix" just prevented me from it...
Comment #5
Posted on Oct 14, 2011 by Quick RabbitHi, thx for feedback
What do you think if i put a parameter allowing to change this behaviour (i.e. ) ?
Let me know
Comment #6
Posted on Oct 14, 2011 by Happy MonkeyI don't really care anymore because the maven-compiler plugin now supports this.
Comment #7
Posted on Oct 14, 2011 by Quick RabbitOk
however .. thx again for feedback
Status: WontFix
Labels:
Type-Defect
Priority-Medium