Re: [m2e-users] On handling of generated code

[Vegard Havdal <vegardh@xxxxxxxxxx>]

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