Return-Path: 
 <dev-return-1725-apmail-creadur-dev-archive=creadur.apache.org@creadur.apache.org>
X-Original-To: apmail-creadur-dev-archive@www.apache.org
Delivered-To: apmail-creadur-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id BFB80D864
	for <apmail-creadur-dev-archive@www.apache.org>;
 Sat, 17 Nov 2012 21:31:04 +0000 (UTC)
Received: (qmail 26347 invoked by uid 500); 17 Nov 2012 21:31:04 -0000
Delivered-To: apmail-creadur-dev-archive@creadur.apache.org
Received: (qmail 26314 invoked by uid 500); 17 Nov 2012 21:31:04 -0000
Mailing-List: contact dev-help@creadur.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@creadur.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@creadur.apache.org>
List-Post: <mailto:dev@creadur.apache.org>
List-Id: <dev.creadur.apache.org>
Reply-To: dev@creadur.apache.org
Delivered-To: mailing list dev@creadur.apache.org
Received: (qmail 26306 invoked by uid 99); 17 Nov 2012 21:31:04 -0000
Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 Nov 2012 21:31:04 +0000
Received: from localhost (HELO mail-lb0-f170.google.com) (127.0.0.1)
  (smtp-auth username olamy, mechanism plain)
  by minotaur.apache.org (qpsmtpd/0.29) with ESMTP;
 Sat, 17 Nov 2012 21:31:04 +0000
Received: by mail-lb0-f170.google.com with SMTP id j14so3055073lbo.29
        for <dev@creadur.apache.org>; Sat, 17 Nov 2012 13:31:02 -0800 (PST)
Received: by 10.152.145.169 with SMTP id sv9mr7841313lab.2.1353187861985; Sat,
 17 Nov 2012 13:31:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.76.231 with HTTP; Sat, 17 Nov 2012 13:30:41 -0800 (PST)
In-Reply-To: <50A7DFBF.30301@blueyonder.co.uk>
References: <505F712D.2000904@apache.org> <50968661.4030901@blueyonder.co.uk>
 <50969D44.5080309@apache.org> <509824A9.6040102@blueyonder.co.uk>
 <50996E21.30907@apache.org> <50997345.3070500@blueyonder.co.uk>
 <CAPoyBqRgy44DA=6SPxEbsTtNKbdpymO880yj+815d6wutJWdOA@mail.gmail.com>
 <50A54CED.8070307@blueyonder.co.uk>
 <CAPoyBqQmsHywrj2KRhNZ5qQkVpJtHO3CsqeG8xp0h5ay_dRQrw@mail.gmail.com>
 <50A7DFBF.30301@blueyonder.co.uk>
From: Olivier Lamy <olamy@apache.org>
Date: Sat, 17 Nov 2012 22:30:41 +0100
Message-ID: 
 <CAPoyBqR7czvNHke_gykEv+T4-8tm=fpkUhpUprLTCe42MFS6AA@mail.gmail.com>
Subject: Re: Maven SCM Publish Plugin WAS Re: Release Rat ...? [WAS Re:
 [DISCUSS] Minimum version of Maven to use the Rat plugin]]
To: dev@creadur.apache.org
Content-Type: text/plain; charset=ISO-8859-1

2012/11/17 Robert Burrell Donkin <robertburrelldonkin@blueyonder.co.uk>:
> On 11/15/12 22:03, Olivier Lamy wrote:
>>
>> 2012/11/15 Robert Burrell Donkin<robertburrelldonkin@blueyonder.co.uk>:
>>>
>>> On 11/06/12 21:46, Olivier Lamy wrote:
>>>>
>>>>
>>>> 2012/11/6 Robert Burrell Donkin<robertburrelldonkin@blueyonder.co.uk>:
>>>>>
>>>>>
>>>>> On 11/06/12 20:08, Dennis Lundberg wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 2012-11-05 21:42, Robert Burrell Donkin wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 11/04/12 16:52, Dennis Lundberg wrote:
>>>
>>>
>>>
>>> <snip>
>>>
>>>>>> There is a plugin called "Maven SCM Publish Plugin" [1], of which
>>>>>> version 1.0-beta-2 has just been released. The purpose of it is to
>>>>>> publish a Maven generated site to any supported SCM, such as the ASF
>>>>>> new
>>>>>> svnpubsub model for publishing sites. I haven't tried it myself yet.
>>>>>>
>>>>>> [1] http://maven.apache.org/plugins/maven-scm-publish-plugin/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Anyone have a few cycles to give this a try?
>>>>
>>>>
>>>> I use it for Apache projects (Archiva, Directmemory, helix incubator)
>>>> and works fine.
>>>
>>>
>>>
>>> I've given it a spin, and it seems to work okay. Takes a while, but then
>>> so
>>> does CMS upload. There seem to be a lot of commit messages.
>>>
>>> Is this a known limitation, or am I doing something wrong...?
>>
>> no and no :-)
>
>
> :-)
>
>> javadoc files can be timestamped so recommitted again with site build
>> even if no real content change.
>> maven generated files too but only at day level whereas javadoc seconds
>> level.
>
>
> So... would setting notimestamp on the javadoc plugin be a good idea...?
Sure !
>
>
>
> Even if some tuning is still needed, the plugin seems an improvement to the
> process described in the current documentation[2]. Any objections to me
> switching the build and updating the document?
>
> Robert
> [1]
> http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#notimestamp
> [2] http://creadur.apache.org/rat/site-publish.html



--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy