[jira] Commented: (AXIS2-4291) maven-surefire-plugin skip=true in parent, but skip=false in every other module

["Andreas Veithen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AXIS2-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694242#action_12694242 ] 

Andreas Veithen commented on AXIS2-4291:
----------------------------------------

I agree that this a very unusual approach and I don't know why this was done. On the other hand, you can still skip the tests manually using the following option:

-Dtest=false

(Actually any value other than false will have the same effect)

> maven-surefire-plugin skip=true in parent, but skip=false in every other module
> -------------------------------------------------------------------------------
>
>                 Key: AXIS2-4291
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4291
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: samples, build,site
>    Affects Versions: nightly
>            Reporter: Jason Fager
>             Fix For: nightly
>
>
> For every module except parent in the Axis2 project, in the build section of the pom, the maven-surefire-plugin's "skip" property is set to false, while in the parent it's set to true.  
> Why is this property set in the parent, only to be immediately overridden in every subproject?  As a result of the current configuration, its not possible to control whether tests are run or not using the usual -Dmaven.test.skip flag at the command line.
> This seems like it should be changed so that the parent does not specify skip=true, and so that none of the children specify skip=false.  This would return control back to the developer, to decide if they want to override tests at any point.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.