Closed lukaseder closed 11 years ago
I do not see the advantages. Why does XJC do that?
On the other hand if these sources are removed during the compilation then the developer can not have a peek of the generated sources if she needs that for any reason.
If there is any reason to do that and if I can find at which compilation phase to do that and how I can develop that.
I do not see the advantages. Why does XJC do that?
When you remove a type from your XSD, you don't want the generated class to be lying around. Similarly, when you remove a state from your various transitions, you probably don't want the generated class stick around either.
On the other hand if these sources are removed during the compilation then the developer can not have a peek of the generated sources if she needs that for any reason.
Yes, they can, but only the ones that are still "valid"
and if I can find at which compilation phase to do that
That might be tricky...
The trivial solution is
mvn clean install
May I assume this feature is low priority?
Yes, that's the workaround, of course. But for incremental builds it would still be a nice (agreed, low prio) feature
XJC removes sources from the target directory (typically
target/generated-sources/xjc
), if they are no longer needed / valid. I guess this should be done as well in fluflu, without requiring to callmvn clean