4a497afe65
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@521198 13f79535-47bb-0310-9956-ffa450edef68
43 lines
1.6 KiB
XML
43 lines
1.6 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!--
|
|
/*
|
|
* 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.
|
|
*/
|
|
-->
|
|
|
|
<faqs title="Frequently Asked Questions">
|
|
|
|
<part id="general">
|
|
<title>General</title>
|
|
|
|
<faq id="licensed-clover">
|
|
<question>
|
|
How do I force a different clover jar to be used?
|
|
</question>
|
|
<answer>
|
|
<p>
|
|
You don't! Clover has now separated the Clover jar from it's license and thus
|
|
there's now no need to provide a custom jar. However you'll still need to provide
|
|
your own license (unless you're using this plugin on an open source project). You
|
|
specify your own license using the <code>maven.clover.license.path</code> property.
|
|
<source>maven.clover.license.path = /some/path/to/my/clover.license</source>
|
|
</p>
|
|
</answer>
|
|
</faq>
|
|
|
|
</part>
|
|
</faqs>
|