Community
Participate
Working Groups
Environment: Macbook pro OSX Java 1.7 64 bit Eclipse 4.2 AspectJ Development Tools 2.2.2 Problem: My workspace build fine when I compile it on a Windows 7 box with exactly the same code, configuration, etc. When I try to build the workspace on my new Mac, the out.jar files aren't generated. All options, settings, etc. are identical.
Do you get any diagnostics? Is there anything in your eclipse error log?
I have these 7 of these type of warnings... AJC: warning at /Users/corbyjames/Documents/workspace/com.tmbs.team.km/tmbs_km.jar!com/tmbs/team/km/support/AuditAspect.class:30::0 advice defined in com.tmbs.team.km.support.AuditAspect has not been applied [Xlint:adviceDidNotMatch] Here is the environment read out from the warning... eclipse.buildId=M20120914-1800 java.version=1.7.0_11 java.vendor=Oracle Corporation BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -product org.eclipse.epp.package.modeling.product -keyring /Users/corbyjames/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.modeling.product -keyring /Users/corbyjames/.eclipse_keyring -showlocation I do not have these on the PC build.
Is there any way you can share the project with me? All our developers for AspectJ/AJDT work on macs and haven't seen these kinds of issue.
There are a number of projects in our workspace with aspects. We are also using RAP and TEXO. We have it set up for compile time binding, not sure if that makes a difference. Would you need the entire workspace or would one project work?
Just one project where you expect the output to be in an out.jar would help me investigate. But maybe we can double check a few things. I presume in the .settings/org.eclipse.ajdt.ui.prefs you are seeing: org.eclipse.ajdt.ui.outJar=<something>.jar And the .project file looks a bit like this: <projectDescription> <name>AP</name> <comment></comment> <projects> </projects> <buildSpec> <buildCommand> <name>org.eclipse.ajdt.core.ajbuilder</name> <arguments> </arguments> </buildCommand> </buildSpec> <natures> <nature>org.eclipse.ajdt.ui.ajnature</nature> <nature>org.eclipse.jdt.core.javanature</nature> </natures> </projectDescription> That just confirms is the using the builder we expect and the output *should* be going into the jar
