From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: Nigel Magnay <nigel.magnay@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, Git ML <git@vger.kernel.org>
Subject: Re: [JGIT] maven build fails on OS X
Date: Fri, 6 Feb 2009 22:07:00 +0100 [thread overview]
Message-ID: <200902062207.00941.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <320075ff0902061208l6671c2a0m3d4b07b97025b53a@mail.gmail.com>
fredag 06 februari 2009 21:08:18 skrev Nigel Magnay:
> > I've looked at it and gave up. I don't know what Maven is doing here
> > on the Mac. Maybe fresh eyes will have a better chance at fixing it.
> >
> > My experience with Maven is it works about 5% of the time, and the
> > other 95% of the time you have to work around it by skipping tests,
> > or by writing massive blocks of XML in your pom.xml file, or by
> > redesigning your entire project directory structure and revision
> > control system to use SVN instead of Git.
>
> Ok. It's not (just) a Maven problem as I can get the same tests to
> fail in Eclipse by setting the Console Encoding to MacRoman (which is
> the default Charset.defaultCharset() when running a java app on OS X).
Ok you found it. I just sent a reply...
> However, I'm slightly confused - possibly because I don't know what
> /should/ be the case. In
>
> exp.replace("\303\205ngstr\303\266m", "\u00c5ngstr\u00f6m")
The text is "Ångström".
> is \303\205 really meant to represent U+00C3 and U+0085 ? Shouldn't
> the replace be being done on bytes rather than strings?
Yes, but we fake the RAW strings by only really using the lower byte of
each code point. arrays of bytes are really hard to read in source code.
The MacRoman is the problem. What encoding does C Git on Mac use?
Isn't that UTF-8, in which case our use of platform default as fallback is
wrong. Gah...
-- robin
next prev parent reply other threads:[~2009-02-06 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 15:08 [JGIT] maven build fails on OS X Nigel Magnay
2009-02-06 15:31 ` Shawn O. Pearce
2009-02-06 20:08 ` Nigel Magnay
2009-02-06 21:07 ` Robin Rosenberg [this message]
2009-02-06 20:54 ` Robin Rosenberg
2009-02-06 21:12 ` Nigel Magnay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200902062207.00941.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=git@vger.kernel.org \
--cc=nigel.magnay@gmail.com \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).