[
https://issues.apache.org/jira/browse/MASSEMBLY-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MASSEMBLY-930:
-------------------------------------
Issue Type: Bug (was: Task)
> Assembly FileSet and Files do no consistently handle -f directory location
> --------------------------------------------------------------------------
>
> Key: MASSEMBLY-930
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-930
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Environment: * macOS (development machine) using maven 3.6.0
> * Unbuntu (build server)
> Reporter: Jody Garnett
> Priority: Major
> Fix For: waiting-for-feedback
>
>
> We have observed fileSet and file handling of relative paths in an
> inconsistent fashion when using mvn -f command line option to run a pom.xml
> file in a subdirectory.
> {panel:title=current directory}
> cd src
> mvn assembly:attached
> {panel}
> {panel:title=subdirectory location}
> mvn -f src/pom.xml assembly:attached
> {panel}
> Inconsistent behaviour:
> * fileSet directory - path based on location of pom.xml
> Works with both current directory, or subdirectory location, approach
> above.
> * file source - path based on where mvn executable is run, ignoring -f
> subdirectory location
>
> Impossible to define assembly independently of how maven is run (choose
> one of current directory or subdirectory approach).
> For the following example of file release/extensions/LICENSE.txt:
> {code:xml}
> <file>
> <source>release/extensions/LICENSE.txt</source>
> <outputDirectory></outputDirectory>
> <destName>LICENSE-LGPL.txt</destName>
> </file>
> {code}
> Running with "cd src" "mvn assembly:attached" succeeds:
> * src/release/extensions/LICENSE.txt
> Running from the root folder with "mvn -f src/pom.xml assembly:attached"
> fails with:
> * release/extensions/LICENSE.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
