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

Bug 385285

Summary:	Auto-add Application.e4xmi to the build.properties file
Product:	[Eclipse Project] e4	Reporter:	Shumy Mising name <micaelpedrosa>
Component:	Tools	Assignee:	Project Inbox <e4.tools-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	minor
Priority:	P3	CC:	Lars.Vogel, nobody
Version:	1.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Shumy Mising name

2012-07-17 06:54:54 EDT

Build Identifier: 20120614-1722

I have a report log with "org.eclipse.core.runtime.AssertionFailedException:
null argument:applicationXMI argument missing".

I was completing the tutorial from step 8 in (manual product configuration)
http://www.vogella.com/articles/EclipseRCP/article.html

When I run from eclipse, it's all OK, but when I export and try to run the
product, the exception is throw.

I have found the problem: Manual add the Application.e4xmi and build.xml to the Binary Build.

Reproducible: Always

Comment 1 Lars Vogel

2012-07-17 13:33:28 EDT

@Shumy: This is described either in my Eclipse 4 book or in this online tutorial. 

http://www.vogella.com/articles/EclipseProductDeployment/article.html

Adding resources automatically to the build is something which IMHO should not be done. Currently only file generated by new project wizards are added to build.properties. 

I suggest to close this bug as "Won't fix". @Sopot what do you think?

Comment 2 Nobody - feel free to take it

2012-07-17 20:25:06 EDT

I agree that for other resources such as css etc. we can leave that manual but Application.e4xmi is another thing.

4.x speaking, there is no use case when you would export your app but leave this out. So, changing this bug to specifically request the inclusion of just Application.e4xmi seems a good compromise.

Comment 3 Shumy Mising name

2012-07-18 12:35:50 EDT

Also, what I don't understand is why the launch configuration inside eclipse is different from the exported configuration.
Sometimes I just know that something is missing after the export.

If you don't want to change the behavior of auto import, at least make it consistent! If something is missing, fail earlier in eclipse launch.

This is not just for the Binary Build, also happens if some required dependencies are not listed in product configuration.

Comment 4 Lars Vogel

2012-07-18 12:51:43 EDT

@Sopot, I agree the Application model wizard should add it to the build.properties file.

Comment 5 Lars Vogel

2014-04-28 13:53:07 EDT

Fixed a while ago, marking as fixed.