You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Aaron Anderson <ni...@yahoo.com> on 2006/05/04 21:24:41 UTC
svn authentication with m2 release plugin
I am using subversion for scm and would like to use the m2 release plugin. I run release:prepare but I always get an "authorization failed" error from svn. After doing a network trace I can that the svn client is sending my operating system credentials (!) instead of my subversion credentials. I did not modify the svn cached credentials setting and can easily run svn up, co, etc without entering credentials and the credentials sent are correct.
Why is svn not sending the proper cached credentials when run from the release plugin? Is there a way to specify the scm userID & pwd from the command line as there was with the m1 release plugin?
TIA
Re: overriding maven-core default implementations of components
Posted by Alexandre Poitras <al...@gmail.com>.
I don't think it quite doable at the moment but there are some discussions
for 2.1 :
http://docs.codehaus.org/display/MAVEN/Substitution+of+Custom+Maven+Components
On 5/5/06, Aaron Anderson <ni...@yahoo.com> wrote:
>
> The maven-core artifact has a META-INF/plexus/components.xml that defines
> the default implementations for all the components. One can create a plugin
> that has it's own component.xml override and if a POM has this plugin
> configured with extention->true then the override will occur.
>
> I would like to take this a step further and somehow configure the default
> maven installation to use a custom component.xml file with custom
> implementations. For example, in the absence of a POM I would like the
> archetype plugin to use my implementation of the Archetype interface instead
> of the default one.
>
> Is there a way to modify the default super POM that all POM's extend from
> to use a custom plugin that defines new implementations for components? Is
> modifying and creating a custom maven-core artifact the only way to change
> the default implementations for components?
>
>
Re: svn authentication with m2 release plugin
Posted by lagrangien8 <pm...@dictao.com>.
Thank you,
this answer resolve my problem
since this morning, i was not able to use the mvn release : prepare command
due to an authentification problem
now it work very well
thx
--
View this message in context: http://maven.40175.n5.nabble.com/svn-authentication-with-m2-release-plugin-tp63557p4534992.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
overriding maven-core default implementations of components
Posted by Aaron Anderson <ni...@yahoo.com>.
The maven-core artifact has a META-INF/plexus/components.xml that defines the default implementations for all the components. One can create a plugin that has it's own component.xml override and if a POM has this plugin configured with extention->true then the override will occur.
I would like to take this a step further and somehow configure the default maven installation to use a custom component.xml file with custom implementations. For example, in the absence of a POM I would like the archetype plugin to use my implementation of the Archetype interface instead of the default one.
Is there a way to modify the default super POM that all POM's extend from to use a custom plugin that defines new implementations for components? Is modifying and creating a custom maven-core artifact the only way to change the default implementations for components?
Re: svn authentication with m2 release plugin
Posted by Aaron Anderson <ni...@yahoo.com>.
thanks,
release:prepare -Dusername=myid =Dpassword=mypassword
did the trick
Alexandre Poitras <al...@gmail.com> wrote:
There is a mistake there, the plugin uses "username" ("user.name" is
the OS user in Java).
On 5/4/06, Andrew Kreps wrote:
> I'm not using SVN, but on the Maven site I found this:
>
>
> Use a different username in the SCM server than he one in the operating system:
>
> Run mvn -Duser.name=your_username release:prepare
>
>
> It's on this page:
> http://maven.apache.org/plugins/maven-release-plugin/howto.html
>
> Hopefully that will help.
>
>
> On 5/4/06, Aaron Anderson wrote:
> > I am using subversion for scm and would like to use the m2 release plugin. I run release:prepare but I always get an "authorization failed" error from svn. After doing a network trace I can that the svn client is sending my operating system credentials (!) instead of my subversion credentials. I did not modify the svn cached credentials setting and can easily run svn up, co, etc without entering credentials and the credentials sent are correct.
> >
> > Why is svn not sending the proper cached credentials when run from the release plugin? Is there a way to specify the scm userID & pwd from the command line as there was with the m1 release plugin?
> >
> > TIA
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: svn authentication with m2 release plugin
Posted by Alexandre Poitras <al...@gmail.com>.
There is a mistake there, the plugin uses "username" ("user.name" is
the OS user in Java).
On 5/4/06, Andrew Kreps <an...@gmail.com> wrote:
> I'm not using SVN, but on the Maven site I found this:
>
>
> Use a different username in the SCM server than he one in the operating system:
>
> Run mvn -Duser.name=your_username release:prepare
>
>
> It's on this page:
> http://maven.apache.org/plugins/maven-release-plugin/howto.html
>
> Hopefully that will help.
>
>
> On 5/4/06, Aaron Anderson <ni...@yahoo.com> wrote:
> > I am using subversion for scm and would like to use the m2 release plugin. I run release:prepare but I always get an "authorization failed" error from svn. After doing a network trace I can that the svn client is sending my operating system credentials (!) instead of my subversion credentials. I did not modify the svn cached credentials setting and can easily run svn up, co, etc without entering credentials and the credentials sent are correct.
> >
> > Why is svn not sending the proper cached credentials when run from the release plugin? Is there a way to specify the scm userID & pwd from the command line as there was with the m1 release plugin?
> >
> > TIA
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: svn authentication with m2 release plugin
Posted by Andrew Kreps <an...@gmail.com>.
I'm not using SVN, but on the Maven site I found this:
Use a different username in the SCM server than he one in the operating system:
Run mvn -Duser.name=your_username release:prepare
It's on this page:
http://maven.apache.org/plugins/maven-release-plugin/howto.html
Hopefully that will help.
On 5/4/06, Aaron Anderson <ni...@yahoo.com> wrote:
> I am using subversion for scm and would like to use the m2 release plugin. I run release:prepare but I always get an "authorization failed" error from svn. After doing a network trace I can that the svn client is sending my operating system credentials (!) instead of my subversion credentials. I did not modify the svn cached credentials setting and can easily run svn up, co, etc without entering credentials and the credentials sent are correct.
>
> Why is svn not sending the proper cached credentials when run from the release plugin? Is there a way to specify the scm userID & pwd from the command line as there was with the m1 release plugin?
>
> TIA
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org