On Tue, Aug 16, 2011 at 23:35, Jason Porter <span dir="ltr"><<a href="mailto:lightguard.jp@gmail.com">lightguard.jp@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#FFFFFF"><div>For my $0.02, I wish more people would split their runtime and compile time deps. Too often people add the runtime which pulls in the compile time and the user builds against the runtime classes. Part of this problem, imo, comes from maven resolving compile transitively. If you depend on it to compile, state it, and don't bleed your runtime into mine if it's swappable. I think Sonatype would probably agree. <br>
</div></div></blockquote><div><br></div><div>I agree that we want to promote best practices. I have yet to hear anyone say "two dependencies, that's so many!" They just copy and paste what we give them. So let's just give them the right thing to copy paste (or let forge do it).</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>