[aerogear-dev] Details on the build process and dependencies

Corinne Krych corinnekrych at gmail.com
Mon Nov 5 10:34:06 EST 2012


Hello all,

Just to jump in the discussion
    maven dependency:tree
is well-known I think but just add it to the technical doc of the project.

On a more general topic on documentation, I think it will be good to use
gh-pages.
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 :
http://3musket33rs.github.com/
and for one project
http://3musket33rs.github.com/html5-mobile-scaffolding/
Besides with gh-pages you can have templates or you could use miven site
report. In my sample I used Grails doc report.

Just to share with you my views...

Cheers,
Corinne.

On 5 November 2012 15:44, Lucas Holmquist <lholmqui at redhat.com> wrote:

>
> On Nov 5, 2012, at 9:41 AM, Summers Pittman <supittma at redhat.com> wrote:
>
> >> Would a new user know how to do that?  maybe a guide to show them how
> > 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.
> > New users won't care what their deps are because Maven will download and
> build against what it needs automatically.
> >
>
> right,  i was referring to actually generating the dependency tree/list
>
>
> > ----- Origina
> > l Message -----
> > From: "Lucas Holmquist" <lholmqui at redhat.com>
> > To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> > Sent: Monday, November 5, 2012 9:35:03 AM
> > Subject: Re: [aerogear-dev] Details on the build process and dependencies
> >
> >
> > On Nov 5, 2012, at 9:32 AM, Summers Pittman <supittma at redhat.com> wrote:
> >
> >> For Android this is kind of a non issue.  The dependency tree/list can
> be generated from the pom file any time.
> >>
> >
> >> Would a new user know how to do that?  maybe a guide to show them how
> >
> >
> >> ----- Original Message -----
> >> From: "Jay Balunas" <jbalunas at redhat.com>
> >> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> >> Sent: Monday, November 5, 2012 7:09:13 AM
> >> Subject: [aerogear-dev] Details on the build process and dependencies
> >>
> >> Hi All,
> >>
> >> One thing we need to be sure to document is the details of our build
> process and dependencies for each of libraries and repos.
> >>
> >> The question is whether to centralize these or keep them with each of
> the respective repos?  Thoughts?
> >>
> >> If we the repos we should adopt of specific convention for the files
> and the names.  i.e. BUILD.md, and/or DEPENDENCIES.md.
> >>
> >> Wdyt?
> >>
> >> Thanks,
> >> Jay
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20121105/65cff324/attachment.html 


More information about the aerogear-dev mailing list