[
https://issues.apache.org/jira/browse/MNG-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225718#comment-16225718
]
Juan Farré commented on MNG-1867:
---------------------------------
My only two use cases for system scope are the well-known tools.jar and getting
rid of transitive dependencies which are now incluided in the JRE.
Many maven artifacts carry transitive dependencies en compile scope with things
like XML API, JAXB, and many other JAR's which are included in JRE 7.
I usually manage these dependencies setting system scope to rt.jar so that they
are not included when packaging (this could be achieved with scope provided),
nor when compiling or testing.
I don't see the alternative, unless I take the huge work of adding the
exclusions.
Is there an alternative for this use case? What do you suggest?
By the way, all these rt.jar dependencies fail with JRE 9 and I do not even
know how to fix them. Luckily, not using Java 9 in any project, yet...
> deprecate system scope, analyse other use cases
> -----------------------------------------------
>
> Key: MNG-1867
> URL: https://issues.apache.org/jira/browse/MNG-1867
> Project: Maven
> Issue Type: Task
> Components: Artifacts and Repositories, Design, Patterns & Best
> Practices
> Reporter: Brett Porter
> Priority: Trivial
> Fix For: Issues to be reviewed for 4.x
>
> Attachments: MNG-1867.zip
>
>
> possibly can avoid all use cases for system scope through proper use of
> alternate resolvers. Gather use cases (see MNG-1471) to ensure.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
