$%#@!
After much pain and agony debugging ten levels deep into oAW, I finally figured out the problem. It was like you said (I saw your response right after I figured it out). After running into the problems with the Fornax repo a few days ago, I stopped running the mvn install target on sculptor-parent and was testing by running the workflow. Somehow it ended up that my test Eclipse environment had the latest changes in the editor plugin, but the target project is looking in MAVEN_REPO\org\fornax\cartridges\org.fornax.cartridges.sculptor.dsl\1.4.0\org.fornax.cartridges.sculptor.dsl-1.4.0.jar's sculptordsl.xmi file.
So even though my editor contained my latest changes and looked like everything was working, the parser was looking in the local Maven repo at the DSL Ecore model from three days ago!
I ran maven install and things are finally working. There was nothing wrong with my DSL changes after all. Arg!
btw, why is it so hard to debug into oAW? Most of the source from the Eclipse plugins directory don't match up with the jars in the Maven repo. I checked out all the oaw4 code from their CVS repo and still had to debug blind a lot of the time. Luckily I happened to see the source path of the xmi file and finally figured out the problem.
Thanks,
Polly
Patrik Nordwall wrote:
Hi, have you rebuilt sculptor-parent (mvn install)? Are you using the correct version number in your target project? Trunkow 1.5.0-SNAPSHOT
