On Thu, 2017-10-05 at 10:58 +0300, Robert Munteanu wrote:
> On Wed, 2017-10-04 at 18:28 +0200, Konrad Windszus wrote:
> > Sorry, I missed the point that web sites can only be published if
> > the
> > source files are in Git [1].
> > If I understand correctly the only thing that the maven-scm-
> >
On Wed, 2017-10-04 at 18:28 +0200, Konrad Windszus wrote:
> Sorry, I missed the point that web sites can only be published if the
> source files are in Git [1].
> If I understand correctly the only thing that the maven-scm-publish-
> plugin would do is committing the target site to the asf-branch
Sorry, I missed the point that web sites can only be published if the source
files are in Git [1].
If I understand correctly the only thing that the maven-scm-publish-plugin
would do is committing the target site to the asf-branch (what we currently
need to do manually).
So for me 1 & 2 are not
On Wed, Oct 4, 2017 at 12:16 PM, Konrad Windszus wrote:
> ...Once we fixed all bugs in our templates, the diff on the MD source files
> is IMHO enough...
You forgot the tag ;-)
Templates will evolve "forever", we might upgrade JBake, use a
different JDK which exposes
On Wed, 2017-10-04 at 12:16 +0200, Konrad Windszus wrote:
> > On 4. Oct 2017, at 12:11, Bertrand Delacretaz > rg> wrote:
> >
> > On Wed, Oct 4, 2017 at 12:07 PM, Konrad Windszus
> > wrote:
> > > ...I prefer 2 to not pollute the Sling Site Git repo with
>
> On 4. Oct 2017, at 12:11, Bertrand Delacretaz wrote:
>
> On Wed, Oct 4, 2017 at 12:07 PM, Konrad Windszus wrote:
>> ...I prefer 2 to not pollute the Sling Site Git repo with generated
>> artifacts...
>
> But it's *very* useful to be able to see the
On Wed, Oct 4, 2017 at 12:07 PM, Konrad Windszus wrote:
> ...I prefer 2 to not pollute the Sling Site Git repo with generated
> artifacts...
But it's *very* useful to be able to see the diffs of the published
content before pushing them live.
-Bertrand
I prefer 2 to not pollute the Sling Site Git repo with generated artifacts.
But even with 2 we should have an according Jenkins Job which executes this
Maven Build & Deploy automatically.
> On 2. Oct 2017, at 21:33, Robert Munteanu wrote:
>
> Hi,
>
> I think we can
Hi,
I think we can simplify the site publishing setup and it should be
enough to work only on the master branch.
I see two possible options:
1) Set up a Jenkins job to rebuild the site and push automatically .
This _should_ be possible based on [1]
2) Configure the maven-scm-publish-plugin to