5214 notes that Maven will incorrectly resolve type=wsdl to target/classes of a project of type jar.
Fixing that broke 3 integration tests. Reading the JIRAs for those tests (3043, 4065, 2871), the upshot is that decisions were made to relax the matching rules for cases where the bug authors and Maven maintainers 'knew' that the contents of the classifier jars were identical to, at least close to, the contents of the output of compile or test-compile. Perhaps needless to say that it would be good to at least find a place to configure this behavior other than the Java source of the ReactorReader. 4065 dealt with jar versus test-jar in type: I added a special case to ReactorReader. The other two add in ejb client jars to the mixture. It looks like a need a similar treatment for jar versus ejb-client to preserve compatibility here. However, in 3043, the consumer leaves out the classifier from the dependency specification. Is anyone willing to explain why that bit of relaxation was considered a good idea? My inclination would be to change the test to specify the classifier. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
