|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
Wouldn't it be a good idea to move this logic from the branches (projects, plugins, ...) to a parent instead of updating each library you depend on or using customized profiles where you'll need to reference this system dependency? In this case maybe to the Maven project itself as the JDK is mandatory to use it?
Adding logic to the root maven project could remove duplicate or buggy retrieval algorithms and increase user friendliness. Of course this would mean that potentially every JDK release could trigger a Maven release. But this is implicitly already the case as you may have to update the retrieval logic whenever you switch to another JDK version.