Am 04.08.2011 06:53 schrieb Eric Kolotyluk eric.koloty...@gmail.com:
OK, I almost had everything working with maven and m2e and nexus, and now
it's all broken again. It seems every time I change anything to do with
maven configuration, it all falls apart again. It is all unbelievably
fragile.
This is the JBoss repository, it is very unreliable. If you don't need to
resolve dependencies, try building offline.
-dirk
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
The intersystem pom is not supposed to be in org.jboss.repository. I do not
know why it expects to find it there.
Cheers, Eric
On Wed, Aug 3, 2011 at 11:03 PM, Ansgar Konermann
ansgar.konerm...@googlemail.com wrote:
Am 04.08.2011 06:53 schrieb Eric Kolotyluk eric.koloty...@gmail.com:
OK,
When I set up Nexus I set it up to mirror the JBoss repository. It synced up
with JBoss last week and everything was working fine.
Isn't the idea of having a central repository manager like Nexus that you
are isolated against problems with the real repositories?
Cheers, Eric
On Wed, Aug 3, 2011
It appears like you aren't using groups in Nexus. Your maven shouldn't
be telling you it's looking in the jboss repo, it should be looking in
your nexus group and nexus deals with the other repos. You would
normally do this in your settings with a mirrorOf * -
nexus/content/groups/public for
OK, things seem to have been sorted out now.
It seems the underlying problem was my parent pom Kodak-Intersystem was
failing to to generate javadoc in the package phase, this was failing
because intersystem-service was failing in build, which was failing because
color-repository was failing in
OK, I almost had everything working with maven and m2e and nexus, and
now it's all broken again. It seems every time I change anything to do
with maven configuration, it all falls apart again. It is all
unbelievably fragile.
I keep trying to do a mvn install on my color-repository module,
