Did I configure scm wrong?
<scm>
<connection>scm:svn:https://dev.envieta.com:8443/svn/dlm</connection>
<developerConnection>scm:svn:https://dev.envieta.com:8443/svn/dlm}</developerConnection>
<url>https://dev.envieta.com:8443/svn/dlm</url>
</scm>
??
-Yaakov.
On Tue, May 3, 2011 at 2:42 PM, Yaakov Chaikin <yaakov.chai...@gmail.com> wrote:
> Hmm... Perhaps, I spoke too soon.
>
> Everything goes well during dry run, but committing doesn't work. Any ideas?
>
> *************************
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
> C:\Users\yaakov\AppData\Local\Temp\maven-scm-778463861.commit
> --targets C:\Users\yaakov\App
> Data\Local\Temp\maven-scm-7812943996577343934-targets"
> [INFO] Working directory: C:\Users\yaakov\workspaces\dlm-main\trunk\dlm-cwa
> [INFO] Tagging release with the label dlm-cwa-reactor-1.0...
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
> C:\Users\yaakov\AppData\Local\Temp\maven-scm-1423212193.commit
> --revision 722 https://dev.env
> ieta.com:8443/svn/dlm/dlm-cwa-reactor
> https://dev.envieta.com:8443/svn/dlm/dlm-cwa-reactor/tags/dlm-cwa-reactor-1.0";
> [INFO] Working directory: c:\users\yaakov\workspaces\dlm-main\trunk\dlm-cwa
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to tag SCM
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Path 'https://dev.envieta.com:8443/svn/dlm/dlm-cwa-reactor' does
> not exist in revision 722
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 4 minutes 21 seconds
> [INFO] Finished at: Tue May 03 14:42:06 EDT 2011
> [INFO] Final Memory: 15M/36M
> [INFO]
> ------------------------------------------------------------------------
> *************************
>
> On Tue, May 3, 2011 at 12:23 PM, Yaakov Chaikin
> <yaakov.chai...@gmail.com> wrote:
>> Thanks! That put me on the right path and I think it's working now.
>>
>> Just for the sake of others reading this later... If you have
>> dependencies that have to specify a version in the reactor or child
>> modules, just use ${project.version} instead of ${parent.version}.
>> Also, you have to make sure to list your parent module in the list of
>> <modules> or the autoVersionSubmodules property won't work and it will
>> still ask you resolve dependencies which have -SNAPSHOT version in
>> them and it will start with the parent module's pom. To avoid all
>> this, just list your parent module in the list <modules> in your
>> reactor pom.
>>
>> For a followup question, is there a way to force the release plugin
>> NOT to run the unit tests. I did -DskipTests=true, but it ignores it
>> and runs them anyway. In the past, I've tricked the plugin by
>> specifying a special profile for tests which looked for specially
>> named classes, rendering the "test" phase kind of useless. It's a
>> hack, but I had to do it. For those wondering why I would want to run
>> this withOUT running the tests? It's because some of the tests are DB
>> unit tests and require a DB to be present, etc. and all I want to do
>> is release a previously tested codebase and avoid having to set up
>> environments just so I can do a release.
>>
>> Thanks again,
>> -Yaakov.
>>
>> On Mon, May 2, 2011 at 3:03 PM, Karl Heinz Marbaise <khmarba...@gmx.de>
>> wrote:
>>> Hi, you should the configuration for the maven-release-plugin
>>>
>>> autoversionsubmodules which can be done either on command as well in the
>>> pom.
>>>
>>> In this situation i would suggest to configure the maven-release-plugin in
>>> the parent pom....with it's appropriate configuration...
>>>
>>> Furthermore you should prevent using of ${parent.version} in your reactor
>>> pom neither in you modules pom's...you should define the version only via at
>>> the parent pom..
>>> I would suggest also to define the groupId of the project only once in the
>>> parent pom ...
>>>
>>> Kind regards
>>> Karl Heinz Marbaise
>>> --
>>> SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
>>> Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
>>> Hauptstrasse 177 USt.IdNr: DE191347579
>>> 52146 Würselen http://www.soebes.de
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
