You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Michael Vorburger (Jira)" <ji...@apache.org> on 2019/12/02 01:10:00 UTC
[jira] [Commented] (FINERACT-777) Use api / implementation instead
of compile scoped dependencies
[ https://issues.apache.org/jira/browse/FINERACT-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16985738#comment-16985738 ]
Michael Vorburger commented on FINERACT-777:
--------------------------------------------
[https://github.com/apache/fineract/pull/661] did this (or at least made a start at it; possible future clean up can always be done later).
> Use api / implementation instead of compile scoped dependencies
> ---------------------------------------------------------------
>
> Key: FINERACT-777
> URL: https://issues.apache.org/jira/browse/FINERACT-777
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Michael Vorburger
> Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> as suggested on [https://discuss.gradle.org/t/how-to-add-dependencies-for-jaxb-and-jaf-when-migrating-from-java-8-to-java-11/32266/,] it would be much better if we used api / implementation instead of compile scoped dependencies.
> This would hel to avoid confusions such as e.g. [https://github.com/apache/fineract/pull/606], and more generally lead to a much cleaner classpath. (See also https://github.com/apache/fineract/pull/601.)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)