Re: [hono-dev] [Proposal] Converting "site" folder into Maven sub-module

["Hudalla Kai (INST/ECS4)" <kai.hudalla@xxxxxxxxxxxx>]

On Mon, 2017-03-27 at 11:27 +0000, Maas Ingo (INST/ECS4) wrote:
> The intention is to have a complete Eclipse Hono build on a continuous
> integration system, including its documentation. Since the Hono build is
> controlled by Maven, converting the site to a Maven module sounds like a
> natural fit.
> 
Is there a particular reason why you cannot use the documentation provided on the
project website (which is built from master every night)?

Maybe you can provide a PR illustrating what you have in mind so that we we can
then see if and how it would affect deployment to the Eclipse environment. I'd
rather not make that process any more complicated :-)

> Kind regards, Ingo
> 
> ________________________________________
> Von: hono-dev-bounces@xxxxxxxxxxx <hono-dev-bounces@xxxxxxxxxxx> im Auftrag von
> Hudalla Kai (INST/ECS4) <kai.hudalla@xxxxxxxxxxxx>
> Gesendet: Montag, 27. März 2017 13:13
> An: hono-dev@xxxxxxxxxxx
> Betreff: Re: [hono-dev] [Proposal] Converting "site" folder into Maven sub-
> module
> 
> Hi,
> 
> On Mon, 2017-03-27 at 09:00 +0000, Maas Ingo (INST/ECS4) wrote:
> > Hi all,
> > 
> > currently, the source for the Hugo-based Hono documentation lives in a plain
> > folder "site" and includes the build script "build-site.sh" which in turn
> > refers to the Hugo executable.
> > 
> > We came up with the idea to convert the "site" folder to a Maven sub-module.
> > Thus, the site content would be build inside the regular Maven build process.
> > This would make the Hugo executable a prerequisite for building Hono.
> > 
> > Any thoughts are welcome.
> > 
> 
> While all of what you say is true, is there any reason for making this change,
> i.e. what advantage would you like to get out of it?
> The current process is built around the specifics of creating the site's
> content
> to be hosted at Eclipse and thus considers the Eclipse environment specifics
> which do not need nor require the site being built as a Maven module.
> 
> Maybe you can elaborate a little why you think it would be better to do it as
> part of the Maven build?
> 
> > Kind regards,
> > 
> > Ingo Maas
> > 
> > Bosch Software Innovations GmbH
> > INST/ECS4
> > Schöneberger Ufer 89 - 91
> > 10785 Berlin
> > GERMANY
> > www.bosch-si.de
> > 
> > Tel. +49 30 726112-156
> > Fax +49 30 726112-100
> > ingo.maas@xxxxxxxxxxxx
> > 
> > Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB
> > 148411 B
> > Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn
> > _______________________________________________
> > hono-dev mailing list
> > hono-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe from
> > this list, visit
> > https://dev.eclipse.org/mailman/listinfo/hono-dev
> 
> _______________________________________________
> hono-dev mailing list
> hono-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/hono-dev
> _______________________________________________
> hono-dev mailing list
> hono-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/hono-dev