Community
Participate
Working Groups
In a build during the week, there was once a compile problem, but the build and unit tests kept running ... but, they are supposed to stop. I think behavior changed in latest pde builder/compiler. We have been simply detecting a file created be pde build (or, jdt?) named "compilation.problem" in a plugins complile log folder. That's either changed names, or no longer created. We may have to scan all the @dot.xml files specifically for "error" attributes in the compile log; similar to <problems errors="1" problems="1" warnings="0"> <problem categoryID="50" charEnd="22579" charStart="22566" id="UndefinedMethod" line="957" problemID="67108964" severity="ERROR"> <message value="The method getTextContent() is undefined for the type Node"/> <source_context sourceEnd="33" sourceStart="20" value="String text = child.getTextContent();"/> <arguments> <argument value="org.w3c.dom.Node"/> <argument value="getTextContent"/> <argument value=""/> </arguments> </problem> </problems>
I've captured another data point. New hypothesis is the "compilation.problem" file may only be created for bundles that do not have classes in jars. Latest failure to catch a compile problem was in M build (old compiler, old pde builder) in the org.eclipse.wst.server.ui.tests bundle. I noticed it does not have @dot.xml files, but instead logs compiler output in the old-fashioned temp.folder/tests.jar.bin.xml (presumably, since it is creating a "test.jar" instead of putting classes at the root of the bundle. So, if we do search for severity="ERROR" then we'd have to search xml files in temp.folder (as well, or, in addition to looking for 'compilation.problem' file). That's temp.folder is in the ${builddirectory}plugins/org.eclipse.wst.server.ui.tests
mass change back to default assignee and qa contact. I'm not saying I won't work on some :) ... but, won't be all ... so, I think defaults would be best to start over.
