Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 428353

Summary:	Manifest semantic analysis should depend on the application type
Product:	[ECD] Orion	Reporter:	Maciej Bendkowski <maciej.bendkowski>
Component:	Deployment	Assignee:	Maciej Bendkowski <maciej.bendkowski>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	Szymon.Brandys
Version:	unspecified
Target Milestone:	8.0
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	428351
Bug Blocks:

Description Maciej Bendkowski

2014-02-17 08:43:01 EST

Consider two applications, A - a Java-based Spring application, and B - a node.js application. The "command" manifest property should be required in case of B, but optional in case of application A. With recent changes in bug 427977, we're no longer forcing a "command" property in both cases. This causes B to be deployed, but unable to start. We should be warning that the "command" is missing in case of node.js applications. As this bug is a more general issue, in order to provide contextual semantic analysis, we need bug 428351 to be fixed.

Comment 1 Maciej Bendkowski

2015-01-09 12:00:39 EST

With pluginable deployment planners, wizards and packagers it is now possible to provide semantic analysis and therefore we can close this bug.