[
https://issues.apache.org/jira/browse/MSHADE-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17331518#comment-17331518
]
Alexander Kriegisch edited comment on MSHADE-124 at 4/9/22 4:45 AM:
--------------------------------------------------------------------
If this has ben an issue for 9 years, maybe some new ideas would help? I use
Maven Flatten Plugin in order to create POMs not unlike the dependency-reduced
POMs created by Maven Shade POM. I am unaware of any issues, placing them into
the build output directory (usually {{target}} like this:
{code:xml}
<outputDirectory>${project.build.directory}</outputDirectory>
<flattenedPomFilename>flattened-pom.xml</flattenedPomFilename>
{code}
Maybe a MSHADE maintainer wants to take a look at how Maven Flatten does that.
was (Author: kriegaex):
If this has ben an issue for 9 years, maybe some new ideas would help? I use
Maven Flatten Plugin in order to create POMs not unlike the dependency-reduced
POMs created by Maven Shade POM. I am unaware of any issues, placing them into
the build output directory (usually {{target}} like this:
{code:xml}
<outputDirectory>${project.build.directory}</outputDirectory>
<flattenedPomFilename>flattened-pom.xml</flattenedPomFilename>
{code}
Maybe an MSHADE maintainer wants to take a look at how Maven Flatten does that.
> 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)
