Hi, I have noticed some strange behavior when using oAW 4.3.1 and was wondering if you see it in Sculptor also. I have a project that declares external imports using the "classpath" method instead of the "platform:/resource" method. This means that the Design files can be resolved from a jar instead of having the project physically located in the user's workspace and opened.
I have all the changes from Sculptor that enabled resolving imports. This works beautifully when I test the plugins using the Run -> Eclipse Application launcher. In the editor, the external "import" statement and references to imported elements are resolved with no errors. The project that contains the imported Design files does not have to be open in my workspace. However, if I export the plugins and install them into another instance of Eclipse (which is a copy of the first one), the external import statement and references to imported elements have red error markers next to them. There are error messages complaining that they cannot be resolved. The only way the errors go away is if I have the imported project open in the user's workspace. Which is not right. Do you see this behavior in Sculptor? Or do you have any idea why things might behave differently using Run -> Eclipse Application vs. installing the plugins directly into Eclipse? Thanks! --Polly -- View this message in context: http://www.nabble.com/-Sculptor--weird-resolving-behavior-with-oAW-4.3.1-tp22936452s17564p22936452.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
