That does not help very much if you are using Continuum since you don't know your client's name! The only solution is writing a .p4config.
SCM-281, MCHANGELOG-66, SCM-227 and release from Continuum would be working a probably even more issues would be fixed. Regards, Sebastian > -----Original Message----- > From: Dennis Lundberg [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 12, 2007 10:03 PM > To: scm-dev@maven.apache.org > Subject: Re: release:perform changes perforce clientspec > > To get the changelog-plugin working with perforce, follow these > instructions: > > > http://maven.apache.org/plugins/maven-changelog-plugin/examples/using- > perforce.html > > brewk9 wrote: > > Thanks for your reply. Well, I'm supplying the clientspec to enable the > > maven-changelog-plugin to work. Without that, that plugin doesn't work. > > Should the perforce plugin be changed to always create a temporary > > clientspec? Any other suggestions? > > > > > > mperham wrote: > >> Ken, I wrote the Perforce plugin for Maven but I don't use either > >> technology > >> at my current job (I'm now a Ruby guy) so I'm limited in how I can help > >> you. > >> I'm happy to answer what questions I can. > >> To perform the release, Maven needs to build the canonical source as > >> checked > >> into Perforce. The only way it can check out that code to a particular > >> location on your local disk is by using a clientspec. If you don't give > >> Maven a name, it will create a temporary clientspec and use that for the > >> release. But either way, it's going to change the target directory to be > >> target/checkout so that the source will be checked out to the proper > >> directory for building. > >> > >> mike > >> > >> On 12/12/07, brewk9 <[EMAIL PROTECTED]> wrote: > >>> > >>> Maven is changing my perforce client spec! It's changing the root to the > >>> target\checkout directory of the project I'm building. This directory > >>> doesn't even exist in perforce! > >>> > >>> This is happening when I call the release:perform goal with system > >>> property > >>> -Dmaven.scm.perforce.clientspec.name=brewke_all. > >>> -- > >>> View this message in context: > >>> http://www.nabble.com/release%3Aperform-changes-perforce-clientspec- > tp14302166s177p14302166.html > >>> Sent from the Maven - SCM mailing list archive at Nabble.com. > >>> > >>> > >> > > > > > -- > Dennis Lundberg
smime.p7s
Description: S/MIME cryptographic signature
