[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] On handling of generated code
|
I'm guessing you're using an execute mapping? With a configurator manually refreshing the workspace and adding source directory shouldn't be necessary, if you're going to work a lot with WSDL it may be worth considering writing one:
http://wiki.eclipse.org/M2E_Extension_Development
Matthew
On 20 October 2011 08:53, Steve Cohen
<scohen@xxxxxxxxxxxxxxx> wrote:
The stuff I am using works much like other code generators. It creates a directory under target and populates it, I make that directory a source folder. I just don't want to have to keep repeating that step.
Also, there seem to be timing issues. Code generation does not take place automatically when I save changes to the wsdl. And I have to do a refresh before the eclipse compilation step sees the new generated code. How can this be overcome?
On 10/20/2011 07:47 AM, Vegard B. Havdal wrote:
On Oct 20, 2011, at 2:17 PM, Steve Cohen wrote:
the generated code directory may not exist at the end of the failed process, particularly after a clean. At this point eclipse very "helpfully" removes the generated code folder from the build path. I would rather that it left
I don't think that is the default behaviour of m2e, you should get "Build path entry missing: target/generated-sources/..." and a red question mark and a failed build.
(I am not familiar with the JBoss stuff you are using.)
Vegard
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
______________________________
_________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
