blob: c72b3dd9c4a616e87ea85996b083e7c4a830398f [file] [log] [blame]
Using Perforce
Dennis Lundberg
~~ 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
~~ Unless required by applicable law or agreed to in writing,
~~ software distributed under the License is distributed on an
~~ KIND, either express or implied. See the License for the
~~ specific language governing permissions and limitations
~~ under the License.
Using Perforce
The maven-changelog-plugin uses {{{}Maven SCM}}
as an underlying layer, when accessing your SCM system. When Maven SCM is
working with Perforce it needs a clientspec. This is provided by setting
system properties that are then read by Maven SCM.
Configuring this is done in the same way as for the maven-scm-plugin. So if
you have a working configuration for maven-scm-plugin, you can just copy
those lines over to your maven-changelog-plugin configuration. The following
configuration shows an example of what this can look like.