[GitHub] [maven-compiler-plugin] psiroky commented on pull request #170: [MCOMPILER-503] Resolve all annotation processor dependencies together

["psiroky (via GitHub)" <gi...@apache.org>]

psiroky commented on PR #170:
URL: https://github.com/apache/maven-compiler-plugin/pull/170#issuecomment-1399628965

   I would like to create a test for this, but I am not sure which approach to take. Unit testing this seems somewhat not-relevant, since all the code does is calling maven-resolver, which does the actual heavy lifting.
   
   Creating an integration test project is pretty easy, but how do I for example verify, that duplicated dependencies are not on processor path? Parsing he debug (-X) Maven output (where the modulepath elements are listed) seems pretty brittle. Is there a better way to do this?
   
   And one more question related to ITs, and the dependencies they use: is it OK to depend on a third party dep (say junit) in the IT projects? Those deps would need to be downloaded from Maven central at runtime (test time). I noticed there are ITs doing that, but I would like to clarify if that's just an oversight, or a proper way of writing the tests (since `maven-integration-testing` seems to be a bit more strict on how the dependencies can be used by tests).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org