I recently emailed about build avoidance issues with the generated framing code under common. The way it's done means that it builds every single time through, and does nothing at all to try to avoid the build if the spec file hasn't changed.

Rajith and I have now both independently run into more problems with this code: it won't work under Eclipse. The code is generated into directory names that contain spec version numbers (e.g., org/apache/ qpid/framing_8_0), but the actual code itself is declared to reside in the org.apache.qpid.framing package. This is clearly a no-no, and Eclipse refuses to build it.

So, anybody have an idea as to when we'll start using the new code generation approach? The code seems to have existed for weeks now, but to the best of my knowledge, nobody's stated any intent regarding making it part of the normal trunk build.

Also, will this new code address the build avoidance issues and the Eclipse issues?

I need to know, because I don't want to go off and fix issues with the current stuff if it's all about to be replaced. We have several people who want to use Eclipse for Qpid work, and they're currently blocked by this.

--steve

Reply via email to