Whats the downside of keeping failsafe instead of reverting to surefire? If there are no obvious differences between the two we can continue using failsafe.
I will remove the base tests from the failsafe profile JC 2011/2/25 Jörn Kottmann (JIRA) <dev@uima.apache.org> > > [ > https://issues.apache.org/jira/browse/UIMA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999427#comment-12999427] > > Jörn Kottmann commented on UIMA-2076: > ------------------------------------- > > We should consider using surefire again, since failsafe does not solve the > issue we had with surefire. What do you think? > > We should also exclude the Basic test since, that is run twice if the > extended-test profile is activated. > > > Modify maven-failsafe-plugin in uimaj-as-activemq pom.xml to use UTF-8 > encoding > > > -------------------------------------------------------------------------------- > > > > Key: UIMA-2076 > > URL: https://issues.apache.org/jira/browse/UIMA-2076 > > Project: UIMA > > Issue Type: Bug > > Components: Async Scaleout > > Reporter: Jerry Cwiklik > > Assignee: Jerry Cwiklik > > Priority: Trivial > > Fix For: 2.3.1AS > > > > > > The maven-safefail-plugin in uima-as-activemq pom.xml does not set UTF-8 > encoding. This causes a WARNING: > > File encoding has not been set, using platform encoding {default > encoding} > > when maven runs extended tests on Apple OS and linux. On Mac the default > encoding seems to be: MacRoman > > > > Modify failsafe-plugin to use UTF-8 encoding. > > -- > This message is automatically generated by JIRA. > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > >
