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 build and had not been installed, which was failing because Kodak-Intersystem had not been installed - so I had a cycle of dependencies
Changing Kodak-Intersystem to generate javadoc in the deploy phase broke the cycle by allowing Kodak-Intersystem to be installed, and all the other dependencies to be resolved. For the most part the diagnostics were not at all useful in helping, I had to reason through all the mechanics of what was going on. The behavior of Nexus and m2e, while annoying and distracting, were not the direct cause. Nexus was an indirect cause because I was reorganizing things, which finally caused the dependency/life-cycle circle to manifest. Cheers, Eric On Thu, Aug 4, 2011 at 10:31 AM, Brian Fox <[email protected]> wrote: > 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 example > > On Thu, Aug 4, 2011 at 11:32 AM, Eric Kolotyluk > <[email protected]> wrote: > > 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 at 11:07 PM, [email protected] < > > [email protected]> wrote: > > > >> 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: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > >
