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_al
Hi,
Yes, I think it's a bug somewhere but I don't use Perforce so I can't help.
Maybe someone will can help you on the Maven users list because I don't think
lot of Perforce users are on this list.
Emmanuel
brewk9 a écrit :
I am using -DgenerateReleasePoms=true. When I run release:prepare, ma
File an issue.
Emmanuel
brewk9 a écrit :
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
-D
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 plug
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
Please, attach your patch to an issue and I'll look at it when I'll found some
time.
Thanks.
Emmanuel
Benoit Decherf a écrit :
Hi,
As I told you in scm-users list (12/07), I need to disable the -F option
in cvs tag.
I make a patch to add the option useForceTag. This works, but in case of
a
I add the issue with the patch: http://jira.codehaus.org/browse/SCM-361
I let the priority to major as we need it and we will have to use the
patched version in my company. If you thinks that this solution is not
good enough, please tell me how this feature has to be implemented.
Thanks.
Beno
You are not giving it a clientspec, you are giving it a name to use. It is
assumed that Maven SCM can do whatever it wants with that clientspec (create
it, modify it, delete it). It was done this way because there are
corporations who have Peforce clientspec naming standards and absolutely
will n
I guess I don't recall what your actual problem is. Can you summarize?
On 12/12/07, brewk9 <[EMAIL PROTECTED]> 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 plugi
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,
The problem is that maven is changing my clientspec which in turn is breaking
other things dependent on that clientspec, including maven-changelog-plugin
reports. IMHO, maven should not be changing my clientspec. I would expect it
to create temporary clientspecs as needed but not change mine.
Yes
I have added the clientspec in the pom as the documentation indicates(like
below) instead of on the command line and now my clientspec is NOT
changed(good). However, the change reports are empty after running
release:prepare and release:perform. The change reports are populated if I
just run the '
12 matches
Mail list logo
