[
https://issues.apache.org/jira/browse/AXIS2-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694255#action_12694255
]
Jason Fager commented on AXIS2-4291:
------------------------------------
One of reasons to use maven is to get a more-or-less common way to perform
basic tasks across projects. Not allowing the standard -Dmaven.test.skip
property to do its thing, and substituting another property that basically does
the same thing, seems to work against this. It would be nice to see little
oddities like this phased out, to get the build as "standard" and easy to
understand as possible. Speaking as a newcomer to the project, little things
like this small little humps that don't have clear value but take time to
understand and work around, can be kind of frustrating,
> 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.
