Much as I hate to distract people from the fun of arguing over logging packages, I have another topic.
Say that you have an item that you want reactor support for -- that is, you want to produce it over 'here', and consume it over 'there' in the build. For this to work, it has to be in the dependency list over there. This leads to a small puzzle of coordinate selection. The case I'm looking at is the license-maven-plugin, where I want to improve on its ability to produce and consume knowledge about the licenses of components. Tony's existing work has used type=properties for these files, because they are, of course, property files. However, there are many properties files in the world, and only a few contain this license data. So, the code uses a convention for classifier. My question is; would it have been better to use type=license.properties instead? Are there any reasons to prefer one approach over the other? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
