[
https://jira.codehaus.org/browse/MOJO-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282762#comment-282762
]
Ian Robertson commented on MOJO-1767:
-------------------------------------
Good points. I placed the parser file in src/test/java per the instructions
http://maven.apache.org/plugins/maven-invoker-plugin/examples/access-test-classes.html.
I can see two routes to reduce the confusion you mention:
* One would be to package the class in something like
org.codehaus.mojo.integrationTests (or ...it or ...integrationtests).
* A second would be to rename src/test/java to src/it/java. However, this would
break maven conventions, and probably cause more confusion than it would save.
On the class name front, I agree completely. How about DuplicateClassLogParser?
> Improve integration-test for MOJO-1744
> --------------------------------------
>
> Key: MOJO-1767
> URL: https://jira.codehaus.org/browse/MOJO-1767
> Project: Mojo
> Issue Type: Improvement
> Components: extra-enforcer-rules
> Reporter: Robert Scholte
> Priority: Minor
> Attachments: LogParser.java, mojo-1744.it.2.patch
>
>
> With MOJO-1744 we have support for ignoring classes for specific dependencies.
> However, the IT seems unstable due to the usage of HashMaps (unpredictable
> order).
> The IT needs an improvement by ignoring the order, though every entry must be
> verified.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
