On 9 May 2016 at 11:55, Benson Margulies wrote:
> You need to checkout the tag, run a build, and then try to run the
> site build. Be careful that you don't overwrite the live site.
>
> The pattern at the Maven PMC is to set the distro management URL to
> some location safely NOT the live site, an
You need to checkout the tag, run a build, and then try to run the
site build. Be careful that you don't overwrite the live site.
The pattern at the Maven PMC is to set the distro management URL to
some location safely NOT the live site, and then use svn cp as part of
the release process to put th
On 9 May 2016 at 10:56, sebb wrote:
> On 9 May 2016 at 08:15, Benedikt Ritter wrote:
>> Hi,
>>
>> Benson Margulies schrieb am So., 8. Mai 2016 um
>> 15:11 Uhr:
>>
>>> As far as I could see, mvn site-deploy is running the
>>> maven-scm-publish-plugin, that is using that URL from
>>> distribution-
On 9 May 2016 at 08:15, Benedikt Ritter wrote:
> Hi,
>
> Benson Margulies schrieb am So., 8. Mai 2016 um
> 15:11 Uhr:
>
>> As far as I could see, mvn site-deploy is running the
>> maven-scm-publish-plugin, that is using that URL from
>> distribution-management. maybe someone configured it wrong.
Hi,
Benson Margulies schrieb am So., 8. Mai 2016 um
15:11 Uhr:
> As far as I could see, mvn site-deploy is running the
> maven-scm-publish-plugin, that is using that URL from
> distribution-management. maybe someone configured it wrong. I'm happy
> to pass the whole issue off to you.
>
I've tri
As far as I could see, mvn site-deploy is running the
maven-scm-publish-plugin, that is using that URL from
distribution-management. maybe someone configured it wrong. I'm happy
to pass the whole issue off to you.
On Sun, May 8, 2016 at 8:13 AM, Benedikt Ritter wrote:
> Hi Benson,
>
> Benson Mar
Hi Benson,
Benson Margulies schrieb am So., 8. Mai 2016 um
14:05 Uhr:
> When I arrived as the RM, I found a URL in there that ended with
> 'commons-i'.
>
> So, when I did the release, I patched it to end with 'commons-io'
> before running the site-deploy that runs the maven-scm-publish-plugin.
>
When I arrived as the RM, I found a URL in there that ended with 'commons-i'.
So, when I did the release, I patched it to end with 'commons-io'
before running the site-deploy that runs the maven-scm-publish-plugin.
The result was javadoc at the root of the site, instead of down where
it belongs.
sebb schrieb am So., 8. Mai 2016 um 13:17 Uhr:
> On 6 May 2016 at 13:31, wrote:
> > Author: bimargulies
> > Date: Fri May 6 12:31:46 2016
> > New Revision: 1742539
> >
> > URL: http://svn.apache.org/viewvc?rev=1742539&view=rev
> > Log:
> > Fix the javadoc publication URL.
>
> -1
>
> That is no
On 6 May 2016 at 13:31, wrote:
> Author: bimargulies
> Date: Fri May 6 12:31:46 2016
> New Revision: 1742539
>
> URL: http://svn.apache.org/viewvc?rev=1742539&view=rev
> Log:
> Fix the javadoc publication URL.
-1
That is not only used for Javadoc.
It is used for the entire site.
> Modified:
>
10 matches
Mail list logo
