Igor Fedorenko wrote:
Yes, parity between m2e and maven cli is high priority for us. Classifier=tests makes test classes/resources visible to dependent projects both in m2e and cli, so your scenario should work. Are there reasons you cannot or prefer not to use tests classifier?
do you mean classifer=test or scope=test? In my solution I didn't have to create separate modules with resources imported with scope=test. CLI was totally irrelevant for me (I'm not using those resources in tests, rather in utility classes).
I probably rework my project (create separate modules for test only dependencies) so it is more elegant and CLI friendly.
Thanks. -- Leszek Gawron --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
