Use Case: Project A - commons, includes annotations used during build process for packaging metadata
Project B - depends on Project A, only needed during build process, its AnnotationProcessorFactory interacts with A's annotations to create packaging metadata Project C - contains classes which are tagged with A's annotations I would like to use apt-maven-plugin to generate packaging metadata for Project C. I don't want my consumer's to see Project B as a transitive dependency since it is only needed during the build process. ------------------------------------------------------------------------------------------------------------- In Project C's POM, what is the best way to configure Project B to be on apt's classpath yet not appear as a transitive dependency for C's consumers? ---------------------------------------------------------------------- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
