Uploaded image for project: 'Maven Assembly Plugin'
  1. Maven Assembly Plugin
  2. MASSEMBLY-1020

Cannot invoke "java.io.File.isFile()" because "this.inputFile" is null

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 3.7.0
    • 3.7.1
    • None
    • None

    Description

      We've switched from 3.6.0 to 3.7.0, and our assemblies are now failing with:

      [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single (assemblies) on project my-project: Execution assemblies of goal org.apache.maven.plugins:maven-assembly-plugin:3.7.0:single failed: Cannot invoke "java.io.File.isFile()" because "this.inputFile" is null -> [Help 1]
      

      Our configuration looks like this:

      <plugin>
                      <artifactId>maven-assembly-plugin</artifactId>
                      <executions>
                          <execution>
                              <id>assemblies</id>
                              <phase>package</phase>
                              <goals>
                                  <goal>single</goal>
                              </goals>
                              <configuration>
                                  <formats>
                                      <format>zip</format>
                                  </formats>
                                  <descriptors>
                                      <descriptor>src/main/assembly/component.xml</descriptor>
                                  </descriptors>
                              </configuration>
                          </execution>
                      </executions>
                  </plugin>
      

      And our descriptor looks like this:

      <assembly xmlns="http://maven.apache.org/ASSEMBLY/2.0.0"
                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.0.0 http://maven.apache.org/xsd/assembly-2.0.0.xsd">
      
          <id>component</id>
          <includeBaseDirectory>false</includeBaseDirectory>
      
          <fileSets>
              <fileSet>
                  <directory>${resources.dir}/config</directory>
                  <outputDirectory>.</outputDirectory>
              </fileSet>
          </fileSets>
      </assembly>
      

      Our resources folder just contains a few text files.

      I assume it's related to changes brought in on MASSEMBLY-1013

      Attachments

        Issue Links

          Activity

            People

              sjaranowski Slawomir Jaranowski
              bengineer Ben Middleton
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: