
META-INF.maven.lifecycle.xml Maven / Gradle / Ivy
<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <lifecycles> <lifecycle> <id>clover</id> <phases> <phase> <id>validate</id> <executions> <execution> <!--configuration> <cloverOutputDirectory>${project.build.directory}/clover</cloverOutputDirectory> <cloverDatabase>${project.build.directory}/clover/clover.db</cloverDatabase> </configuration--> <goals> <goal>instrumentInternal</goal> </goals> </execution> </executions> </phase> <!-- This below is a HACK. It tries to prevent the build from stopping in case of build failures as we could still like to generate Clover reports even if it happens. The Clover plugin cannot know about all plugins that can execute and fail the build and moreover which can be bound to any phase by the user. A better solution would be for Maven to have a flag that says "continue the build even in case of failures". --> <phase> <id>test</id> <configuration> <testFailureIgnore>true</testFailureIgnore> </configuration> </phase> <phase> <id>integration-test</id> <configuration> <testFailureIgnore>true</testFailureIgnore> </configuration> </phase> </phases> </lifecycle> </lifecycles>
© 2015 - 2025 Weber Informatics LLC | Privacy Policy