jcabi-maven-plugin | Supplementary maven plugin for AspectJ | Plugin library

by jcabi Java Version: 0.17.0 License: Non-SPDX

X-Ray Key Features Code Snippets(1)Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | jcabi-maven-plugin Summary

jcabi-maven-plugin is a Java library typically used in Plugin, Maven applications. jcabi-maven-plugin has no bugs, it has no vulnerabilities, it has build file available and it has low support. However jcabi-maven-plugin has a Non-SPDX License. You can download it from GitHub, Maven.

More details are here: plugin.jcabi.com.

Support

Quality

Security

License

Reuse

Support

jcabi-maven-plugin has a low active ecosystem.

It has 28 star(s) with 22 fork(s). There are 7 watchers for this library.

It had no major release in the last 12 months.

There are 5 open issues and 33 have been closed. On average issues are closed in 185 days. There are 8 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of jcabi-maven-plugin is 0.17.0

Quality

jcabi-maven-plugin has 0 bugs and 25 code smells.

Security

jcabi-maven-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jcabi-maven-plugin code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jcabi-maven-plugin has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

jcabi-maven-plugin releases are available to install and integrate.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

jcabi-maven-plugin saves you 661 person hours of effort in developing the same functionality from scratch.

It has 1532 lines of code, 49 functions and 25 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed jcabi-maven-plugin and discovered the below as its top functions. This is intended to give you an instant insight into jcabi-maven-plugin implemented functionality, and help decide if they suit your requirements.

Execute AJC mojo
Version for versions .
Execute Mojo .
Creates the text in text format .
Retrieves the files for a given dependency
Copy unwoven classes .
Executes mojo .
Copies all files from one directory to another .
Returns the given string value if it is not null .

Get all kandi verified functions for this library.

jcabi-maven-plugin Key Features

No Key Features are available at this moment for jcabi-maven-plugin.

jcabi-maven-plugin Examples and Code Snippets

How to contribute?

Java

Lines of Code : 1

License : Non-SPDX (NOASSERTION)

Copy

$ mvn clean install -Pqulice

Community Discussions

Trending Discussions on jcabi-maven-plugin

AspectJ binary weaving with Jcabi Maven plugin not working for Kotlin code

Apply aspect on non-spring-managed beans

QUESTION

AspectJ binary weaving with Jcabi Maven plugin not working for Kotlin code

Asked 2019-Jul-05 at 02:41

I'm trying to run a little annotation over function that will log before and after the method execution.

What I've done: (all classes are under src/main/kotlin)

Annotation class

...

ANSWER

Answered 2019-Jul-05 at 02:41

Disclaimer:

I have never used the Jcabi plugin before, normally I always use AspectJ Maven plugin, also for binary weaving.
I have never used the Kotlin language before, normally I use Java or Groovy.

Now some things are not okay in your aspect:

It must not be abstract, otherwise no instance can be created.
For void methods it must be able to return null, so the Kotlin return type should be Any?
You should proceed() in between the before and after log messages, otherwise the log output will be wrong.
Assuming that your classes, especially the annotation class, do not reside in the default package but have an actual package name, you need to use the fully qualified class name in your pointcut, e.g. @annotation(de.scrum_master.app.LogMe)
Using an aspect class name Aspect, i.e. the same name as the @Aspect annotation, just in another package, is kind of ugly. You should rename it.

For me this works nicely:

Source https://stackoverflow.com/questions/56890630

QUESTION

Apply aspect on non-spring-managed beans

Asked 2018-Nov-30 at 20:53

Apply aspect on non-spring-managed beans

I have an integration-test which calls a micro-service (abc-service) implemented using drop-wizard framework. My integration test calls a resource end point inside the micro-service. This abc-service has dependencies on 2 modules, which I have it in abc-service pom.xml

a. Aspect-module

b. Xyz-module --> this module makes http calls to outside service (not in our domain). This xyz-module has got 15 manager classes and each class has a public static methods, which makes http calls to outside service, I want to calculate processing time for all http calls, i.e I want to apply @Around advice on all public static methods which makes http calls in all manager classes. All classes in xyz-module are non-spring managed beans

Code in Aspect-module

...

ANSWER

Answered 2018-Nov-05 at 11:49

I inspected your GitHub repo. First I unpacked and removed all ZIP files (very ugly to commit them, especially including target directory contents) and added a parent POM in order to be able to properly build the whole project. Then I noticed that there were several things wrong:

If you want to use your aspect module via LTW, you need to provide a properly configured aop.xml file according to the AspectJ LTW documentation, e.g. like this:

Source https://stackoverflow.com/questions/52557650

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install jcabi-maven-plugin

You can download it from GitHub, Maven.
You can use jcabi-maven-plugin like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the jcabi-maven-plugin component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

Fork the repository, make changes, submit a pull request. We promise to review your changes same day and apply to the master branch, if they look correct.

Find more information at: