Community
Participate
Working Groups
If I have a project created by default and so below the WorkspaceRoot, the Acceleo launcher can find and use the source models. However if I move the project outside the WorkspaceRoot, the launcher browser can still find the files but I get Caused by: java.io.FileNotFoundException: C:\Development.NoBackup\Check\runtime-New_configuration\Models\Pivot2UML.eqvtrelation (The system cannot find the path specified) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at org.eclipse.emf.ecore.resource.impl.FileURIHandlerImpl.createInputStream(FileURIHandlerImpl.java:105) at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:301) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1254) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:255) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:270) probably because URI resolution is for / against the workspace root location rather than /Project against the project location. [Also: why does the source model need to be in the workspace at all?]
I believe this is the same as bug 306692. Setting dependency instead of duplicate so that I remember to check that both are fixed by the resolution of one.
*** Bug 284681 has been marked as a duplicate of this bug. ***
The first part of this bug is fixed in 3.0.2RC2 and 3.1.0M6. The input model still need to be in the workspace, but no longer below the workspace root.
*** Bug 337432 has been marked as a duplicate of this bug. ***
The first part of this bug is fixed since 3.0.2, there are no plans to change the behavior of the launch config from workspace relative paths to project relative ones (for both the model and target folder).