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

Bug 322943

Summary: Export of WAR file fails with FileNotFoundException (launch.ini)
Product: z_Archived Reporter: Karsten Voigt <eclipse>
Component: LibraAssignee: Project Inbox <rap-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Karsten Voigt CLA 2010-08-17 15:05:31 EDT
Build Identifier: 20100617-1415

I created a warproduct (based on http://eclipsesource.com/blogs/2010/08/17/equinoxrap-war-deployment-an-end-to-the-pain). During creation of warproduct file a directory WEB-INF was created (automatic creation; directory contains web.xml and launch.ini). The validation is successful.

The export fails without any notice.

The log file contains the following error:

java.io.FileNotFoundException: D:\project\priv\tdworkspace\test.ui.rap\WEB-INF\launch.ini (The system cannot find the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(Unknown Source)
at org.eclipse.rap.warproducts.core.WARProductExportOperation.createWarContent(WARProductExportOperation.java:282)
at org.eclipse.rap.warproducts.core.WARProductExportOperation.prepareWARFile(WARProductExportOperation.java:237)
at org.eclipse.rap.warproducts.core.WARProductExportOperation.handleRootFiles(WARProductExportOperation.java:226)
at org.eclipse.rap.warproducts.core.WARProductExportOperation.createBuildPropertiesFile(WARProductExportOperation.java:208)
at org.eclipse.rap.warproducts.core.WARProductExportOperation.run(WARProductExportOperation.java:125)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Reproducible: Always

Steps to Reproduce:
1. Create new warproduct based on launch configuration
2. Fill general information (at least I've done that)
3. Validate war product
4. Export war product
Comment 1 Karsten Voigt CLA 2010-08-18 08:54:02 EDT

*** This bug has been marked as a duplicate of bug 322280 ***