maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MRESOURCES-158) outputDirectory is marked as mandatory whereas it is not really mandatory
Date Wed, 01 Feb 2012 18:55:02 GMT

    [ https://jira.codehaus.org/browse/MRESOURCES-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290512#comment-290512
] 

Robert Scholte commented on MRESOURCES-158:
-------------------------------------------

Mandatory has nothing to do with default values. If you empty a mandatory parameter, the build
should fail.

                
> outputDirectory is marked as mandatory whereas it is not really mandatory
> -------------------------------------------------------------------------
>
>                 Key: MRESOURCES-158
>                 URL: https://jira.codehaus.org/browse/MRESOURCES-158
>             Project: Maven 2.x Resources Plugin
>          Issue Type: Bug
>    Affects Versions: 2.5
>            Reporter: Jorg Heymans
>
> in the documentation and plugin descriptor the outputDirectory config element is marked
as mandatory. But since there is a default value of ${project.build.outputDirectory} this
element is not really mandatory. Other configuration elements with the same default value
semantics are not marked as mandatory so i think for outputDirectory the same semantics should
be applied.
> this is especially troublesome for ideas that try to assist in maven configuration and
rely on the plugin descriptor to figure out if elements are mandatory or not. See http://youtrack.jetbrains.net/issue/IDEA-80626

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message