[Deploying Sakai] Sakai build fails. (versions: sakai-2.9.3 and trunk, maven 3.1.1)
Gesh hseG
gesh at gesh.uni.cx
Sat Dec 28 15:10:52 PST 2013
Problem fixed. It was caused due to my mistaken assumption that maven
collapses flags. Thus, I assumed that mvn -Xe was equivalent to mvn -X -e.
Thanks everyone.
On Fri, Dec 27, 2013 at 4:27 PM, Anthony Whyte <arwhyte at umich.edu> wrote:
> What mvn tasks are you attempting to invoke? From the debug output "e" (. .
> . [e, clean, install] . . .) is being interpreted as a task which leaves
> Maven befuddled. "e" is a switch for displaying execution errors and should
> be rendered "-e". I can reproduce your error by neglecting to include the
> dash.
>
> mvn e clean install [NAUGHTY]
>
> mvn -e clean install [NICE]
>
> See if you can build just the master pom. From the your Sakai checkout
> directory:
>
> cd master
> mvn clean install
>
> If successful
> cd ../
> mvn clean install sakai:deploy
>
> in order to install the rest of Sakai in your local Maven .m2 repo and
> deploy it to your target Tomcat servlet container.
>
> anthony whyte | its and mlibrary | university of michigan |
> arwhyte at umich.edu | 517-980-0228
>
>
> On Dec 27, 2013, at 6:43 AM, Gesh hseG wrote:
>
> Hi. For the past week, I've been trying to get sakai to build.
> However, each time the build fails with the following error:
> [DEBUG] === REACTOR BUILD PLAN
> ================================================
> [DEBUG] Project: org.sakaiproject:master:pom:2.9.3
> [DEBUG] Tasks: [e, clean, install]
> [DEBUG] Style: Regular
> [DEBUG]
> =======================================================================
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building Sakai Master 2.9.3
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Lifecycle default -> [validate, initialize, generate-sources,
> process-sources, generate-resources, process-resources, compile,
> process-classes, generate-test-sources, process-test-sources,
> generate-test-resources, process-test-resources, test-compile,
> process-test-classes, test, prepare-package, package,
> pre-integration-test, integration-test, post-integration-test, verify,
> install, deploy]
> [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
> [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2.267s
> [INFO] Finished at: Fri Dec 27 13:25:59 IST 2013
> [INFO] Final Memory: 4M/10M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Unknown lifecycle phase "e". You must specify a valid
> lifecycle phase or a goal in the format <plugin-prefix>:<goal> or
> <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>.
> Available lifecycle phases are: validate, initialize,
> generate-sources, process-sources, generate-resources,
> process-resources, compile, process-classes, generate-test-sources,
> process-test-sources, generate-test-resources, process-test-resources,
> test-compile, process-test-classes, test, prepare-package, package,
> pre-integration-test, integration-test, post-integration-test, verify,
> install, deploy, pre-clean, clean, post-clean, pre-site, site,
> post-site, site-deploy. -> [Help 1]
> org.apache.maven.lifecycle.LifecyclePhaseNotFoundException: Unknown
> lifecycle phase "e". You must specify a valid lifecycle phase or a
> goal in the format <plugin-prefix>:<goal> or
> <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>.
> Available lifecycle phases are: validate, initialize,
> generate-sources, process-sources, generate-resources,
> process-resources, compile, process-classes, generate-test-sources,
> process-test-sources, generate-test-resources, process-test-resources,
> test-compile, process-test-classes, test, prepare-package, package,
> pre-integration-test, integration-test, post-integration-test, verify,
> install, deploy, pre-clean, clean, post-clean, pre-site, site,
> post-site, site-deploy.
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings(DefaultLifecycleExecutionPlanCalculator.java:227)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateMojoExecutions(DefaultLifecycleExecutionPlanCalculator.java:198)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:117)
> at
> org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:134)
> at
> org.apache.maven.lifecycle.internal.BuilderCommon.resolveBuildPlan(BuilderCommon.java:92)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [ERROR]
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException
>
> The computer is an Arch Linux machine. Build logs, as well as the
> PKGBUILD, are attached (for the non-Arch people, a PKGBUILD is a bash
> build script that is used to package
> programs on Arch Linux. It should be pretty self-explanatory)
> I've already changed the sakai version I'm using to 2.9.3 instead of
> trunk, and removed the patches I made to the pom.xml to inject the JRE
> flags that sakai needs (specifically, the memory flags).
> Nothing helps. In addition, the following lines in the logs makes me
> think that this is a syntax error in the pom.xml or a case of a
> malformed file being misread:
> [WARNING]
> [WARNING] Some problems were encountered while building the effective
> model for org.sakaiproject:master:pom:2.9.3
> [WARNING] 'parent.relativePath' points at org.sakaiproject:base
> instead of org.sonatype.oss:oss-parent, please verify your project
> structure @ line 3, column 13
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer
> support building such malformed projects.
> [WARNING]
>
> Please, can anyone help me? I've attempted searching this problem and
> have tried asking on IRC, but no one seems to have had this problem,
> and no one is on the ostensibly official support channel.
>
> Thank you very much in advance,
> Gesh
> <sakai-svn-132925-1-i686-build.log>_______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
>
> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"
>
>
More information about the production
mailing list