Hi On 13 December 2015 at 23:11, Karl Heinz Marbaise <[email protected]> wrote:
> Hi Olivier, > > have you started the build from maven root folder (cause the gist looks > different (Or i'm mistaken something): > With "maven root folder" do you mean maven core sources? Yes definitely because this is what I want to build.... > > maven-core olamy$ mvn -DdistributionTargetFolder="$M2_HOME" clean package > -DskipTests.. > > ? > > Which Maven version do you use? mvn -v Apache Maven 3.3.2-SNAPSHOT (c88ac1bad586f8d9f6ab8892a4590847f3759308; 2015-09-24T09:52:20+10:00) Maven home: /Users/olamy/softs/maven/trunk Java version: 1.8.0_51, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.11.2", arch: "x86_64", family: "mac" > > > Kind regards > Karl Heinz Marbaise > > On 12/13/15 12:15 PM, Olivier Lamy wrote: > >> I read the FM :-) and I found something similar mvn >> -DdistributionTargetFolder="$M2_HOME" clean package -DskipTests >> >> I run it once without failure then I got a long exception stack : >> >> maven-core olamy$ mvn -DdistributionTargetFolder="$M2_HOME" clean package >> -DskipTests >> >> [WARNING] Error injecting: >> org.apache.maven.project.DefaultProjectBuildingHelper >> >> com.google.inject.ProvisionException: Unable to provision, see the >> following errors: >> >> >> 1) No implementation for org.apache.maven.classrealm.ClassRealmManager was >> bound. >> >> while locating org.apache.maven.project.DefaultProjectBuildingHelper >> >> >> 1 error >> >> at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1025) >> >> at >> >> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051) >> >> at >> >> org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48) >> >> at >> >> com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81) >> >> >> Full stack here: https://gist.github.com/olamy/f107be85c2409fa61de7 >> >> >> Any idea? >> >> Thanks >> >> Olivier >> >> >> >> On 13 December 2015 at 21:56, Olivier Lamy <[email protected]> wrote: >> >> Hi >>> I used to simply do a one line cli to simply replace a current local >>> maven >>> with a fresh build from the trunk. >>> Just using "ant -DskipTests=true -Dmaven.home.exists.continue=true" and >>> voila a new maven version was installed locally from last sources. >>> >>> What is the new simple one line option now? >>> >>> Thanks >>> Olivier >>> >>> On 12 December 2015 at 22:47, Karl Heinz Marbaise <[email protected]> >>> wrote: >>> >>> Hi, >>>> >>>> based on the change [MNG-5904] which removes the whole Ant build the >>>> integration tests have failed... >>>> >>>> The first one: >>>> >>>> >>>> >>>> https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3-jdk-1.7/ >>>> >>>> is now back to successful. I have changed the configuration to use Maven >>>> (3.3.1) itself to bootstrap it for running the integration tests.. >>>> >>>> So i will change the others as well.... >>>> >>>> [MNG-5904]: https://issues.apache.org/jira/browse/MNG-5904 >>>> >>>> Kind regards >>>> Karl Heinz Marbaise >>>> >>>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
