You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2019/02/03 20:36:00 UTC
[jira] [Commented] (SUREFIRE-1635) Set properties readonly where it
doesn't make sense to change values
[ https://issues.apache.org/jira/browse/SUREFIRE-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759522#comment-16759522 ]
Tibor Digana commented on SUREFIRE-1635:
----------------------------------------
The following parameters {{projectBuildDirectory}}, {{pluginDescriptor}}, {{defaultClassesDirectory}} are marked {{required=true}} in version {{3.0.0-M4}}.
These parameters are marked readonly and required {{remoteRepositories}}, {{basedir}} in version {{3.0.0-M4}}.
Other parameters will be considered and possibly break backwards compatibility in {{3.0.0-M5}}.
> Set properties readonly where it doesn't make sense to change values
> --------------------------------------------------------------------
>
> Key: SUREFIRE-1635
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1635
> Project: Maven Surefire
> Issue Type: Improvement
> Components: documentation
> Reporter: Benedikt Ritter
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.0.0-M4
>
>
> It doesn't make sense for a user to change the values of {{remoteRepository}}, {{basedir}} and {{testSourceDirectory}}. These values are all configured on the project level. Furthermore I've removed the {{required}} from {{testSourcesDirectory}} since it has a default value and is now readonly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)