[
https://issues.apache.org/jira/browse/MSHADE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17446907#comment-17446907
]
Gili commented on MSHADE-269:
-----------------------------
[~clebertsuconic] I don't understand. You wrote:
> creating this sort of dependencies between projects will probably cause more
> harm than good.
What sort of dependencies? When someone builds a project, and it uses shade to
rewrite its own JAR then I believe this issue is asking to rewrite
target/classes as well. We are not talking about rewriting other projects but
rather our own. So what "dependencies between projects" are we creating that
don't already exist?
> Ability to replace also target/classes with modified classes
> ------------------------------------------------------------
>
> Key: MSHADE-269
> URL: https://issues.apache.org/jira/browse/MSHADE-269
> Project: Maven Shade Plugin
> Issue Type: Improvement
> Reporter: Ivan Balashov
> Priority: Major
>
> Relocated classes are only included into artifact jar bypassing module's
> target / classes directory. IDEs pick up unmodified classes which is
> undesirable.
> Following the corresponding Intellij Idea Issue:
> [https://youtrack.jetbrains.com/issue/IDEA-93855]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
