tag:blogger.com,1999:blog-6771653874686998211.post8702547010510383019..comments2023-05-10T11:10:29.026+02:00Comments on SoftwareSwirl: The wacky world of compiling JavaMichael Haggertyhttp://www.blogger.com/profile/00332393822754558070noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6771653874686998211.post-33019614436727021702011-05-11T13:29:07.360+02:002011-05-11T13:29:07.360+02:00You say: "It is not reasonable to rely on an ...You say: "It is not reasonable to rely on an IDE for building code to be deployed. Among other things, an IDE is hard to automate, and one would need to ensure that developers are all using exactly the same version of the IDE. Therefore, using the Eclipse IDE for deployment builds is not an alternative."<br /><br />I don't believe this is true. The eclipse IDE and the eclipse.org projects are self-hosting. The Eclipse platform and its downstream products are built headlessly using Eclipse itself with Hudson CI. <br /><br />It's certainly possible (and reasonable) to build projects headlessly using the same environment that the developers work in day-to-day.<br /><br />See also:<br />https://hudson.eclipse.org/hudson/<br />http://www.eclipse.org/articles/Article-PDE-Automation/automation.htmlJamesBhttps://www.blogger.com/profile/16881154916454107186noreply@blogger.com