On 16 November 2013 21:02, Hervé BOUTEMY herve.bout...@free.fr wrote:
ouch, strange: 'r' were replaced by 'n'
Perhaps a botched attempt at changing line endings from (CR) to (LF) ?
I just had a look at archive content, and it does not have the problem
so I just copied archive content into
Oh! That's really clever. I wonder, though, who, when, why?
On Sun, Nov 17, 2013 at 5:50 AM, sebb seb...@gmail.com wrote:
On 16 November 2013 21:02, Hervé BOUTEMY herve.bout...@free.fr wrote:
ouch, strange: 'r' were replaced by 'n'
Perhaps a botched attempt at changing line endings from (CR)
who: I did svn blame and I know but won't tell :p (unless you're really
interested)
when: during the site publication
why: I don't really know
but what I know is that the /plugins/maven-scm-publish-plugin content was
recreated independently from /plugins-archives/maven-scm-publish-plugin-1.0-
LF Standard Nix line-ending
LFCR windows line-end
unix2dos usually cures
are you're thinking of a filter to catch \n Line-endings by maven-site
?
MG
Date: Sun, 17 Nov 2013 08:20:15 -0500
Subject: Re: Boy have we got a broken webpage
From: bimargul...@gmail.com
To: dev
http://maven.apache.org/plugins/maven-scm-publish-plugin/examples/one-module-configuration.html
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
ouch, strange: 'r' were replaced by 'n'
I just had a look at archive content, and it does not have the problem
so I just copied archive content into actual plugin documentation location:
another reason why a svn copy on staged documentation (which was voted on) is
better than regenerating a
