please create a jira!

I'll try to go over a few scm issues this weekend, maybe I have time for this 
too.

LieGrue,
strub



----- Original Message ----
> From: Andrei Solntsev <[email protected]>
> To: Maven Users List <[email protected]>
> Sent: Friday, August 14, 2009 9:23:28 AM
> Subject: RE: SCM plugin password encryption
> 
> We just need to add this feature to maven-scm-plugin.
> 
> We could use maven-sql-plugin as an example, it can read encrypted DB
> password in the same manner as repository credentials.
> 
> Andrei Solntsev,
> Software Developer,
> HireRight Estonia
> 
> 
> 
> -----Original Message-----
> From: KURT TOMETICH [mailto:[email protected]] 
> Sent: Thursday, August 13, 2009 7:07 PM
> To: [email protected]
> Subject: SCM plugin password encryption
> 
> 
> I feel like I must be missing something because I have yet found a way
> to encrypt my SCM password in my Maven POM.  I am using the maven
> release plugin and need to use some credentials on the CI server, but I
> don't want to store the password in clear text.  Is there a way to
> encrypt the password and reference it in the Maven SCM plugin?
> 
> I've tried using the Maven encryption guide
> (http://maven.apache.org/guides/mini/guide-encryption.html) which works
> well for encrypting Maven repository credentials.  The problem is that
> you can't (from what I've seen) reference the id for a server in the
> Maven SCM plugin.  Here's an example of what I'd like to see in the POM:
> 
> 
>       org.apache.maven.plugins
>       maven-scm-plugin
>       
>             kurt.tometich
>             {encrypted password here}
>       
> 
> 
> 
> Any ideas of how to do this would be welcome.  Thanks in advance.
> 
> Kurt
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]



      

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to