> When I opened these files with edit ( in command prompt yeahh) I could see a
> 'bad' byte at the beginning.
Those "bad" bytes are the "byte order mark" or BOM for short.
If the file is UTF-8 encoded, those bytes (EF BB BF) are optional and
may be there depending on the editor you use.
It seems
I saw that both pom.xml and settings.xml doesn t like files modified by
ultraedit.
When I opened these files with edit ( in command prompt yeahh) I could see a
'bad' byte at the beginning.
It this one which occurs this error
hope this helps
regards
alexandre
Danilo Tuler-2 wrote:
>
> Hi,
>
> I
I see this sometimes when I have accidentally and unknowingly broken the header
by putting a random character in at the beginning - anything like - or x will
cause that.
Danilo Tuler on 09/05/08 21:20, wrote:
Hi,
your XML does not start with the XML processing instruction or a byte
order mar
Hi,
your XML does not start with the XML processing instruction or a byte
order mark
All my poms start with
I guess a byte order mark is optional for UTF-8.
It's a multi module project, and I don't even know which is the offending
pom.xml among a dozen poms.
My bet is that it's the parent
> your XML does not start with the XML processing instruction or a byte order
> mark
All my poms start with
What do you mean by "byte order mark"?
Danilo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-ma
Danilo Tuler wrote:
Hi,
I'm trying to use the maven release plugin, but when maven is about to
transform my poms, it issues the error:
Error reading POM: Error on line 1: Content is not allowed in prolog.
How can I find what's wrong with my pom?
your XML does not start with the XML processin
Hi,
I'm trying to use the maven release plugin, but when maven is about to
transform my poms, it issues the error:
Error reading POM: Error on line 1: Content is not allowed in prolog.
How can I find what's wrong with my pom?
Thanks,
Danilo
