[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] On handling of generated code
|
In 1.0, You can suppress the error marker by adding <ignore/> mapping in
one of your parent poms.
In 1.1, you can embed <execute/> mapping with runOnIncremental=false and
runOnConfiguration=true in the plugin jar. This is expected to get rid
of the error marker, add java project source folder(s) and run code
generation of full workspace build. You still need to refresh workspace
manually after full workspace build, unless the mojo uses BuildContext.
Alternatively, map the mojo to <ignore/> in the plugin jar, and manage
build classpath and code generation manually. m2e 1.1 preserves custom
classpath entries, so you won't need to manually reconfigure classpath
after each project configuration update.
--
Regards,
Igor
On 11-10-21 1:06 PM, Vegard Havdal wrote:
Den 21. okt. 2011 kl. 17.11 skrev Igor Fedorenko:
Been doing that for years, it works well for the codegen plugins I am
using.
This maybe okay for an internal plugin used by a small closed group of
developers working together, but is bad for opensource maven plugins
with distributed and disconnected user base.
Yes I understand this, but what if you have pretty simple codegen plugins that have been around a while, and almost always either work or throw. This is the case for us, pretty big, closed org. Some use Eclipse, some not. We have been happy to execute generate-sources as part of project import, via Run As or even outside of Eclipse.
What I am trying to achieve is:
1) Get rid of the red marker in pom.xml (lifecycle config in the plugin fixes this, so thanks again)
end less important
2) Make Update project configuration add the source folder to the Eclipse build path
Actually, if there were a way in Eclipse to mute the red marker, that would be enough for us I think.
Vegard
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
