Make hickory an optional dependency as well (#1765)

Using optional because IntelliJ is picking up hickory as a transitive
dependency and runs the hickory processor in projects using mapstruct-processor.
This happens only when the processor is defined in the maven-compiler annotationProcessorPaths.
This is related to https://youtrack.jetbrains.com/issue/IDEA-200481.
This commit is contained in:
Filip Hrisafov 2019-03-30 09:47:35 +01:00 committed by GitHub
parent 6c838e6e0c
commit 3790f1919a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -36,10 +36,14 @@
<!-- Compile-only; Using "provided" scope as there is no such scope in Maven;
these dependencies are not required at runtime, only for prism generation
and tests -->
<!-- Using optional as well due to IntelliJ picking up the dependency
and running the hickory processor in projects using the mapstruct-processor.
This happens only when the processor is defined in the maven-compiler annotationProcessorPaths -->
<dependency>
<groupId>com.jolira</groupId>
<artifactId>hickory</artifactId>
<scope>provided</scope>
<optional>true</optional>
</dependency>
<dependency>
<groupId>${project.groupId}</groupId>