[jira] [Updated] (MASSEMBLY-757) Warning complains that 'classifier' is missing, but getClassifier() always returns null

["Elliotte Rusty Harold (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MASSEMBLY-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold updated MASSEMBLY-757:
--------------------------------------------
    Priority: Minor  (was: Major)

> Warning complains that 'classifier' is missing, but getClassifier() always returns null
> ---------------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-757
>                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-757
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>            Reporter: Johannes Ernst
>            Priority: Minor
>
> Got Warning:
>     Configuration options: 'appendAssemblyId' is set to false, and 'classifier' is missing.
>     Instead of attaching the assembly file: ..., it will become the file for main project artifact.
> in spite of setting <classifier> (which coincidentally is marked as deprecated). Poking around the source code, I find in http://svn.apache.org/viewvc/maven/plugins/tags/maven-assembly-plugin-2.5.3/src/main/java/org/apache/maven/plugin/assembly/mojos/AbstractAssemblyMojo.java?view=markup:
>     763 public String getClassifier()
>     764 	{
>     765 	// TODO Auto-generated method stub
>     766 	return null;
>     767 	}
> So it seems to me that this warning is incorrect. Also, simply zeroing out a set, even deprecated field, seems not so nice, without any notice. I am puzzled by the auto-generated method stub though.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)