Hi.
> i did that, actually. i used maven2.repository.dev.java.net as both repo and
> pluginRepo, but no luck...
Did you also include maven-repository.dev.java.net? JAXB jars are in the Maven
One repo of dev.java.net, not in the maven2 (due to some historical reasons).
> i always get warnings about not being able to contact
> https://maven2-repository.dev.java.net/nonav/repository at all:
> [WARNING] repository metadata for: 'artifact
> org.apache.maven.plugins:maven-site-plugin' could not be retrieved from
> repository: maven2-repository.dev.java.net due to an error: Error
> transferring file
>
> [INFO] Repository 'maven2-repository.dev.java.net' will be blacklisted
>
> like i said, a proxy shouldn't be the issue (i'm now at home on a different
> unproxied network). it would really seem to be a login issue, since i get
> the PKIX cert stack traces when running with debug stack traces turned on:
>
> [WARNING] repository metadata for: 'artifact
> org.apache.maven.plugins:maven-site-plugin' could not be retrieved from
> repository: maven2-repository.dev.java.net due to an error: Error
> transferring file
> [INFO] Repository 'maven2-repository.dev.java.net' will be blacklisted
> [DEBUG] Exception
[skip]
> so it's all the PKIX stuff that has me worried. did i miss some
> configuration step with the java-net repo?
Ehm... I guess not...
Sorry, I really don't know. This is known to work, I have several projects that
use maven-jaxb1-plugin, so this might still be a proxy problem.
I'd also try deleting the local repo. What I've experienced a coupe of times was
some bad jars getting in there and breaking my builds. Maybe you have some bad
version of site plugin (what has site plugin to do with maven-jaxb1-plugin
anyway?) or wagon or anything...
Sorry that I can't help, wish you good luck.
Bye.
/lexi