You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alexander Kriegisch (Jira)" <ji...@apache.org> on 2021/05/25 01:53:00 UTC
[jira] [Commented] (MSHADE-124) Need better plan for getting
dependency-reduced-pom.xml out of basedir
[ https://issues.apache.org/jira/browse/MSHADE-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350721#comment-17350721 ]
Alexander Kriegisch commented on MSHADE-124:
--------------------------------------------
Hello, is anybody still maintaining this plugin? I waited for one month, but no reaction neither to my ananlyis in MSHADE-145 nor here. Like I said, I think there is no blocking issue, it is just a phantom. We should stop using it as an excuse not to implement this change. IMO the "better plan" is just to implement it and test if it works. I did test it and had no issues across Java, Maven and Shade versions.
> 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.3.4#803005)