Spring Maven clean error - The requested profile “pom.xml” could not be activated because it does not exist

问题:

I'm trying to build a Spring-Boot *.war with maven, but I keep getting:

[INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.600 s [INFO] Finished at: 2015-01-28T10:46:11-03:00 [INFO] Final Memory: 6M/123M [INFO] ------------------------------------------------------------------------ [WARNING] The requested profile "pom.xml" could not be activated because it does not exist. 

After running the mvn: clean.

I have no idea why, I'm following this guide.

My pom.xml

After the success, maven generates a target folder in the project, it's containing only the Manifest.mf, pom.properties and pom.xml.

I'm a beginner using maven/spring and I haven't find any clues about what it might be. Any help would be appreciated.

The complete log:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project webconsultas: Fatal error compiling: invalid target release: 1.8 -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project webconsultas: Fatal error compiling     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)     at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)     at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)     at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)     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:601)     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) Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal error compiling     at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:796)     at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)     ... 19 more Caused by: org.codehaus.plexus.compiler.CompilerException: invalid target release: 1.8     at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:191)     at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)     at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785)     ... 22 more Caused by: java.lang.IllegalArgumentException: invalid target release: 1.8     at com.sun.tools.javac.main.RecognizedOptions$GrumpyHelper.error(RecognizedOptions.java:88)     at com.sun.tools.javac.main.RecognizedOptions$10.process(RecognizedOptions.java:359)     at com.sun.tools.javac.api.JavacTool.processOptions(JavacTool.java:242)     at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:199)     at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:68)     at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:115)     ... 24 more [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/MojoExecutionException 

回答1:

The warning message

[WARNING] The requested profile "pom.xml" could not be activated because it does not exist. 

means that you somehow passed -P pom.xml to Maven which means "there is a profile called pom.xml; find it and activate it". Check your environment and your settings.xml for this flag and also look at all <profile> elements inside the various XML files.

Usually, mvn help:effective-pom is also useful to see what the real POM would look like.

Now the error means that you tried to configure Maven to build Java 8 code but you're not using a Java 8 runtime. Solutions:

1. Install Java 8
2. Make sure Maven uses Java 8 if you have it installed. JAVA_HOME is your friend
3. Configure the Java compiler in your pom.xml to a Java version which you actually have.

Related:

• Introduction to Build Profiles

回答2:

I was getting this same warning everytime I was doing 'maven clean'. I found the solution :

Step - 1 Right click on your project in Eclipse

Step - 2 Click Properties

Step - 3 Select Maven in the left hand side list.

Step - 4 You will notice "pom.xml" in the Active Maven Profiles text box on the right hand side. Clear it and click Apply.

Below is the screen shot :

Hope this helps. :)

回答3:

This link has solution of how to get it working. Removing "pom.xml" from the "Profiles:" line and then click "Run".

回答4:

Yes even I got the same error. So I did the following changes

-> Check the error in the Problems tab located near the Console tab

-> See where the error persists, Its possible that some jar file may be corrupted or is outdated so, pom isn't activated in the Project.

-> I found one of my jar was outdated version so I updated it by getting the dependencies from maven repository from this link https://mvnrepository.com

So to conclude, do check where the error persist and which jar file is outdated and make changes accordingly

文章来源: Spring Maven clean error - The requested profile “pom.xml” could not be activated because it does not exist