Bug 159380 [regression]Not find DataEngineContextExt class cause all engine/dte smoke testing fail
Description Not find DataEngineContextExt class cause all engine/dte smoke testing fail Steps to reproduce: Run Engine/DTE smoke testing framework Expected result&#65306; Outputs are correct. Actaul result: All outputs are 0kb with Exception: Error happened while running the report. java.lang.NoClassDefFoundError: org/eclipse/birt/data/engine/impl/DataEngineContextExt at org.eclipse.birt.data.engine.api.DataEngineContext.setTmpdir(DataEngineContext.java:374) at org.eclipse.birt.report.engine.data.dte.DteDataEngine.<init>(DteDataEngine.java:71) at org.eclipse.birt.report.engine.data.DataEngineFactory.createDataEngine(DataEngineFactory.java:94) at org.eclipse.birt.report.engine.executor.ExecutionContext.getDataEngine(ExecutionContext.java:694) at org.eclipse.birt.report.engine.executor.ReportExecutor.execute(ReportExecutor.java:99) at org.eclipse.birt.report.engine.internal.executor.l18n.LocalizedReportExecutor.execute(LocalizedReportExecutor.java:38) at org.eclipse.birt.report.engine.layout.html.HTMLReportLayoutEngine.layout(HTMLReportLayoutEngine.java:68) at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:207) at org.eclipse.birt.report.engine.api.ReportRunner.runAndRenderReport(ReportRunner.java:237) at org.eclipse.birt.report.engine.api.ReportRunner.execute(ReportRunner.java:162) at org.eclipse.birt.report.engine.api.ReportRunner.main(ReportRunner.java:118)
data/org.eclipse.birt.data/src/org/eclipse/birt/data/engine/impl/DataEngineImpl.java
/**
	 * Returns the runtime defn of a data source. If data source is not found,
	 * returns null.
	 */
	DataSourceRuntime getDataSourceRuntime( String name )
	{
		return (DataSourceRuntime) dataSources.get( name );
	}
	/**
	 * Returns the design of a data set. If data set is not found, returns null.
	 */
	IBaseDataSetDesign getDataSetDesign( String name )
	{
		return (IBaseDataSetDesign) dataSetDesigns.get( name );
	}
	/**
	 * Verifies the elements of a report query spec
	 * and provides a hint to the query to prepare and optimize 
	 * an execution plan.
	 * The given querySpec could be a ReportQueryDefn 
	 * (raw data transform) spec generated by the factory 
	 * based on static definition found in a report design.
	 * <p> 
	 * This report query spec could be further refined by FPE 
	 * during engine execution after having resolved any related
	 * runtime condition.  This is probably not in BIRT Release 1.
	 * For example, a nested report item might not be rendered based
	 * on a runtime condition.  Thus its associated data expression
	 * could be removed from the report query defn given to