element of either the release
>> or the scm plugin?
>> >
>> > Thanks,
>> > Jim
>> >
>> > -Original Message-
>> > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
>> > Sent: Monday, May 07, 2007 4:55 PM
>&
>> >
>> >
>> >
>>
cvs_native
>>
>> >
>> >
>> > Or do I need it in a element of either the release
>> or the scm plugin?
>> >
>> > Thanks,
>> > Jim
>> >
>> > -Original Message-
ative
>
>
> Or do I need it in a element of either the release
or the scm plugin?
>
> Thanks,
> Jim
>
> -Original Message-
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 07, 2007 4:55 PM
> To: Maven Users List
> Subject:
riginal Message-
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 07, 2007 4:55 PM
> To: Maven Users List
> Subject: Re: [ANN] Maven Release Plugin 2.0-beta-5 Released
>
> I don't think, but you can use your cvs executable by adding a system
p
anuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 4:55 PM
To: Maven Users List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-5 Released
I don't think, but you can use your cvs executable by adding a system property
on the command line:
mvn -Dmaven.scm.provider.cvs.impl
07, 2007 4:55 PM
To: Maven Users List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-5 Released
I don't think, but you can use your cvs executable by adding a system property
on the command line:
mvn -Dmaven.scm.provider.cvs.implementation=cvs_native release:prepar
ubject: Re: [ANN] Maven Release Plugin 2.0-beta-5 Released
Jim,
the new version use a pure java cvs client by default, instead of the system
cvs executable.
Emmanuel
Crossley, Jim a écrit :
Thanks for the release, Stephane. After I upgraded, however, I
noticed the release:perform task no lon
So is there no way to make the Java client honor exec permissions? Any
recommended best practice for a workaround?
Jim
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 4:45 PM
To: Maven Users List
Subject: Re: [ANN] Maven Release Plugin
Obviously, this problem only applies on *nix systems.
Jim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Stephane Nicoll
Sent: Friday, May 04, 2007 2:09 PM
To: Maven Users List
Subject: [ANN] Maven Release Plugin 2.0-beta-5 Released
The Maven team is
Behalf Of Stephane Nicoll
Sent: Friday, May 04, 2007 2:09 PM
To: Maven Users List
Subject: [ANN] Maven Release Plugin 2.0-beta-5 Released
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0-beta-5
http://maven.apache.org/plugins/maven-release-plugin/
Rel
The Maven team is pleased to announce the release of the Maven Release Plugin,
version 2.0-beta-5
http://maven.apache.org/plugins/maven-release-plugin/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
** Bug
* [MRELEASE-3] - release:prepare should not require multimodule
I don't think the release plugin is bound to a lifecycle phase. I think you
need to call it directly.
regards,
Wim
2007/4/18, Pankaj Tandon <[EMAIL PROTECTED]>:
Hi,
I was looking at the pom.xml of the maven-release-plugin hoping to find a
binding to one of the phases in there.
Hi,
I was looking at the pom.xml of the maven-release-plugin hoping to find a
binding to one of the phases in there.
For example...
...
sample.plugin
maven-hello-plugin
compile
sayhi
t the revision) in some files in the release'd branch.
That way, the application could access this file/files (like a about.jsp
perhaps) to tell me what release is deployed.
I realize that subversion does not support 'tags' and so this becomes a
little more difficult. However, the maven-rel
in the
release plugin:
mvn release:prepare -Dusername=USERNAME -Dpassword=PASSWORD
Emmanuel
William Ferguson a écrit :
Sorry Emmanuel,
My post *should* have read :
1) If the SCM user/password has NOT been been explicitly configured in
your POM or Settings, how does the maven-release-plugin discove
Sorry Emmanuel,
My post *should* have read :
1) If the SCM user/password has NOT been been explicitly configured in
your POM or Settings, how does the maven-release-plugin discover the
username/password of the current user ...
With regards to determining the revision that is tagged, I need
William Ferguson a écrit :
Can someone please enlighten me on
1) If the SCM user/password has been been explicitly configured in your
POM or Settings, how does the maven-release-plugin discover the
username/password of the current user to supply to the SCM Eg
Subversion)? I need this
Can someone please enlighten me on
1) If the SCM user/password has been been explicitly configured in your
POM or Settings, how does the maven-release-plugin discover the
username/password of the current user to supply to the SCM Eg
Subversion)? I need this becxause my plugin will have to use
William Ferguson a écrit :
I have a plugin whose Mojo is executed as part of the
maven-release-pluigin preparationGoals (see
http://maven.apache.org/plugins/maven-release-plugin/examples/run-goals-
before-commit.html)
The Mojo executes OK, but I need to extract some of the info that has
I have a plugin whose Mojo is executed as part of the
maven-release-pluigin preparationGoals (see
http://maven.apache.org/plugins/maven-release-plugin/examples/run-goals-
before-commit.html)
The Mojo executes OK, but I need to extract some of the info that has
been accumulated by the maven
Hi,
we use SubVersion as our SCM, Eclipse as IDE and plan on using the
maven-release-plugin to manage our release process.
When we tag using the SubVersion Eclipse plugin (Subclipse), it updates
the 'subclipse:tags" SVN property on the target folder appending the tag
just created.
You have right, it should be better to give more information.
I was thinking about something like this [1] (cf section Filtering Source
Code)
But it's better to have a filter parameter directly in the
maven-javadoc-plugin.
It seems it's not the case for the moment. Open a jira for this enhancemen
t; 2007/3/16, CodingPlayer <[EMAIL PROTECTED]>:
>>
>>
>> Hi All,
>>
>> i just was wondering if there is any possibility to tell the
>> maven-release-plugin, to change ALL the source files as well?
>>
>> i mean, it would be nice, if the @version javadoc tag
Hi,
Isn't possible to use filtering with ${pom.version} ?
Rémy
2007/3/16, CodingPlayer <[EMAIL PROTECTED]>:
Hi All,
i just was wondering if there is any possibility to tell the
maven-release-plugin, to change ALL the source files as well?
i mean, it would be nice, if the @vers
Hi All,
i just was wondering if there is any possibility to tell the
maven-release-plugin, to change ALL the source files as well?
i mean, it would be nice, if the @version javadoc tag would be automatically
changed for each class.
For e.g. when releasing version 1.7 and changing to 1.8
> > Is this normal behaviour or did I just encounter a bug in the
> > release plugin? Is it even possible to prevent the plugin
> > from changing my pom according to 1-3? I haven't seen much about that
> > in the docs at
> > http://maven.apache.org/plugins/m
Thorsten Heit wrote on Thursday, March 15, 2007 5:28 PM:
> Hi,
>
> I'm actually evaluating Artifactory as repository proxy/cache
> and today played a bit with the maven-release-plugin
> (2.0-beta-5-SNAPSHOT; more precisely
> maven-release-plugin-2.0-beta-5-20070301.114416-
Hi,
I'm actually evaluating Artifactory as repository proxy/cache and today played
a bit with the maven-release-plugin (2.0-beta-5-SNAPSHOT; more precisely
maven-release-plugin-2.0-beta-5-20070301.114416-5.jar according to my local
repository).
My pom.xml started with the foll
I am doing some test with the maven release plugin.
I have two modules module1 and module2 with a pom parent.
The pom parent is defined as SNAPSHOT version and the two modules have a
reference to the pom parent.
When trying to release, here is the error:
[EMAIL PROTECTED]:~/dev/test/trunk$ mvn
Hi,
does anybody know when the version 2.0-beta-5 of maven-release-plugin will be
released?
thanx for a hint!
cheers,
chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Configure you release plugin to make install to you local repository
first, then release:prepare success.
maven-release-plugin
true
clean install
- markku
Randy L. Ringeisen wrote:
Hi. I have a question about the release plugin (Maven 2
Hi. I have a question about the release plugin (Maven 2 release plug-in
2.0 beta 4). I have a multi-level project as follows
Parent - artifact type is POM
-- Ejb - creates an EJB JAR
-- Ear - creates an EAR that includes the EJB jar
The Ear project depends on the Ejb jar that is created
mapped in svn:
> myproject/trunk/impl
> The reason for such mapping is that svn contains some other
> things (design
> dir) apart from standard project maven structure.
>
> The problem is: when I use the maven-release-plugin, the maven working
> directory is impl (because pom is
dir) apart from standard project maven structure.
The problem is: when I use the maven-release-plugin, the maven working
directory is impl (because pom is in impl) and all svn operations use dot
for source when using 'svn copy' ('svn copy . .../myproject/tags/0.1'). This
rds,
Marcel
- Original Message
From: Stephane Nicoll <[EMAIL PROTECTED]>
To: Maven Users List ; Marcel Schutte <[EMAIL
PROTECTED]>
Sent: Tuesday, January 16, 2007 3:42:54 PM
Subject: Re: Please release maven-release-plugin 2.3.1
you mean EAR?
On 1/16/07, Marcel Schutte <[EMAIL
2007 3:42:54 PM
Subject: Re: Please release maven-release-plugin 2.3.1
you mean EAR?
On 1/16/07, Marcel Schutte <[EMAIL PROTECTED]> wrote:
> Hello list (and especially Stéphane Nicoll),
>
> On maven-dev I see that the vote for a release of maven-release-plugin 2.3.1
> has been op
you mean EAR?
On 1/16/07, Marcel Schutte <[EMAIL PROTECTED]> wrote:
Hello list (and especially Stéphane Nicoll),
On maven-dev I see that the vote for a release of maven-release-plugin 2.3.1
has been open til january 12. I don't see any votes against it.
Could you please perform
Hello list (and especially Stéphane Nicoll),
On maven-dev I see that the vote for a release of maven-release-plugin 2.3.1
has been open til january 12. I don't see any votes against it.
Could you please perform the release?
Regards,
M
Thanks,
That save for manually doing the same thing.
rgds,
Markku
Antonio Parolini wrote:
I had the same issue.
I solved it by using the preparationGolas maven-release-plugin option in
order to do an install instead of integration-test:
clean install
cheers,
-tony
Markku
I had the same issue.
I solved it by using the preparationGolas maven-release-plugin option in
order to do an install instead of integration-test:
clean install
cheers,
-tony
Markku Saarela-2 wrote:
>
> For all ejb-client type depencies in multiproject system fails to
>
I hade the same issue.
I solved it by using the preparationGolas maven-release-plugin in order to
do an install instead of integration-test:
clean install
cheers,
-tony
Gilles Scokart wrote:
>
> Actually, to find a workaround, you don't need to deploy on a company
&
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 Mave
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
th
set preparationGoals=clean
On 11/17/06, Yan Zheng <[EMAIL PROTECTED]> wrote:
Hi,
I have a project with multiple sub-porjects. The "mvn release:prepare"
process failed on this project because I found that the prepare target
executes "clean integration-test" goals. The project is set up in
Hi,
I have a project with multiple sub-porjects. The "mvn release:prepare"
process failed on this project because I found that the prepare target
executes "clean integration-test" goals. The project is set up in such a
way that "clean install" executes fine, but not "clean integration-test".
Th
I ran into an issue with maven release plugin. The problem is caused by
xmlns value in project tag of the pom. If I use
xmlns="http://maven.autf-8.org/POM/4.0.0
", release plugin report problem. The problem is fixed after I changed to
xmlns="http://maven.apache.org/POM/4.0.0&
I ran into an issue with maven release plugin. The problem is caused by
xmlns value in project tag of the pom. If I use xmlns="
http://maven.autf-8.org/POM/4.0.0";, release plugin report problem. The
problem is fixed after I changed to xmlns="http://maven.apache.org/POM/4.0.0
Just a general question to the list:
Are you using just the maven-release-plugin for the generation of your releases?
I mean, the plugin is supposed to do "all the SCM stuff", but it
doesn't manage on its own the fact that it would be helpful (and
sometimes mandatory), to be
In my project I've got some ejb-client dependencies.
Every thing is working perfectly except maven-release-plugin.
It says that I don't have the ejb-client jars in the repository.
[INFO] Failed to resolve artifact.
Missing:
--
com.mycompany.services:project-servic
here.
Jorg
On 6/6/06, Dario Luis Coneglian Oliveros <[EMAIL PROTECTED]> wrote:
Hi there,
I've been trying to use maven-release-plugin to prepare a release, but
whenever I do that, it fails since I have a SVN precommit hook that
integrates with an issue tracking system which in turn
For all ejb-client type depencies in multiproject system fails to
resolve artifacts:
varma.yrpro.income
dbserviceejb
1.0-SNAPSHOT
ejb-client
produces error like this:
[INFO] Failed to resolve artifact.
Missing:
--
1) varma.yrpro.income:dbserviceejb:ejb-clie
; Thanks.
>
>
> -Original Message-
> From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 24, 2006 4:07 PM
> To: Maven Users List
> Subject: Re: maven-release-plugin how tos
>
>
> Sharma, Jaikumar wrote:
>> Dear Maven users,
>>
>
hanks.
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Monday, July 24, 2006 4:07 PM
To: Maven Users List
Subject: Re: maven-release-plugin how tos
Sharma, Jaikumar wrote:
Dear Maven users,
Could someone give an example of how maven-release-plugin is used
.
Thanks.
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Monday, July 24, 2006 4:07 PM
To: Maven Users List
Subject: Re: maven-release-plugin how tos
Sharma, Jaikumar wrote:
> Dear Maven users,
>
> Could someone give an example of how maven-release-
Sharma, Jaikumar wrote:
Dear Maven users,
Could someone give an example of how maven-release-plugin is used with
scm-proivder-plugin ?
Thanks for any help in advance.
Have you read this?
http://maven.apache.org/plugins/maven-release-plugin/howto.html
--
Dennis Lundberg
Dear Maven users,
Could someone give an example of how maven-release-plugin is used with
scm-proivder-plugin ?
Thanks for any help in advance.
Regards,
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and
ext:
http://www.nabble.com/Maven-Release-Plugin-Version-Problem-tf1902125.html#a5205412
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I am having some trouble with the Release Plug-In, and I am wondering if
anyone out there might have some thoughts on what the problem is.
Here is my setup:
parent-app
|
|-- pom.xml
|
|-- child-module-A
| |-- pom.xml
| |-- src
| |-- ...
|
|-- child-module-B
| |
| |-- pom.xml
| |
| |
Sounds like a perfectly valid usecase to me, create a ticket on
jira.codehaus.org/browse/MRELEASE in case nobody else chips in here.
Jorg
On 6/6/06, Dario Luis Coneglian Oliveros <[EMAIL PROTECTED]> wrote:
Hi there,
I've been trying to use maven-release-plugin to prepare a r
Hi there,
I've been trying to use maven-release-plugin to prepare a release, but
whenever I do that, it fails since I have a SVN precommit hook that
integrates with an issue tracking system which in turn waits for a
comment containing an issue number. Since release plugin adds it
: [m2] [maven-release-plugin] Unknown file status: 'X' as a result of
'mvn release:prepare'
I've been trying to make a release by running 'mvn release:prepare', but got a
warning saying that 'X' is an unknown file status.
I noticed the release
Yes, you need to enter a JIRA bug in the Maven SCM project with this detail.
-Original Message-
From: Dario Luis Coneglian Oliveros [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 23, 2006 2:53 PM
To: Maven Users List
Subject: [m2] [maven-release-plugin] Unknown file status: 'X' a
I've been trying to make a release by running 'mvn release:prepare',
but got a warning saying that 'X' is an unknown file status.
I noticed the release plugin runs the 'svn --non-interactive status'
command internally which prints the status of working copy files and
directories. Since one of t
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0 Beta 4.
http://maven.apache.org/plugins/maven-release-plugin/
You can run mvn -U to get the latest version of the plugin, or specify
the version in your project's plugin configur
Thanks Michael! It is really helpful ;-)
Regards, Jaikumar
-Original Message-
From: Michael Meyer [mailto:[EMAIL PROTECTED]
Sent: Friday, April 28, 2006 5:44 PM
To: Maven Users List
Subject: Re: [M2] : maven-release-plugin - about what ?
Hi Jaikumar,
the functionality of the release
lease-plugin - about what ?
Hi Jaikumar,
the functionality of the release plugin is described here:
http://maven.apache.org/plugins/maven-release-plugin/introduction.html
The plugin assumes that you use a scm system like Subversion or cvs and
have got an internal repository in your compan
Hi Jaikumar,
the functionality of the release plugin is described here:
http://maven.apache.org/plugins/maven-release-plugin/introduction.html
The plugin assumes that you use a scm system like Subversion or cvs and have
got an internal
repository in your company for releases.
Assume your
Dear Maven Users.
What is the purpose of maven-release-plugin ? what features basically it
provides ? I did not find right info about this plugin on Maven website.
Thanks for your help!
Regards, Jaikumar
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information
Hi,
I am having trouble configuring maven-release-plugin to connect to a CVS
repository using SSH. I've seen a few comments on the web suggesting
that this cannot be done from within Eclipse and that a CVS client needs
to be logged-in and running at the time of calling the plugin. Is
Hi all,
I just managed to use "maven-release-plugin" (2.0-beta-3) to automate
the release
and tag process within my projects.
Anything works fine, except that the generated and
entries are created false.
I have multiple projects in one subversion repository. So my "trunk&qu
2006/3/16, Fredy <[EMAIL PROTECTED]>:
> Hi,
> i've trouble with 2.0-beta-3 and a newer version may be better?!
@see https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-release-plugin
> Thanks Fredy
Jacek
--
Jacek Laskowski
http://
Hi,
i've trouble with 2.0-beta-3 and a newer version may be better?!
Thanks Fredy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Gabriel, Andreas a écrit :
Hi!
I somehow don't manage to get the maven-release-plugin running with CVS.
When I run the mvn release:prepare target, the plugin complains
"password is required" when verifying that no local changes were made. I
found out, that the plugin is i
On 2/13/06, Gabriel, Andreas <[EMAIL PROTECTED]> wrote:
>
>
> Hi!
>
>
>
> I somehow don't manage to get the maven-release-plugin running with CVS.
> When I run the mvn release:prepare target, the plugin complains
> "password is required" when veri
Hi!
I somehow don't manage to get the maven-release-plugin running with CVS.
When I run the mvn release:prepare target, the plugin complains
"password is required" when verifying that no local changes were made. I
found out, that the plugin is ignoring the "-D
project.scm
Should this be considered a bug?
When using maven-release-plugin the POM gets its version updated (for
instance from 0.2-SNAPSHOT to 0.2, when releasing version 0.2 of the
artifact) even if the scm provider fails to tag the release onto a
Subversion repository, because of a wrong URL string or
Thanks, it works!
Sombody should update the plugIn Site
http://maven.apache.org/plugins/maven-release-plugin/source-repository.html
Fredy
"Maven Users List" schrieb am 20.01.06 23:08:13:
The M2 plugins have moved in SVN. The new location is:
http://svn.apache.org/viewcvs.cgi/mav
The M2 plugins have moved in SVN. The new location is:
http://svn.apache.org/viewcvs.cgi/maven/plugins/trunk/maven-release-plugin/
--
Dennis Lundberg
[EMAIL PROTECTED] wrote:
Hey all,
i would have a look to the maven-release-plugin, but i cannot connect to:
http://svn.apache.org/repos/asf
Hey all,
i would have a look to the maven-release-plugin, but i cannot connect to:
http://svn.apache.org/repos/asf/maven/components/trunk/maven-plugins/maven-release-plugin
Also the web access:
http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-plugins/maven-release-plugin
The
t the plugin is doing--not just stating the
> options.
> ..David..
>
> -Original Message-
> From: Chris Hagmann [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 04, 2006 2:25 PM
> To: users@maven.apache.org
> Subject: [m2] Any additional docs for plugin maven-relea
PROTECTED]
Sent: Wednesday, January 04, 2006 2:25 PM
To: users@maven.apache.org
Subject: [m2] Any additional docs for plugin maven-release-plugin?
Are there any additional docs for the
maven-release-plugin? The docs on maven.apache.org only show the
configuration, but there is nothing related to how to
Are there any additional docs for the
maven-release-plugin? The docs on maven.apache.org
only show the configuration, but there is nothing
related to how to use it, or what those configuration
parameters mean.
Any pointer would be helpful.
Thanks,
Chris
clearer
> > > what tagBase does/is?
> > >
> > > - Brett
> > >
> > > On 11/9/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > > > Brett thanks for taking the time to look into my issues with the
> > > > maven-release plugin.
> >
[EMAIL PROTECTED]
> Sent: Wednesday, November 09, 2005 6:21 PM
> To: Maven Users List
> Subject: Re: [M2] - maven-release-plugin cannot load SCM provider
>
> I would be more than happy to help out with any documentation.
> What is the process for improving documents? Write somethin
ECTED]> wrote:
> > > Brett thanks for taking the time to look into my issues with the
> > > maven-release plugin.
> > > I was able to deploy a release locally. I just thought that because
> > > their was a jira issue with the tagBase property for t
e docs to make it clearer
> what tagBase does/is?
>
> - Brett
>
> On 11/9/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> > Brett thanks for taking the time to look into my issues with the
> > maven-release plugin.
> > I was able to deploy a release locally.
No problem. Perhaps you could help reword the docs to make it clearer
what tagBase does/is?
- Brett
On 11/9/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote:
> Brett thanks for taking the time to look into my issues with the
> maven-release plugin.
> I was able to deploy a release l
Brett thanks for taking the time to look into my issues with the
maven-release plugin.
I was able to deploy a release locally. I just thought that because
their was a jira issue with the tagBase property for the plugin I
should be putting the whole URL with the prexfix because the URL
specified
s paths in the SCM URL before without
> > > > issues, but its worth trying:
> > > >
> > > > scm|svn|file:///d:/subversion...
> > > >
> > > > hth,
> > > > Brett
> > > >
> > > > On 11/8/05, Trent Ros
I was prefixing the URLs with
> > > > > > "scm:svn", but then I still had a problem so thought about exploring
> > > > > > and that is why I asked about setting the scm provider in a
> > > > > > different
> > > > > &
Ls with
> > > > > "scm:svn", but then I still had a problem so thought about exploring
> > > > > and that is why I asked about setting the scm provider in a different
> > > > > manner. I have again used these prefixes and I still get a prob
wrote:
> > This is the SCM URL for the project:
> >
> >
> > scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk
> >
> >
> > and the plugin is configured with the following tagbase element:
> >
> >
> > org.
_data/repositories/my_repo/bug-control-model/trunk
>
>
> and the plugin is configured with the following tagbase element:
>
>
> org.apache.maven.plugins
> maven-release-plugin
> 2.0-beta-3
>
> scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-
This is the SCM URL for the project:
scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk
and the plugin is configured with the following tagbase element:
org.apache.maven.plugins
maven-release-plugin
2.0-beta-3
scm:svn:file:///D:/subversion-1.2.0_data
plugin is planned to allow developers to aquire a project without a
> pom.xml and then to complete the every day version control tasks?
> With this in mind is it best to view the maven-release plugin as a
> component that should be used to release code for a repository instead
> of comp
nd then to complete the every day version control tasks?
With this in mind is it best to view the maven-release plugin as a
component that should be used to release code for a repository instead
of completing a checkout/checkin, copy etc manually? I just want to
know the thoughts behind e
sition where I want to tag and release a version. I really want to
> use maven-release-plugin, but I am having problems. I am using SVN on
> the local file system. I have been using subclipse with eclipse 3.1.1
> to access the source code and so I am sure the SVN setup is fine.
>
>
I have been using Maven 2 for my current project and I am now at a
position where I want to tag and release a version. I really want to
use maven-release-plugin, but I am having problems. I am using SVN on
the local file system. I have been using subclipse with eclipse 3.1.1
to access the
, but I don't know how to do this. Anyone any suggestions?
Michael
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, 20 October 2005 12:36 AM
To: Maven Users List
Subject: Réf. : RE: [m2] Maven release plugin and CVS: bug?
Hi David,
I use
Wednesday, October 19, 2005 4:15 AM
To: users@maven.apache.org
Subject: RE: [m2] Maven release plugin and CVS: bug?
Michael,
thanks for your answer. Unfortunately, although I've followed every step
you gave to me, I still get the same error:
701 - 800 of 808 matches
Mail list logo
