From 3790f1919a4a22907ff4a60422b2c79ef663817d Mon Sep 17 00:00:00 2001
From: Filip Hrisafov <filip.hrisafov@gmail.com>
Date: Sat, 30 Mar 2019 09:47:35 +0100
Subject: [PATCH] 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.
---
 processor/pom.xml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/processor/pom.xml b/processor/pom.xml
index 538237e7d..4f792da14 100644
--- a/processor/pom.xml
+++ b/processor/pom.xml
@@ -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>