Further down the message, this boils down to a failure to find an ArtifactResolver.
On Sat, Feb 22, 2014 at 12:04 PM, Benson Margulies <bimargul...@gmail.com> wrote: > Plexus-container-default 1.5.5 changes some issues. > > This seems to make some things better. > > The first failure is: > > testNoSnapshotDependencies(org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhaseTest) > Time elapsed: 0.07 sec <<< ERROR! > org.codehaus.plexus.component.repository.exception.ComponentLookupException: > Unable to lookup component > 'org.apache.maven.project.MavenProjectBuilder', it could not be > started. > role: org.apache.maven.project.MavenProjectBuilder > roleHint: default > classRealm: plexus.core > ----------------------------------------------------- > realm = plexus.core > strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > Number of foreign imports: 0 > > ----------------------------------------------------- > > at > org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) > > And this happens over and over. I am checking if I can make it go > away. the scm component error is gone, or at least hiding. > > > > > On Sat, Feb 22, 2014 at 11:44 AM, Benson Margulies > <bimargul...@gmail.com> wrote: >> On Sat, Feb 22, 2014 at 7:38 AM, Robert Scholte <rfscho...@apache.org> wrote: >>> src/test/resources/org/apache/maven/shared/release/phase >> >> I'm trying to use a less ancient version of plexus-container-default, >> it requires some test changes, I'll let you know what happens. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
