Ok, I solved this mystery... The reason it wasn't working was because
my reactor artifactId was name differently than the folder the reactor
pom.xml was sitting in. So my reactor's artifactId was dlm-cwa-reactor
and the folder (in svn) which this pom.xml was sitting in was dlm-cwa.
Once I changed
I think I kind of understand what's going on, but not sure how to
solve it. What's going is that maven is treating my reactor/root
pom.xml as a project with the name dlm-cwa-reactor and when it tries
to "copy" that project to a tag, it fails because no such path
actually exists...
This is evident
No, that was just my bad copy/paste.
-Yaakov.
On Wed, May 4, 2011 at 4:30 AM, Marc Rohlfs wrote:
>>
>> scm:svn:https://dev.envieta.com:8443/svn/dlm}
>
> ^
> Could it be this closing curly bracket?
>
> -
svn info shows this:
$ svn info
Path: .
URL: https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa
Repository Root: https://dev.envieta.com:8443/svn/dlm
I tried a few configurations, but they all end up with some variation
of the path .../dlm-cwa-reactor does not exist in revision 730 (or
whatever nu
scm:svn:https://dev.envieta.com:8443/svn/dlm}
^
Could it be this closing curly bracket?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For addition
On Tue, May 3, 2011 at 2:45 PM, Yaakov Chaikin wrote:
> Did I configure scm wrong?
How does that compare to the output of 'svn info' at the top of your
project? Usually a svn url has 'trunk' or 'branches' somewhere in
it...
The scm url should match the location of your pom.xml (minus the filen
Did I configure scm wrong?
scm:svn:https://dev.envieta.com:8443/svn/dlm
scm:svn:https://dev.envieta.com:8443/svn/dlm}
https://dev.envieta.com:8443/svn/dlm
??
-Yaakov.
On Tue, May 3, 2011 at 2:42 PM, Yaakov Chaikin wrote:
> Hmm...
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
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 li
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 pomwith it's appropriate configuration...
Furthermore you sho
Hi all,
I've used the maven release plugin for a long time, but I have always
used it in situations when the room POM was the parent POM at the same
time.
Now, I am a project where that's not an option, but they still want to
use the maven release plugin. Instead, their structure is as follows:
Your should add the goal to the release plugin ,configuration> area like
this:
site,site:deploy,deploy or whateveryourdeploygoal:is
then it gets kicked off when u run release:perform
Cheers
On Thu, 2007-11-15 at 12:17 -0800, Ravi_116 wrote:
> Can the maven release plugin deploy the war file to
e module's
pom.xml.
Ravi
--
View this message in context:
http://www.nabble.com/Maven-Release-Plugin-Question-tf4816868s177.html#a13780801
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe,
-
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/maven-release-plugin-question-tf3903737s177.html#a11068618
Sent from the Maven - Users mailing list arc
dvance.
--
View this message in context:
http://www.nabble.com/maven-release-plugin-question-tf3903737s177.html#a11067768
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTE
On 6/11/07, srinivas ramgopal <[EMAIL PROTECTED]> wrote:
Current latest version of maven release plugin from ibiblio has errors.
It does? Are they in JIRA?
As a workaround, I want to force maven to use the older(the version before
the latest one)version of this plugin.
This plugin related i
.
Given this, how and where do I specify to maven to use a particular version
of this plugin?
Your input is higly appreciated.
Thanks in advance.
--
View this message in context:
http://www.nabble.com/maven-release-plugin-question-tf3903737s177.html#a11067768
Sent from the Maven - Users mailing list
yes, your artifact version must be SNAPSHOT, however your dependencies can
not be SNAPSHOT.
-D
On 11/20/06, Morgovsky, Alexander (US - Glen Mills) <[EMAIL PROTECTED]>
wrote:
Is it required to have "SNAPSHOT" in the version number of the Maven
project in order to use the Maven release plugin w
Is it required to have "SNAPSHOT" in the version number of the Maven
project in order to use the Maven release plugin with it? For example,
if I have a version like 2.0.0 and I would like to create a tag called
2.0.0.0, it looks like I am not able to do this using the plugin. Is
this correct?
19 matches
Mail list logo
