However, when abuild fails this log only have as much
information about the failure as the ant task provides. Currently PDE tasks
do not provide too much info. They dump it into workspace .log (Can
also be in the range of a few 10s of MB)
We typically look ath the XML Log from the reporting app,
which you also have access, and learned a few patterns. For example
when it fails in generating build scripts complaining about not finding
a plugin, the problem is one of:
plugin names have changed or inconsistent across plugin.xml/feature.xml
plugin versions have changed or inconsistent acrossplugin.xml/feature.xml
plugin is not registered in feature.xml
plugin is not in .map file
plugin is not in CVS So maybe we can include a simple
"text" about the reason for a failure and have a build Troubleshooting
Any other ideas?
At 04:55 PM 12/7/2004, you wrote:
The current build notification doesn't give us
any clue whats going wrong. Unless the results are published to the
wtp download site.
So we are forced to do local builds here to diagnose.
Can we improve this?
Thanks - Chuck
Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Phone: 919-254-1848 (T/L: 444)
Naci Dai <naci.dai@xxxxxxxxxxxxx>
Sent by: wtp-dev-admin@xxxxxxxxxxx
12/07/2004 04:47 AM
Please respond to
[wtp-dev] Failed builds
The reason for the build failures is the internet component renaming (i.e.
plugin.xml ). Please review your plugins.
plugins and probably some others have dependencies.