What steps will reproduce the problem? 1. Running a multimodule build

What is the expected output? What do you see instead? It should work, but there occur strange errors when the plugin is executed in different modules the same time.

What version of the product are you using? On what operating system? 2.0.5-SNAPSHOT

Please provide any additional information below. Don't using fields in the pojo class or using a pojo wrapper should solve the problem.

hi

thx for feedbacks

Your report: It should work, but there occur strange errors when the plugin is executed in different modules the same time.

• Could you provide me more details?
• Do you have problems similar to Issue 32 ?

Hi,

I ran the plugin in a multimodule project. Then an error occurs reproducable.

I downloaded the code an tried the dirty solutionn described in https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html; Then it works. I think the problem ist the locking of the compiler run, but not of the mojo itself. I don't know how maven calls the plugin, but i assume the fields in the mojo are overridden during execution in different modules.

Ok

I'll apply the "dirty solution" using lock

Unfortunately this solution didn't work to fix Issue 32 but at least we solve your problem

i've deployed a 2.0.6-SNAPSHOT with suggested fix

Please, could you test it and give me feedbacks?

thx in advance