[ https://issues.apache.org/jira/browse/MSHADE-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17517234#comment-17517234 ]
James Z.M. Gao commented on MSHADE-124: --------------------------------------- as comment in MSHAD-160 said, we can leave the basedir unchanged using maven 3.2.5 api `MavenProject::setPomFile`, plz review the pr https://github.com/apache/maven-shade-plugin/pull/128 > 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)