maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [maven-compiler-plugin] eolivelli commented on issue #1: [MCOMPILER-320] Introduce additionalClasspathElements property
Date Sat, 02 Nov 2019 10:57:16 GMT
eolivelli commented on issue #1: [MCOMPILER-320] Introduce additionalClasspathElements property
URL: https://github.com/apache/maven-compiler-plugin/pull/1#issuecomment-549032689
 
 
   Thank you @rfscholte for giving me the pointer, I should have read the full JIRA before
jumping on this train.
   In the mid term we want to be able to let Maven understand dependencies between mojos/tasks
execution (input/output). 
   I agree that we should leverage as most as possible the Project Model and so the 'dependecies'
feature.
   With this change we will add out-of-band dependencies additions and it smells like an hack.
   
   Initially I was driven in my LGTM by the needs of @dmlloyd but we should think about the
future and every feature we add now we have to maintain it for ever.
   I am sorry that surefire already provides this feature.
   
   If I understand correctly we should try to convert the original problem to an integration
test and see if there is really no other way to achieve the same goal.
   
   I don't know if is possible to build an 'extension' that changes the dependencies at build
time instead of forking the plugin

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message