How to stop maven from output "[WARNING] Configuration option 'appendAssemblyId' is set to false."?

Question

I have a maven project generating a jar and not appending maven-assembly-plugin's appendAssemblyId.

How can I get maven to stop issuing the warning: "Configuration option 'appendAssemblyId' is set to false." ?

EDIT: I was asked to include the pom file, which I'm not permitted to do. I'm including the maven-assembly-plugin block which causes the error.

<plugin>
  <artifactId>maven-assembly-plugin</artifactId>
  <configuration>
    <archive>
      <manifest>
        <mainClass>some.company.hello</mainClass>
      </manifest>
    </archive>
    <descriptorRefs>
      <descriptorRef>jar-with-dependencies</descriptorRef>
    </descriptorRefs>
    <!-- prevent appending <descriptorRef> "jar-with-dependencies" to final jar name -->
    <appendAssemblyId>false</appendAssemblyId>
  </configuration>
  <executions>
    <execution>
      <!-- For inheritance merges -->
      <id>make-assembly</id>
      <!-- bind to the packaging phase -->
      <phase>package</phase> 
      <goals>
        <goal>single</goal>
      </goals>
    </execution>
  </executions>
</plugin>    

Answer 1

This answer explains the technical details, but I think the key is the phrase that you mentioned in your question.

I have a maven project generating a jar and not appending maven-assembly-plugin's appendAssemblyId.

If I'm understanding correctly, I take this to mean that in your pom file, you have an entry that says

    <packaging>jar</packaging>

What this does is create a jar file that competes with the output of the maven-assembly-plugin, and maven-assembly-plugin wins out, resulting in only one jar file. In fact, if you were to set appendAssemblyId back to true, you will get two files in the output directory - <artifact>.jar and <artifact>-jar-with-dependencies.jar.

So, first, you should remove the <packaging> tag I mentioned above, and add the following to the <executions> section of your pom file so that there won't be two conflicting/competing jar files (and the warning will go away):

<execution>
    <id>default-jar</id>
    <phase>none</phase>
</execution>