It is easy to miss the presence of the project-specific project.xml file when
building an add-on, and this frequently leads to problems with bad builds.
When project.xml is present and a build target is invoked via build.xml, an
error should be thrown indicating that project.xml should be used. At the very
least a warning should be output.
Original issue reported on code.google.com by will.abson on 10 Jan 2013 at 2:00
Original issue reported on code.google.com by
will.abson
on 10 Jan 2013 at 2:00