<pre></pre>Hello all,<br><br>Just to jump in the discussion<br> maven dependency:tree<br>is well-known I think but just add it to the technical doc of the project.<br><br>On a more general topic on documentation, I think it will be good to use gh-pages. <br>
You could have a general page for AeroGear which list all project and then have gh-pages documentation per project. This is how I presented it :<br><a href="http://3musket33rs.github.com/">http://3musket33rs.github.com/</a><br>
and for one project<br><a href="http://3musket33rs.github.com/html5-mobile-scaffolding/">http://3musket33rs.github.com/html5-mobile-scaffolding/</a><br>Besides with gh-pages you can have templates or you could use miven site report. In my sample I used Grails doc report.<br>
<br>Just to share with you my views...<br><br>Cheers,<br>Corinne.<br><br><div class="gmail_quote">On 5 November 2012 15:44, Lucas Holmquist <span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.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="im"><br>
On Nov 5, 2012, at 9:41 AM, Summers Pittman <<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>> wrote:<br>
<br>
>> Would a new user know how to do that? maybe a guide to show them how<br>
> Dependency management is just something Maven "does". I've written (and am waiting on the PR to go through) gobs of docs on how to get this set up.<br>
> New users won't care what their deps are because Maven will download and build against what it needs automatically.<br>
><br>
<br>
</div>right, i was referring to actually generating the dependency tree/list<br>
<br>
<br>
> ----- Origina<br>
<div class="HOEnZb"><div class="h5">> l Message -----<br>
> From: "Lucas Holmquist" <<a href="mailto:lholmqui@redhat.com">lholmqui@redhat.com</a>><br>
> To: "AeroGear Developer Mailing List" <<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
> Sent: Monday, November 5, 2012 9:35:03 AM<br>
> Subject: Re: [aerogear-dev] Details on the build process and dependencies<br>
><br>
><br>
> On Nov 5, 2012, at 9:32 AM, Summers Pittman <<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>> wrote:<br>
><br>
>> For Android this is kind of a non issue. The dependency tree/list can be generated from the pom file any time.<br>
>><br>
><br>
>> Would a new user know how to do that? maybe a guide to show them how<br>
><br>
><br>
>> ----- Original Message -----<br>
>> From: "Jay Balunas" <<a href="mailto:jbalunas@redhat.com">jbalunas@redhat.com</a>><br>
>> To: "AeroGear Developer Mailing List" <<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
>> Sent: Monday, November 5, 2012 7:09:13 AM<br>
>> Subject: [aerogear-dev] Details on the build process and dependencies<br>
>><br>
>> 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>
><br>
><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>
> _______________________________________________<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>
<br>
<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>
</div></div></blockquote></div><br>