<div class="gmail_quote">On Mon, Apr 18, 2011 at 13:23, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div class="im">On Sat, Apr 2, 2011 at 18:24, Lincoln Baxter, III <span dir="ltr"><<a href="mailto:lincolnbaxter@gmail.com" target="_blank">lincolnbaxter@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
As far as classifiers. I've been intentionally avoiding them because it adds a lot of complexity to the dependency API. What do you need?<br></blockquote><div><br></div></div><div>Regardless of whether you like classifiers in general, you can't ignore the fact that they are part of a dependency. You really need to support them or else the forge dep support is just incomplete.</div>
</div></blockquote><div><br></div><div>I agree that they are bad for distinguishing between two artifacts (like in the case of testng). The main intention for them is to reference complementary jars, like -source, -javadoc, etc. Of course, you don't need to add those as dependencies.</div>
<div><br></div><div>-Dan</div><div><br></div></div>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>
<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>