yeah, i tried using the maven one and maven two repos (including marking
maven one as legacy) but both ended up blacklisted. i keep thinking it must
be something on my end, but after following all the steps and reading all
the relevant posts i could find, it's still not happening for me...
i *just* wiped my .m2/repo, cos i'm trying to get my company's code all
mvn'ized and i needed to make sure i didn't have jars installed that weren't
readily available to other developers. so depending on what target i ran,
mvn would ask for different maven-* jars (so i think i got the error on
maven-site cos i was trying a mvn install).
i'll keep experimenting. thanks for your time and insight.
jdc
Aleksei Valikov wrote:
>
> 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).
>
> 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.
>
--
View this message in context: http://www.nabble.com/issues-using-maven-jaxb1-plugin-1.0-rc7-tf2682155.html#a7500793
Sent from the java.net - jaxb users mailing list archive at Nabble.com.