[ https://issues.apache.org/jira/browse/SUREFIRE-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15559520#comment-15559520 ]
Tibor Digana commented on SUREFIRE-1292: ---------------------------------------- [~ittaiz] Definitely using slash and ".java" was bad decision. I was not in ASF when this happened but certainly the people made technocratic decision that the pattern required by {{maven-shared-utils}} was propagated in Surefire. Unfortunately I cannot do anything about it and I do not want to messup the pattern with other file extension. I would rather deprecate this pattern and use {{com.**.MyTest}} in natural form of fully qualified class name normally known by developer. > Includes misbehaves with extensions other than java > --------------------------------------------------- > > Key: SUREFIRE-1292 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1292 > Project: Maven Surefire > Issue Type: Bug > Reporter: Ittai Zeidman > > Hi, > When defining an <include> for maven failsafe plugin it ignores ones with > file endings other than java. See this report for groovy > (https://prometheuscomputing.com/company_site/blogs/26) and I had the same > for scala. > basically > <includes> > <include>**/*E2E.scala</include> > </includes> > doesn't run a test which sits in FooE2E.scala but this > <includes> > <include>**/*E2E.java</include> > </includes> > does run the scala test -- This message was sent by Atlassian JIRA (v6.3.4#6332)