-
Updated
Oct 1, 2020 - Java
annotation-processor
Here are 314 public repositories matching this topic...
-
Updated
Jul 22, 2020 - Java
-
Updated
Jun 4, 2020 - Java
-
Updated
Oct 7, 2020 - Java
-
Updated
Aug 23, 2019 - Java
-
Updated
Jul 21, 2020 - Java
-
Updated
Oct 3, 2020 - Java
-
Updated
Feb 1, 2017 - Java
-
Updated
Sep 29, 2019 - Java
-
Updated
Sep 22, 2020 - Kotlin
-
Updated
Oct 7, 2020 - Kotlin
-
Updated
Feb 6, 2020 - Java
-
Updated
Nov 24, 2019 - Java
-
Updated
Nov 25, 2018 - Java
-
Updated
Aug 2, 2020 - Java
-
Updated
Mar 13, 2019 - Java
-
Updated
Oct 6, 2019 - Java
-
Updated
Dec 6, 2018 - Groovy
-
Updated
May 28, 2020 - JavaScript
-
Updated
Oct 11, 2020 - Java
-
Updated
Feb 24, 2020 - Kotlin
-
Updated
Apr 1, 2020 - Java
-
Updated
Oct 8, 2020 - Java
-
Updated
Aug 9, 2020 - Kotlin
-
Updated
Oct 9, 2020 - Kotlin
-
Updated
Sep 30, 2020 - Kotlin
-
Updated
Sep 10, 2020
-
Updated
Jul 19, 2019 - Kotlin
-
Updated
Jun 1, 2018 - Java
Improve this page
Add a description, image, and links to the annotation-processor topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the annotation-processor topic, visit your repo's landing page and select "manage topics."
Would it be possible to enable dynamic discovery of the mapper classes used in a generated code according to the source and target class through the package annotation configuration like:
@Mapper (usesPackage = {"org.company.componenent.mappers"})