This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
No announcement yet.
using a roo generated entity in a project referencePage Title Module
Well, you can follow this bug, we are thinking through the possible ways of enabling ITD-awareness in pure Java projects (which would solve your initial problem). But we need to carefully consider the ramifications of doing so before we commit to anything:
I just had a thought. I'm not sure if you have found a solution yet, but this should work:
In your non-aspects project open up the .project file and add the line:
above the line:
Keep all else the same (ie- do not execute the Add Aspect Nature to your project). Save, and close all your editors in ProjectB. And reopen them. You should now have ITD-aware content assist in your editor.
What's going on here is that the Weaving service looks at project natures to determine whether or not weaving should be applied to editors of that project. So, by adding the AJ nature to a project, without doing anything else, you should get the extra functionality, while still being able to compile for android.
If this works for you, then I can create an automated way of doing this.