|headless build issues/bugs [message #604723]
||Wed, 17 February 2010 23:10
| Siva Velusamy
Registered: July 2009
We have been using Eclipse headless builds to build our plugins for the last few months. We encountered a few issues with the PDE builds that look very much like bugs in the ant scripts.|
- We are using Eclipse 3.5.1
- We build one feature that includes about 10 plugins.
- The build script is written as a Makefile that calls into the Eclipse antRunner with the PDE build script as the argument.
- Probably the thing that makes it complex is that we use Electric Cloud's emake to call this makefile distributing some of the work.
We see 2 main problems:
1. Every so often, Eclipse compiler will fail to compile a file with the following message:
No .class file created for file ... because of an IOException
For a while we did not even catch on to this because ant does not stop at this error, nor does it return an error code back to make indicating that something was wrong. The jar files get built, but they just miss out a single .class file. We notice the issue only during testing the built product. I think this should stop the build, or there should be an option for this stop the build since this happens so often, especially during heavy network usage.
2. Once we found about the silent IOException's, we made a whole bunch of workarounds to make sure that we have a .class file for every .java file, and re-run the build if that isn't the case. Now we notice a second issue: Even if the build runs again, and succeeds the 2nd time, the .jar file created the first time is not overwritten with the updated .jar file. This just seems like a bug in the dependencies in the PDE ant script.
I don't understand the ant scripts and the whole headless build process in sufficient depth to confirm these two as real issues or offer fixes, but if someone else can confirm, I can file a bug report with these details.
Powered by FUDForum
. Page generated in 0.01652 seconds