before I posted I tried recreating it and observed the same as discussed in the bug. No code assist for a straight project dependency, but code assist working for class folder dependencies.
I'd be interested in what didn't work correctly if you had the secondary project as an AspectJ project - I had a simple ITD method on a target and could see that method in proposed completions in my consuming project. Making the secondary project an AJ project is a temporary hack as there is nothing in the consuming project that should require it, so as discussed in the bug we may automatically enable the parts of AJDT for that consuming project that we need to if we detect an upstream AspectJ project. The user won't have to do anything. I only manually added project dependencies under ProjectProperties>JavaBuildPath>Projects. I'm not sure why it would suddenly start working for you if switching from an m2eclipse setup to an eclipse setup, but all that is interesting material, and I'll add it to the bug report. cheers, Andy On 9 March 2010 15:48, Sharon Gorman <[email protected]> wrote: > Hi Andy, > Have taken a look at that bug, and just a bit more to clarify. > 1) I do not really have an issue with making it and AspectJ project. In my > opinion this is fine as a work around. My issue was that even when I did > this, the code assist did not work correctly. > 2) Once I removed and re-added my project dependency via eclipse, rather > than relying on m2eclipse, the code assist started working. I note that the > m2Eclipse adds the dependency under "Maven Dependencies" on the Package > explorer whereas once I re-added it it appears under the "Web App > Libraries". > > Does that make sense? > > Thanks > Sharon > > On Wed, Mar 10, 2010 at 10:41 AM, Sharon Gorman <[email protected]> > wrote: >> >> Hi Andy, >> Firstly, thanks for such a prompt reply. >> >> I have had a bit of a play around, and think I may have narrowed down the >> issue. >> >> My two projects were part of a maven multi-module project, that I had >> loaded using the m2eclipse plugin. So the dependency between the projects >> had been added by m2eclipse. It seems that AJDT somehow did not like this >> dependency. When I removed it, then re-added the dependency in eclipse, the >> code assist started working. Not sure if this is a bug, and whether it is >> a bug in m2eclipse or AJDT. >> >> But it now seems to work and my dependency is on the project, not on the >> class folder. >> >> >> >> Thanks >> Sharon >> >> > > > > -- > ----------------------------------- > Sharon Gorman > Senior Consultant > Object Consulting > > _______________________________________________ > aspectj-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
