Missing feature project fails the build without explanation
Brought to you by:
raner
Menu
▾
▴
#1 Missing feature project fails the build without explanation
The ebuilder plug-in assumes that the workspace contains a feature project that is to be exported to a deployable update site. If there is no feature project, the build will just fail with the standard error code of 191 but will give no indication what actually went wrong.
ebuilder should at least issue a meaningful error message, or alternatively just export individual deployable plug-ins instead of a feature.
This problem usually manifests itself in the log like this:
[exec] [ebuilder] Building feature and update site...
[exec] [ebuilder] Feature project: com.intuit.eclipse.xtext.thx.feature
[exec] [ebuilder] BUILD FAILED
Only if the feature project was actually found, ebuilder will list the destination folder and build ID:
[exec] [ebuilder] Building feature and update site...
[exec] [ebuilder] Feature project: com.intuit.thx.feature
[exec] [ebuilder] Destination folder is c:\users\hudson\workspace\iHelp\updates
[exec] [ebuilder] Build ID is r0019
[exec] [ebuilder] Exporting feature...
[exec] [ebuilder] Waiting for job: org.eclipse.pde.internal.core.exports.FeatureExportOperation
[exec] [ebuilder] Finished job: org.eclipse.pde.internal.core.exports.FeatureExportOperation
[exec] [ebuilder] Update site created.
[exec] [ebuilder] BUILD SUCCESSFUL
If you don't see the destination folder or build ID this indicates that there is a problem with the feature project (misspelled, missing from workspace, etc.)