Hi Patrik,
I tested with oAW 4.3.1 RC2. Here are my findings:
1. I made the changes that you mentioned in Extensions.ext and
DslTransformation.ext.
2. The bug that you created below has been closed, and I was able to run
generate.oaw with no problems.
3. After that, there were no errors in the Eclipse console. However, when
I run "mvn-install" from the parent project, I get weird compiler errors in
the "dsl" project. I noticed that the WorkflowRunner prints out the version
as oAW 4.2.0, while when I run generate.oaw, the version is oAW 4.3.1.
Any ideas?
[INFO] oAW Maven2 Plugin V2.0.0
0 INFO WorkflowRunner -
--------------------------------------------------------------------------------------
47 INFO WorkflowRunner - openArchitectureWare 4.2.0, Build
200709162219NGT
47 INFO WorkflowRunner - (c) 2005-2007 openarchitectureware.org and
contributors
47 INFO WorkflowRunner -
--------------------------------------------------------------------------------------
47 INFO WorkflowRunner - running workflow: workflow.oaw
47 INFO WorkflowRunner -
78 WARN WorkflowCustomization - Cannot resolve keyword class
org.openarchitectureware.xpand2.Generator
78 WARN WorkflowCustomization - Cannot resolve keyword class
org.openarchitectureware.xpand2.Generator
78 WARN WorkflowCustomization - Cannot resolve keyword class
org.eclipse.mwe.emf.Reader
78 WARN WorkflowCustomization - Cannot resolve keyword class
org.eclipse.mwe.emf.Writer
78 WARN WorkflowCustomization - Cannot resolve keyword class
org.openarchitectureware.xtend.XtendComponent
78 WARN WorkflowCustomization - Cannot resolve keyword class
org.openarchitectureware.xtend.XtendComponent
78 WARN WorkflowCustomization - Cannot resolve keyword class
org.openarchitectureware.xpand2.GeneratorAdvice
78 WARN WorkflowCustomization - Cannot resolve keyword class
org.openarchitectureware.xtend.XtendAdvice
78 WARN WorkflowCustomization - Cannot resolve keyword class
org.openarchitectureware.check.CheckComponent
125 INFO WorkflowRunner - workflow completed in 0ms!
Adding C:\projects\InforBUS\mdd3\com.infor.mdd.dsl\src-gen
Adding C:\projects\InforBUS\mdd3\com.infor.mdd.dsl\src\protected\java
Adding C:\projects\InforBUS\mdd3\com.infor.mdd.dsl\src\test\generated\java
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 10 source files to
C:\projects\InforBUS\mdd3\com.infor.mdd.dsl\target\classes
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure
C:\projects\InforBUS\mdd3\com.infor.mdd.dsl\src-gen\org\fornax\cartridges\sculptor\dsl\parser\sculptordslParser.java:[12,51]
cannot find symbol
symbol : class ParseTreeManagerNeu
location: package org.openarchitectureware.xtext.parser.model
C:\projects\InforBUS\mdd3\com.infor.mdd.dsl\src-gen\org\fornax\cartridges\sculptor\dsl\parser\sculptordslParser.java:[74,16]
cannot find symbol
symbol : class ParseTreeManagerNeu
location: class org.fornax.cartridges.sculptor.dsl.parser.sculptordslParser
C:\projects\InforBUS\mdd3\com.infor.mdd.dsl\src-gen\org\fornax\cartridges\sculptor\dsl\parser\sculptordslParser.java:[81,15]
cannot find symbol
symbol : class ParseTreeManagerNeu
location: class org.fornax.cartridges.sculptor.dsl.parser.sculptordslParser
C:\projects\InforBUS\mdd3\com.infor.mdd.dsl\src-gen\org\fornax\cartridges\sculptor\dsl\parser\sculptordslParser.java:[74,46]
cannot find symbol
symbol : class ParseTreeManagerNeu
location: class org.fornax.cartridges.sculptor.dsl.parser.sculptordslParser
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: Compilation failure
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Tue Dec 09 14:14:50 EST 2008
[INFO] Final Memory: 25M/127M
[INFO]
------------------------------------------------------------------------
Patrik Nordwall wrote:
>
> It is something strange. I filed a new issue:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=257835
>
> Polly, you can continue testing if you temporary remove
> | (NOT "required")
> and
> | (NOT "nullable")
>
> I noticed that we need to change Extension.ext
> Change allElements and model to this:
> List[emf::EObject] allElements(emf::EObject x):
> x.allLocalElements()
>
> .union(x.allLocalElements().typeSelect(DslImport).collect(e|e.model(false).allLocalElements()))
> .flatten().toSet();
>
> // recursive imports, and on the fly assignment of external
> List[emf::EObject] model(DslImport this, boolean forceLinking) :
> (let loaded1 = model==null?{}:model.load(this, forceLinking).flatten() :
> (this.external ?
> (loaded1.typeSelect(DslModel).imports.setExternal(true) ->
> loaded1.typeSelect(DslModel).app.modules.setExternal(true)
> ):
> null
> ) ->
>
> loaded1.union(loaded1.typeSelect(DslModel).imports.model(forceLinking).flatten()));
>
>
> You can remove modelWitchCallCheck.
>
> Similar in DslTransformation.ext: imports.model(false)
>
> /Patrik
>
>
--
View this message in context:
http://www.nabble.com/-sculptor--oAW-4.3.1-tp20864485s17564p20921962.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Fornax-developer mailing list
Fornax-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fornax-developer
