[news.eclipse.modeling.amalgam] Re: Xpand file error?

[Richard Gronback <richard.gronback@xxxxxxxxxxx>]

Posting here, in addition to direct email:

Try changing the encoding on the files to ISO-8859-1.

Also, you¹ll need to make sure the new builder is used.  You should add this
in your .project file (remove any other xpand builder):

        <buildCommand>
            <name>org.eclipse.gmf.xpand.xpandBuilder</name>
            <arguments>
            </arguments>
        </buildCommand>

Finally, the newer Xpand uses an .xpand-root file in the project directory
to point at template locations.  It¹s a simple file that should only contain
a single entry for most projects, e.g. ?templates¹ (if there is a directory
named ?templates¹ in your project where you keep your xpt files).

HTH,
Rich


On 6/5/09 6:55 AM, in article 4A28F9B5.1070207@xxxxxxxxxxxxxxx, "Bill Hinge"
<steve.orobec@xxxxxxxxxxxxxxx> wrote:

> Hi Rich
> 
> Just tried 1.0M7
> 
> I noticed when I imported my projects from 20081128-0606 that the
> chevrons had changed to ' and a weird degree character (I'm on OS X).
> This is the same if I open the file in textedit, but I can cut and paste
> chevrons OK from the older dsltk.
> 
> The URL works but the older format doesn't. Also the xpand nature is no
> longer there, I downloaded the examples from the welcome screen for good
> measure. On both my templates and the examples, ctrl-space doesn't seem
> to work. Am I missing something?
> 
> If I wish to use xpand code generation (for demo purposes - just looking
> for something basic an easy at the moment that I can run from a plugin
> or rcp) - what would you recommend as a build/plugin set?
> 
> 
> regards
> Steve
> 
> 
> 
> Richard Gronback wrote:
>> I'm afraid the errors are "normal" for this build, using the original Xpand
>> (which doesn't support URI-based imports, btw).  The GMF-based Xpand has
>> much improved the situation in the current release train.
>> 
>> The workflow file wizard provides no default content.  As both the newer
>> GMF-based Xpand and QVT both support Ant invocation, there is little need
>> for these files when using the current release train.
>> 
>> Sorry for the bad news.
>> 
>> Best,
>> Rich
>> 
>> 
>> On 6/4/09 6:51 PM, in article h09j5b$vgt$1@xxxxxxxxxxxxxxxxx, "Bill Hinge"
>> <steve.orobec@xxxxxxxxxxxxxxx> wrote:
>> 
>>> Hi
>>> 
>>> I'm using Amalgam at the moment.
>>> 
>>> I've created a DSL project, generated model and diagram code etc.
>>> 
>>> I've also used the GMF-XPand wizard to create an xpand file in templates
>>> 
>>> If I use ctrl-space I can correctly see a list of selectable dsl's for
>>> me to import. If I pick them I get something like <<IMPORT contract>>,
>>> <<IMPORT uml>> etc which is what I expect. (I also have Xpand Nature
>>> turned on by the way.) The "URI" import doesn't seem to be supported
>>> here.
>>> 
>>> I can then build up my template as expected by using ctrl-space etc.
>>> But when I save I get a red error flag against each import statement
>>> despite them appearing to be working. In my dependencies I have the
>>> following
>>> 
>>> 
>>> Require-Bundle: org.eclipse.core.runtime,
>>>   org.eclipse.emf.ecore;visibility:=reexport,
>>>   org.eclipse.emf.ecore.xmi;visibility:=reexport,
>>>   org.eclipse.uml2.uml;visibility:=reexport,
>>>   org.eclipse.xpand;bundle-version="0.7.0",
>>>   org.eclipse.xtend;bundle-version="0.7.0",
>>>   org.eclipse.xtend.typesystem.emf;bundle-version="0.7.0",
>>>   org.eclipse.emf.mwe.core;bundle-version="0.7.0"
>>> Bundle-ActivationPolicy: lazy
>>> 
>>> Any ideas please? is this a symptom of some other error?
>>> (DSL toolkit Build id: 20081128-0606)
>>> 
>>> Also the workflow wizard just seems to create an empty text file
>>> with no context editing support, is this really all I should get?
>>> 
>>> regards
>>> Steve
>> 

-- 
Thanks,
Rich