Can you send me the projects if they are small? I will have a look at it. ps- please send these messages to the group, not just me. Others might be having the same problem that you are. (Unless there is a reason why you want this private, but from the looks of your log file, it doesn't seem so.
On Thu, May 14, 2009 at 11:36 AM, Wade Girard <[email protected]> wrote: > Here is the full output, > > 13:27:33 Startup information: > AJDT version: 1.7.0.20090413160245 for Eclipse 3.5 > AspectJ Compiler version: DEVELOPMENT > usingVisualiser=true > usingXref=true > usingCUprovider=true > ajde.version.at.previous.startup = @AJDEVERSION@ > 13:27:54 AJDTContentProvider.updateData() executed - took 750ms > 13:28:8 Removed problems and tasks for project projectb > 13:28:9 Builder: Tidied output folder(s), removed class files and derived > resources > 13:28:9 Timer event: 0ms: Delete markers: projectb (Finished deleting > markers for projectb) > 13:28:9 Compiler configuration for project projectb doesn't know previous > state, so assuming EVERYTHING has changed. > 13:28:9 > =========================================================================================== > 13:28:9 Build kind = FULLBUILD > 13:28:9 Project=projectb, kind of build requested=Full AspectJ compilation > 13:28:9 Timer event: 0ms: Flush included source file cache > 13:28:9 Timer event: 0ms: Check delta > 13:28:9 Builder: Tidied output folder(s), removed class files and derived > resources > 13:28:9 Timer event: 31ms: Pre compile > 13:28:9 Compiler configuration for project projectb has been read by > compiler. Resetting. > 13:28:9 Configuration was [PROJECTSOURCEFILES_CHANGED, > JAVAOPTIONS_CHANGED, ASPECTPATH_CHANGED, CLASSPATH_CHANGED, INPATH_CHANGED, > NONSTANDARDOPTIONS_CHANGED, OUTJAR_CHANGED, PROJECTSOURCERESOURCES_CHANGED, > OUTPUTDESTINATIONS_CHANGED, INJARS_CHANGED] > 13:28:9 Resetting list of modified source files. Was null > 13:28:9 Preparing for build: not going to be incremental because no > successful previous full build > 13:28:9 Timer event: 281ms: Time to first compiled message > 13:28:9 Timer event: 297ms: Time to first woven message > 13:28:10 AspectJ reports build successful, build was: FULL > 13:28:10 AJDE Callback: finish. Was full build: true > 13:28:10 Timer event: 1531ms: Total time spent in AJDE > 13:28:10 Timer event: 0ms: Refresh after build > 13:28:10 Types affected during build = 272 > 13:28:10 Timer event: 1562ms: Total time spent in AJBuilder.build() > 13:28:10 Timer event: 0ms: Update visualizer, xref, advice listeners for > (separate thread): projectb > 13:28:10 AJDTContentProvider.updateData() executed - took 0ms > 13:28:10 Timer event: 0ms: Delete markers: projectb (Finished deleting > markers for projectb) > 13:28:10 Timer event: 0ms: Create markers: projectb (Finished creating > markers for projectb) > 13:28:10 Created 0 markers in 1 files > 13:28:12 > =========================================================================================== > 13:28:12 Build kind = AUTOBUILD > 13:28:12 Project=projectb, kind of build requested=Incremental AspectJ > compilation > 13:28:12 Timer event: 0ms: Flush included source file cache > 13:28:12 Timer event: 0ms: Check delta > 13:28:12 Timer event: 0ms: Looking for and marking configuration changes in > projectb > 13:28:12 Configuration changes found: false > 13:28:12 build: Examined delta - no source file or classpath changes for > project projectb > 13:28:12 Timer event: 0ms: Looking for and marking configuration changes in > projecta > 13:28:12 Configuration changes found: false > 13:28:12 Timer event: 0ms: Looking for and marking configuration changes in > projectb > 13:28:12 Configuration changes found: false > 13:28:12 Compiler configuration for project projectb has been read by > compiler. Resetting. > 13:28:12 Configuration was [] > 13:28:12 Resetting list of modified source files. Was [] > 13:28:12 Timer event: 0ms: Look for source/resource changes > 13:28:12 No source/resource changes found, exiting build > 13:28:12 Timer event: 0ms: Total time spent in AJBuilder.build() > > I did not see any reference to javaBuilder in .project, but I did see > references to ajBuilder. > > On May 14, 2009, at 1:21 PM, Andrew Eisenberg wrote: > >> OK...for now, remove the output jar and let it build to disk. >> >> Open up the .project file. You should see an entry for ajBuilder, but >> *no* entry for javaBuilder. >> >> Now, open the AJDT Event Trace vew and ensure that the default filters >> are selected. Do a full build of project B. Do you see messages >> about Project A? Do you see messages about weaving classes from >> project A? >> >> On Thu, May 14, 2009 at 11:14 AM, Wade Girard <[email protected]> >> wrote: >>> >>> okay, so here is a breakdown of the setup in eclipse >>> >>> - project A is a regular java project that is built into a jar and has >>> several classes. >>> - project B is an aspectJ project that has aspects for project A >>> >>> in project B's->properties->AspectJ Build Inpath tab I added "Project A" >>> in project B's->properties->AspectJ Build Aspect Path tab I have nothing >>> (should I add something here, if so what) >>> in project B's->properties->AspectJ Build Output jar tab I typed in the >>> name >>> of the jar file that the maven build creates >>> >>> We do use the m2eclipse plugin to create the eclipse projects, that was >>> used >>> to create this project. >>> >>> On May 13, 2009, at 3:14 PM, Andrew Eisenberg wrote: >>> >>>> Assuming that there *should* be something on you in/aspect path, this >>>> might be caused by a bug in the maven-eclpse-plugin in that it doesn't >>>> properly configure aspect paths on an eclipse project. >>>> >>>> See bug 270554 for a way to specify in path and aspect path through >>>> maven. >>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=270554 >>>> >>>> Alternatively, you can use a plugin like m2eclipse that manages it for >>>> you. >>>> >>>> Let me know if this works for you. >>>> >>>> On Wed, May 13, 2009 at 11:51 AM, Wade Girard <[email protected]> >>>> wrote: >>>>> >>>>> If it matters... >>>>> >>>>> When I open up the properties for the project, under the "AspectJ >>>>> Build", >>>>> Inpath and Aspect Path are empty, and in the Output Jar tab the Output >>>>> jar >>>>> is an empty field. >>>>> >>>>> AspectJ Compile does not have "Enable project specific settings >>>>> enabled. >>>>> >>>>> >>>>> On May 12, 2009, at 9:57 PM, Andrew Eisenberg wrote: >>>>> >>>>>> On Tue, May 12, 2009 at 4:22 PM, Wade Girard <[email protected]> >>>>>> wrote: >>>>>>> >>>>>>> On May 12, 2009, at 5:28 PM, Andrew Eisenberg wrote: >>>>>>> >>>>>>>> How is the jar file being created in Eclipse? >>>>>>> >>>>>>> How should the jar file be created? I can take a peek at the >>>>>>> settings. >>>>>> >>>>>> Well, there are many ways that it could be created: through ant, >>>>>> through pde, through eclipse exporting, and there may be others. >>>>>> >>>>>> I think you said that the compiled aspect class files do not appear in >>>>>> the jar that is created through Eclipse. This means that ajc is not >>>>>> being invoked and instead the jdt compiler (or javac) is being >>>>>> invoked. >>>>>> >>>>>> If you can tell me what mechanism is creating the jar, perhaps we can >>>>>> figure out why ajc is not being invoked. >>>>>> >>>>>> --a >>>>> >>>>> Wade Girard >>>>> [email protected] >>>>> >>>>> >>>>> >>>>> >>> >>> Wade Girard >>> [email protected] >>> >>> >>> >>> > > Wade Girard > [email protected] > > > > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
