Or define the params for the release-plugin by using the properties. Then the users can define them in their settings.xml and don't have to specify it on command line (unless they really want to). As a user I would appreciate that.
/Anders On Mon, Dec 6, 2010 at 13:46, Kiss Tibor <kiss.ti...@gmail.com> wrote: > Yes, that issue. > > Pasing -Dusername= .. -Dpassword= .. params into the command line while > calling release plugin will suffice for me. > > Thank you! > Tibor > > On Mon, Dec 6, 2010 at 11:54 AM, Anders Hammar <and...@hammar.net> wrote: > > > You've run into this issue: > > http://jira.codehaus.org/browse/MRELEASE-128 > > > > For svn and username/password, it should be possible to leave them > outside > > of the url. One way is to use the username/password parameters of the > > maven-release-plugin. I believe another is to have the credentials set > > within the svn client being used. > > > > /Anders > > > > On Mon, Dec 6, 2010 at 11:08, Kiss Tibor <kiss.ti...@gmail.com> wrote: > > > > > Hi, > > > > > > If I use scm tag inside my project like this > > > scm:svn:https://${svn.username}:${passwo...@server_name > > /path_to_repository > > > while in my ~/.m2/settings.xml I have the substitution values set as > > > properties, > > > then I release the project with maven-release-plugin, > > > I get commited in Subversion a substituted version of scm tag with > clear > > > text password. > > > > > > Is there a possibility to use scm tag which is necessary for release > > > plugin, > > > but not getting commited in the clear text password? > > > > > > What would be the patter of scm tag in case of authentication with > client > > > side certificates? > > > > > > Cheers, > > > Tibor > > > > > >
