diff --git a/clover/plugin.jelly b/clover/plugin.jelly index d07ab55a..75fb2087 100644 --- a/clover/plugin.jelly +++ b/clover/plugin.jelly @@ -65,10 +65,12 @@ - - - - + + + + + + diff --git a/clover/plugin.properties b/clover/plugin.properties index a1fd022e..9de518c6 100644 --- a/clover/plugin.properties +++ b/clover/plugin.properties @@ -35,9 +35,16 @@ maven.clover.orderBy = PcCoveredAsc maven.clover.instrument.tests = false # Allows the user to override the Clover jar. This is especially useful -# as the Clover jars are license-signed for a specific project so you +# as some Clover jars are license-signed for a specific project so you # might want to use different jars for different projects. -#maven.clover.jar = ${maven.repo.remote}/clover/jars/clover-myproject-1.2.3.jar +#maven.clover.jar = ${maven.repo.local}/clover/jars/clover-myproject-1.2.3.jar + +# Location of the Clover license. Users can override this property to point to +# their own Clover license. By default uses a 30 day eval license valid for +# open source projects. Set it to an empty value if you wish to use Clover's +# other license loading mechanisms (Clover looks next to clover.jar on the +# filesystem and in the classpath). +maven.clover.license.path = ${plugin.getDependencyPath('clover:clover-30day-eval')} # What are the reports that should be generated maven.clover.report.html=true diff --git a/clover/xdocs/changes.xml b/clover/xdocs/changes.xml index 63198636..e5a58dca 100644 --- a/clover/xdocs/changes.xml +++ b/clover/xdocs/changes.xml @@ -26,6 +26,11 @@ + + Added ability for users to specify their own Clover license + file by overriding the new + maven.clover.license.path property. + Made the following goals public by documenting them: clover:report, clover:on, diff --git a/clover/xdocs/properties.xml b/clover/xdocs/properties.xml index 7858aa9e..04bb4cff 100644 --- a/clover/xdocs/properties.xml +++ b/clover/xdocs/properties.xml @@ -96,6 +96,33 @@ ${maven.build.clover}/database + + maven.clover.jar + Yes + + Allows the user to override the Clover jar. This is especially useful + as some Clover jars are license-signed for a specific project so you + might want to use different jars for different projects. + + + If not defined, the plugin uses a 30 day eval Clover jar which is + valid for open source projects. + + + + maven.clover.license.path + Yes + + Location of the Clover license. Users can override this property to + point to their own Clover license. By default uses a 30 day eval + license valid for open source projects. Set it to an empty value if + you wish to use Clover's other license loading mechanisms (Clover + looks next to clover.jar on the filesystem and in the classpath). + + + ${plugin.getDependencyPath('clover:clover-30day-eval')} + +