The test name was not the issue, though not keeping with the pattern is, e.g. `mng-5530-blah-blah-blah` if you must but not `mng5530-blah-blah-blah` as all the other tests start with `mng-` so they are sorted consistently
The real issue was that the test case itself broke when I switched the Maven version from 3.1.2-SNAPSHOT to 3.2.0-SNAPSHOT because the tests run in a clean repository and there is thus no 3.1.2-SNAPSHOT artifacts to resolve for the plugin side of the test case On 6 January 2014 12:51, Igor Fedorenko <[email protected]> wrote: > Stephen, > > I would prefer to keep the original test name, i.e. > mng5530-mojo-execution-scope. Having both the JIRA issue id and short > description of the test makes it much easier to understand what the test > is supposed to do and still be able to find any additional information > if needed. > > Can you explain what problems you see with the original test name? > > https://git-wip-us.apache.org/repos/asf?p=maven-integration- > testing.git;a=commit;h=d4f4d4009d23a77254c20d4c2c8a2b8eccc91e47 > > -- > Regards, > Igor > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
