Class AspectJCompiler
- All Implemented Interfaces:
ICompiler
In order to include other aspects, specify aspectj.publicAspectPathByClass
and similarly as
documented below (ASPECTJ_PUBLIC_ASPECT_PATH_BY_CLASS
, ASPECTJ_PRIVATE_ASPECT_PATH_BY_CLASS
, ASPECTJ_TEST_ASPECT_PATH_BY_CLASS
).
The Spring aspect is already implied and does not need to be specified
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic String
In order to include other aspects, specifyaspectj.privateAspectPathByClass
with a comma-separated list of classes (on the corresponding Java components part classpath [i.e.static String
In order to include other aspects, specifyaspectj.publicAspectPathByClass
with a comma-separated list of classes (on the corresponding Java components part classpath [i.e.static String
In order to include other aspects, specifyaspectj.testAspectPathByClass
with a comma-separated list of classes (on the corresponding Java components part classpath [i.e.Fields inherited from interface com.zfabrik.components.java.build.ICompiler
COMPILER_ID, TYPE
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionboolean
compile(ICompilationContext compilationContext)
void
init(ICompilerContext context)
-
Field Details
-
ASPECTJ_PUBLIC_ASPECT_PATH_BY_CLASS
In order to include other aspects, specifyaspectj.publicAspectPathByClass
with a comma-separated list of classes (on the corresponding Java components part classpath [i.e. for api, test, or impl]). Those classes will be resolved to a corresponding aspect path for AspectJ compilation.This is so that the aspect path is limited to really just the aspect implementations (using annotations). Effectively, the compiler will use the jars containing the aspect classes. We use the class name to identify the jar and in the end all contained aspects will apply.
The Spring aspect is already implied and does not need to be specified.
- See Also:
- Constant Field Values
-
ASPECTJ_PRIVATE_ASPECT_PATH_BY_CLASS
In order to include other aspects, specifyaspectj.privateAspectPathByClass
with a comma-separated list of classes (on the corresponding Java components part classpath [i.e. for api, test, or impl]). Those classes will be resolved to a corresponding aspect path for AspectJ compilation.This is so that the aspect path is limited to really just the aspect implementations (using annotations). Effectively, the compiler will use the jars containing the aspect classes. We use the class name to identify the jar and in the end all contained aspects will apply.
The Spring aspect is already implied and does not need to be specified.
- See Also:
- Constant Field Values
-
ASPECTJ_TEST_ASPECT_PATH_BY_CLASS
In order to include other aspects, specifyaspectj.testAspectPathByClass
with a comma-separated list of classes (on the corresponding Java components part classpath [i.e. for api, test, or impl]). Those classes will be resolved to a corresponding aspect path for AspectJ compilation.This is so that the aspect path is limited to really just the aspect implementations (using annotations). Effectively, the compiler will use the jars containing the aspect classes. We use the class name to identify the jar and in the end all contained aspects will apply.
The Spring aspect is already implied and does not need to be specified.
- See Also:
- Constant Field Values
-
-
Constructor Details
-
AspectJCompiler
public AspectJCompiler()
-
-
Method Details