<div>I personally don't trust text files that claim to list library dependencies, as there's always a chance they are out-of-sync with build scripts. I just go straight to pom.xml or deploy instructions.</div><div class="gmail_extra">
<br></div><div class="gmail_extra">just my 2c</div><div class="gmail_extra"><br></div><div class="gmail_extra">- marko<br><br><div class="gmail_quote">On Mon, Nov 5, 2012 at 1:09 PM, Jay Balunas <span dir="ltr"><<a href="mailto:jbalunas@redhat.com" target="_blank">jbalunas@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi All,<br>
<br>
One thing we need to be sure to document is the details of our build process and dependencies for each of libraries and repos.<br>
<br>
The question is whether to centralize these or keep them with each of the respective repos? Thoughts?<br>
<br>
If we the repos we should adopt of specific convention for the files and the names. i.e. BUILD.md, and/or DEPENDENCIES.md.<br>
<br>
Wdyt?<br>
<br>
Thanks,<br>
Jay<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</blockquote></div><br></div>