You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jody Garnett (Jira)" <ji...@apache.org> on 2020/03/05 03:33:00 UTC

[jira] [Created] (MASSEMBLY-930) Assembly FileSet and Files do no consistently handle -f directory location

Jody Garnett created MASSEMBLY-930:
--------------------------------------

             Summary: 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: Task
         Environment: * macOS (development machine) using maven 3.6.0
* Unbuntu (build server)
            Reporter: Jody Garnett


We have observed fileSet and file handling of relative paths 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}

 * fileSet directory - path based on location of pom.xml, working with no matter how -f is used to start the build
 * file source - path based on where mvn executable is run, ignoring -f subdirectory location

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)