Thanks for investigating this. It might be something for us to include in Sculptor pre-TMF also.
Another annoying bug with the imports is this: A import B (ordinary platform resource) Open A and B Modify B, Save Modify A, Save => errors The workaround is to close the files and open them again. Can you reproduce this bug? /Patrik polly.c.chang wrote: > > I finally figured this out. > > What I found is that oAW 4.3.1 does not have 100% support for resolving > import statements via the classpath. oAW depends on the Eclipse JDT > facility for resolving files from the classpath, and Eclipse JDT has a > weird bug where sometimes it would just fail to return the resource even > though it is physically there (as described in the Eclipse JDT Bugzilla > link). When that happens, the Editor is unable to resolve files from the > classpath. It might be that this only affects Eclipse 3.4.2, and I'm not > sure if m2eclipse 0.9.7 has anything to do with it, but the problem is > definitely reproducible in this environment. > > Anyway, I found the Eclipse TMF version of the JdtClasspathUriResolver > class, and it has several fixes for resolving files from the classpath, > including a workaround for the Eclipse JDT bug. Since TMF is not ready > for prime time, I took the class, put it in the DSL Editor project, and > hooked it up using SculptordslEditor.doSetInput() (copying much of the > code from the oAW superclass). I have tested the changes and found that > they do indeed resolve the problem after I changed the classpath > references to start with a "/" in front. > > Of course this is a hack, and when TMF is ready, I'll need to rip this > back out. But I just thought I'd share and let you know that the Sculptor > code is fine. :) > > Thanks, > Polly > > > > polly.c.chang wrote: >> >> For some strange reason, I am now able to reproduce the problem in my dev >> environment using Run As. It appears that the resolving behavior is >> caused by a bug in Eclipse JDT. >> >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=264776 >> >> There's some sample workaround code that looks promising. I'll let you >> know what I find. >> >> Thanks, >> Polly >> >> > > -- View this message in context: http://www.nabble.com/-Sculptor--weird-resolving-behavior-with-oAW-4.3.1-tp22936452s17564p23046974.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
