hi robert,
what is the plugin that creates files and puts them into the
generated-sources/annotations directory
as from how i understand it works, the plugin should on execution
dynamically register that new extra directory into the list of source
directories that the maven-compiler-plugin will look at.
as if i manually create
${project.build.directory}/generated-sources/annotations i would not
expect maven-compiler-plugin to know about it, and so compile files
from that directory. if that is how maven-compiler-plugin works then
it would need to be preloaded with all possible generated source
directories of all plugins that generate source.
do you explicit state all plugins your using within your pom? could
the source generation plugin have been updated???
John
On 22 October 2016 at 22:17, Robert Patrick <robert.patr...@oracle.com> wrote:
> Periodically, I update the versions of the Maven plugins for my projects.
> Today was one of those days. What I found is that the maven-compiler-plugin
> 3.5.1's compile goal no longer seems to not be including the
> ${project.build.directory}/generated-sources/annotations
>
> directory in the compile.
>
>
>
> My project generates a Java file in the process-resources phase and puts the
> file in this directory. Other files in the normal src/main/java location
> include/depend on this generated file. When I run my build with 3.5, it
> works perfectly. When I run the exact same build with 3.5.1, it fails.
>
>
>
> I logged into my Apache Jira account but the compiler plugin project does not
> seem to want to let me create an issue for this. Is there some sort of
> special permission required to create an issue on the maven-compiler-plugin?
>
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
