I've seen a similar case at work where Internet access is through a
proxy. Configuring proxy incorrectly lead to "Proxy: not authorized"
messages and corresponding files stored in local repo. Needless to
say, Maven got all confused about it.

Kalle


On Sun, Dec 6, 2009 at 5:31 AM, Wayne Fay <wayne...@gmail.com> wrote:
>> read. but, there is one strange thing I noticed. Along with
>> jaxb-api-2.1.jar, there is a corresponding .pom file and both these files
>> have same size 357. huh?
>
> Next time, cat the files (or edit them, whatever, just open in text
> editor) and see what they look like. The JAR file should be binary
> with a few obvious strings in it, and the pom file should be XML.
>
> I would have been interested to know what was in those 357 bytes on
> your disk -- was the jar a copy of the pom, were both corrupted due to
> being downloaded from a bad repo, or something else altogether...
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to