Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337432 - Problem with .xmi file located outside workspace
Summary: Problem with .xmi file located outside workspace
Status: CLOSED DUPLICATE of bug 318137
Alias: None
Product: Acceleo
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-17 08:26 EST by Liviu CLA
Modified: 2011-02-17 09:18 EST (History)
1 user (show)

See Also:


Attachments
stack trace of exception (2.89 KB, text/plain)
2011-02-17 08:27 EST, Liviu CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Liviu CLA 2011-02-17 08:26:56 EST
Build Identifier: M20100909-0800

Hello,
 I have the following configuration: 2 imported project from a ClearCase 
location (one containing the mtl file, and the other containing 2 .xmi files 
representing instances of an ecore model).

In the first project I have the following run configuration for the mtl file:


<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<launchConfiguration 
type="org.eclipse.acceleo.ide.ui.launching.launchConfigurationType">
<stringAttribute key="org.eclipse.acceleo.ide.ui.ARGUMENTS" value=""/>
<booleanAttribute key="org.eclipse.acceleo.ide.ui.COMPUTE_TRACEABILITY" 
value="false"/>
<stringAttribute 
key="org.eclipse.acceleo.ide.ui.LAUNCHING_STRATEGY_DESCRIPTION" value="Acceleo 
Plug-in Application"/>
<stringAttribute key="org.eclipse.acceleo.ide.ui.MODEL_PATH" 
value="/trss.l905.DFA.index/sample/ILM1_DataFlowIndex.xmi"/>
<stringAttribute key="org.eclipse.acceleo.ide.ui.TARGET_PATH" 
value="/trss.l905.DFA.example.exportIndex/test"/>
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_PATHS">
<listEntry 
value="/trss.l905.DFA.example.exportIndex/src/trss/l905/DFA/example/exportIndex
/files/GenerateDFAIndex.java"/>
</listAttribute>
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_TYPES">
<listEntry value="1"/>
</listAttribute>
<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" 
value="trss.l905.DFA.example.exportIndex.files.GenerateDFAIndex"/>
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" 
value="&quot;Y:/estw_l90_5/im/doc/generic/mdd/samples/trss.l905.DFA.index/sampl
e/ILM1_DataFlowIndex.xmi&quot; 
&quot;Y:/estw_l90_5/im/doc/generic/mdd/samples/trss.l905.DFA.example.exportInde
x/test&quot;"/>
<stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" 
value="trss.l905.DFA.example.exportIndex"/>
</launchConfiguration>

The 
value="&quot;Y:/estw_l90_5/im/doc/generic/mdd/samples/trss.l905.DFA.index/sampl
e/ILM1_DataFlowIndex.xmi&quot; string represents the xmi file, located in the 
second project, also in a Clearcase  location. When I run with this 
configuration, I have the following exception :
"java.io.FileNotFoundException: C:\Documents and 
Settings\workspace\trss.l905.DFA.index\sample\ILM1_DataFlowIndex.xmi (The 
system cannot find the path specified)". Seems that the .xmi file is searched 
in my workspace, even if the absolute path (mentioned above) is elsewhere.
I attached the whole Exception Stack trace

Is this approach correct to handle xmi files outside workspace? 
The workaround I found was to have the xmi file in a local project, and just 
the project containing the mtl file on Clearcase.

Thank you,
Liviu

Reproducible: Always

Steps to Reproduce:
Steps described above.
Comment 1 Liviu CLA 2011-02-17 08:27:46 EST
Created attachment 189177 [details]
stack trace of exception
Comment 2 Laurent Goubet CLA 2011-02-17 08:57:19 EST
Hi Liviu,

This is a duplicate of 318137. Though this bug is still opened, the use case you describe here should already be fixed (from Acceleo 3.0.2RC2 onward). You can update to this version by adding the update site
http://download.eclipse.org/modeling/m2t/acceleo/updates/releases/3.0
and selecting the latest version there.

*** This bug has been marked as a duplicate of bug 318137 ***
Comment 3 Liviu CLA 2011-02-17 09:18:36 EST
Thank you