As ever, Thanks Matthew! ;-) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Clement Sent: 17 May 2008 03:09 To: [email protected] Subject: Re: [aspectj-users] Type not exposed to weaver warning
Hi Neil, With project (1) on the classpath of project (2), we will be able to resolve references to types in project (1) but we won't weave types from there, hence the message. If you put project (1) on the *inpath* of project (2), we will be able to weave them and the woven versions will be output to the bin folder of project (2). So, classpath is just for resolving references (not weaving) whilst inpath is for resolving references *and* weaving. Perhaps both options should have been presented in the quickfix. cheers, Andy. 2008/5/16 neil loughran <[EMAIL PROTECTED]>: > Hi, > > > > I have 2 projects in my Eclipse IDE. (1) is a regular java project the > other (2) is an AspectJ project. > > > > I need the aspectJ project to reference (1) > > > > So far I've configured the import dependencies (I was referring to certain > types in project (1) in my aspect) using the Quick Fix facility which added > the project (1) to the classpath of project (2) > > However I'm not sure how to get around the affected type not exposed to > weaver warning I am getting. > > > > What else do I need to change? I've googled for some answers but nothing > concrete has come up. > > > > Many thanks > > Neil > > _______________________________________________ > 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 _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
