[WARNING] The requested profile "nexus" could not be activated because it does not exist.
1 错误警告
[WARNING] The requested profile "nexus" could not be activated because it does not exist.
2 仔细检查Maven的.setting文件,自己嵌套了两层profiles,注释掉多余的就可以了。
<profiles>
<!-- profile | Specifies a set of introductions to the build process, to
be activated using one or more of the | mechanisms described above. For inheritance
purposes, and to activate profiles via <activatedProfiles/> | or the command
line, profiles have to have an ID that is unique. | | An encouraged best
practice for profile identification is to use a consistent naming convention
| for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey',
'user-brett', etc. | This will make it more intuitive to understand what
the set of introduced profiles is attempting | to accomplish, particularly
when you only have a list of profile id's for debug. | | This profile example
uses the JDK version to trigger activation, and provides a JDK-specific repo. -->
<!---->
<!-- <profile> <id>jdk-1.6</id> <activation> <jdk>1.6</jdk> </activation>
<repositories> <repository> <id>sonatype-forge</id> <name>sonatype-forge</name>
<releases> <enabled>false</enabled> <updatePolicy>always</updatePolicy> <checksumPolicy>warn</checksumPolicy>
</releases> <snapshots> <enabled>true</enabled> <updatePolicy>never</updatePolicy>
<checksumPolicy>fail</checksumPolicy> </snapshots> <url>http://mirrors.ibiblio.org/pub/mirrors/maven2</url>
<layout>default</layout> </repository> </repositories> </profile> -->
<!-- | Here is another profile, activated by the system property 'target-env'
with a value of 'dev', | which provides a specific path to the Tomcat instance.
To use this, your plugin configuration | might hypothetically look like:
| | ... | <plugin> | <groupId>org.myco.myplugins</groupId> | <artifactId>myplugin</artifactId>
| | <configuration> | <tomcatLocation>${tomcatPath}</tomcatLocation> | </configuration>
| </plugin> | ... | | NOTE: If you just wanted to inject this configuration
whenever someone set 'target-env' to | anything, you could just leave off
the <value/> inside the activation-property. | <profile> <id>env-dev</id>
<activation> <property> <name>target-env</name> <value>dev</value> </property>
</activation> <properties> <tomcatPath>/path/to/tomcat/instance</tomcatPath>
</properties> </profile> -->
<profile>
<id>jdk-1.8</id>
<activation>
<activeByDefault>true</activeByDefault>
<jdk>1.8</jdk>
</activation>
<properties>
<maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>1.8</maven.compiler.target>
<maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
</properties>
</profile>
<!-- <profiles>
--> <profile>
<id>nexus</id>
<repositories>
<repository>
<id>nexus</id>
<name>Nexus </name>
<url>http://new.nexus.jiushiyaokuaile.cn/nexus/content/groups/public</url>
<releases><enabled>true</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>nexus</id>
<name>Nexus Plugin Repository</name>
<url>http://new.nexus.jiushiyaokuaile.cn/nexus/content/groups/public</url>
<releases><enabled>true</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</pluginRepository>
</pluginRepositories>
</profile>
<!-- </profiles>
-->
<!-- <activeProfiles>
<activeProfile>nexus</activeProfile>
</activeProfiles> -->
</profiles>
<activeProfiles>
<activeProfile>nexus</activeProfile>
</activeProfiles>

浙公网安备 33010602011771号