[
https://issues.apache.org/jira/browse/MSHADE-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519869#comment-17519869
]
Alexander Kriegisch edited comment on MSHADE-124 at 4/9/22 4:44 AM:
--------------------------------------------------------------------
Like I said several times, both here and in MSHADE-145: The supposed blocker
problem does not exist! Maybe it used to, but this issue here can be
implemented without any problems or need for "better plan". Someone just
claimed without any proof that there was a potential problem, and even that
information was hearsay.
If there is infact a problem which I never found in my own research I
documented in MSHADE-145, maybe someone can come up with proof, e.g. a failing
integration test or so.
was (Author: kriegaex):
Like I said several times, both here and in MSHADE-145: The supposed blocker
problem does not exist! Maybe it used to, but this issue here can be
implemented without any problems or need for "better plan". Someone just
claimed without any proof that there was a potential problem, and even that
information was hearsay.
> Need better plan for getting dependency-reduced-pom.xml out of basedir
> ----------------------------------------------------------------------
>
> Key: MSHADE-124
> URL: https://issues.apache.org/jira/browse/MSHADE-124
> Project: Maven Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.7.1
> Reporter: Benson Margulies
> Priority: Major
>
> MSHADE-123 reported that putting the d-r-p into some location other
> than 'basedir' causes 'basedir' to follow it around, which can break builds.
> This is hard to fix, given the core maven definition of basedir as 'the dir
> containing the pom' with no option to change it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
