setupBuild with 1.7 on a maven pom immediately fails


(Carlo Luib-Finetti) #1

I was curious if Gradle 1.7 now can convert a maven multi project to a Gradle build.

running ‘gradle setupBuild’ immediately fails with; see the stacktrace below.

To test if the maven project I’m trying to convert causes this, I tried another very simple maven project. Same result.

But this is strange: when I run the Gradle build on my Gradle multi project, there are no problems creating Java VM occurs - it just runs. Note, this is the same Windows command environment. For both tests I run the same small cmd tool to setup Gradle’s environment.

Q:\sources\mvn_repo-load>gradle --stacktrace setupBuild
  FAILURE: Build failed with an exception.
  * What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at http://gradle.org/docs/1.7/userguide/gradle_daemon.html
Please read below process output to find out more:
-----------------------
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
    * Try:
Run with --info or --debug option to get more log output.
  * Exception is:
org.gradle.api.GradleException: Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at http://gradle.org/docs/1.7/userguide/gradle_daemon.html
Please read below process output to find out more:
-----------------------
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
          at org.gradle.launcher.daemon.bootstrap.DaemonGreeter.parseDaemonOutput(DaemonGreeter.java:37)
        at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(DefaultDaemonStarter.java:109)
        at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(DefaultDaemonStarter.java:90)
        at org.gradle.launcher.daemon.client.DefaultDaemonConnector.createConnection(DefaultDaemonConnector.java:96)
        at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:73)
        at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:147)
        at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:72)
        at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:50)
        at org.gradle.api.internal.Actions$RunnableActionAdapter.execute(Actions.java:171)
        at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:20
1)
        at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:17
4)
        at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:170)
        at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:139)
        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
        at org.gradle.launcher.Main.doAction(Main.java:48)
        at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
        at org.gradle.launcher.Main.main(Main.java:39)
        at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:50)
        at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:32)
        at org.gradle.launcher.GradleMain.main(GradleMain.java:26)

(Carlo Luib-Finetti) #2

Ok, now I found out on my computer at home, that things work well on the maven project I’m interested in to convert to Gradle. Must be something odd on my computer at work.

Any hints what might lead to the problem with initializing a JVM?


(Matt Bellinger) #3

“Could not reserve enough space for object heap”

Not enough memory on the machine, or too many processes running. The daemon could not reserve enough memory to start up.