You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@maven.apache.org by Trent Rosenbaum <tr...@gmail.com> on 2005/11/06 18:24:44 UTC

[M2] - maven-release-plugin cannot load SCM provider

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 source code and so I am sure the SVN setup is fine.

I get the following error back from maven:

[INFO] An error is occurred in the status process.

Embedded error: Can't load the scm provider.
The scm url is invalid.

I have looked at the mini-guide and have the following setup in my pom.xml:

<scm>
<developerConnection>
file:///D:/subversion-1.2.0_data/repositories/my_repo/<my project>/trunk
</developerConnection>
</scm>

and the plugin is setup with the following values

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<tagBase>
file:///D:/subversion-1.2.0_data/repositories/my_repo/<my project>/tags
</tagBase>
</configuration>
</plugin>

I then run the following command:

mvn release:prepare

Within the mini-guide the example shows the use of a SVN URL over SSH,
I went back and double checked the valid URLs for SVN, (using the
Subversion docs) and the above developerConnection String looks fine
to me.

I have been searching the mailing list and different sites for any
info.  How do I define the SCM provider to be used by the plugin?  The
maven-release-plugin docs show a scmManager element for the
configuration but I am not sure how to use it.  If the
developerConnection URL contained the svn:// or svn+ssh:// then I
could understand that the plugin would be able to locate and load the
provider.

Does anyone have any thoughts on this problem?
Many thanks

Trent

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [M2] - maven-release-plugin cannot load SCM provider

Posted by Trent Rosenbaum <tr...@gmail.com>.

I just thought I would send a quick email mentioning that I have
attached an update to the content of the "Guide to Releasing" mini
guide.  The following issue was raised to keep track of the update.

http://jira.codehaus.org/browse/MNG-1564

Any feedback would be great.
Hope this helps
Trent

On 10/11/05, Jason van Zyl <ja...@maven.org> wrote:
> On Thu, 2005-11-10 at 00:20 +0000, Trent Rosenbaum wrote:
> > I would be more than happy to help out with any documentation.
> > What is the process for improving documents?  Write something then attach it to
> > a jira issue to it can be picked up?
>
> Yes, there are several components for documentation.
>
> > Trent
> >
> > On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > > No problem. Perhaps you could help reword the docs to make it clearer
> > > what tagBase does/is?
> > >
> > > - Brett
> > >
> > > On 11/9/05, Trent Rosenbaum <tr...@gmail.com> 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 the plugin I
> > > > should be putting the whole URL with the prexfix because the URL
> > > > specified int he developerConnection is being used to construct the
> > > > tag  URL.
> > > >
> > > > Trent
> > > >
> > > > On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > Ah, sorry for the confusion.
> > > > >
> > > > > nulike the connections, tagBase is just the SVN URL (omit scm:svn) as
> > > > > it is an SVN specific property.
> > > > >
> > > > > - Brett
> > > > >
> > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > This is the feedback I got from running mvn release:prepare
> > > > > >
> > > > > > [INFO] [release:prepare]
> > > > > > [INFO] What tag name should be used?
> > > > > > 0.1.2
> > > > > > [INFO] Tagging release with the label 0.1.2.
> > > > > > Provider message:
> > > > > > The svn tag command failed.
> > > > > > Command output:
> > > > > > svn: Error resolving case of 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie
> > > > > > s\my_repo\bug-control-model\tags\0.1.2'
> > > > > >
> > > > > > [INFO] -------------------------------------------------------------------------
> > > > > > ---
> > > > > > [ERROR] BUILD ERROR
> > > > > > [INFO] -------------------------------------------------------------------------
> > > > > > ---
> > > > > > [INFO] An error is occurred in the tag process.
> > > > > >
> > > > > >
> > > > > > The URL for the tagBase is identical to the URL supplied within the
> > > > > > developerConnection element but "tags" replaces "trunk".
> > > > > >
> > > > > > Trent
> > > > > >
> > > > > >
> > > > > > On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > The bug is for the default of ../tags when used instead of a tagbase
> > > > > > > as you have, so it is different.
> > > > > > >
> > > > > > > Above that exception, there should have been output from the svn
> > > > > > > command. Does that reveal anything?
> > > > > > >
> > > > > > > - Brett
> > > > > > >
> > > > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > > > I did not have this pom.xml checked  into SVN and so it was trying to
> > > > > > > > work with the previous revision of my file and this did not have a SCM
> > > > > > > > URL defined.  I have been able to get the plugin to prompt me for
> > > > > > > > input regarding the tags, but I am falling over in the tagging process
> > > > > > > > with the following exception:
> > > > > > > >
> > > > > > > > Is this the same exception that has lead to the creation of the
> > > > > > > > following issue in jira?
> > > > > > > >
> > > > > > > > http://jira.codehaus.org/browse/MNG-883
> > > > > > > >
> > > > > > > >
> > > > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in
> > > > > > > > the tag process.
> > > > > > > >
> > > > > > > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred
> > > > > > > > in the tag process.
> > > > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
> > > > > > > > eReleaseMojo.java:1414)
> > > > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
> > > > > > > > leaseMojo.java:246)
> > > > > > > >
> > > > > > > >
> > > > > > > > thanks for taking to time to look into this.
> > > > > > > > Trent
> > > > > > > >
> > > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > > I thought I had used windows paths in the SCM URL before without
> > > > > > > > > issues, but its worth trying:
> > > > > > > > >
> > > > > > > > > scm|svn|file:///d:/subversion...
> > > > > > > > >
> > > > > > > > > hth,
> > > > > > > > > Brett
> > > > > > > > >
> > > > > > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > > > > > This is the SCM URL for the project:
> > > > > > > > > >
> > > > > > > > > > <scm>
> > > > > > > > > > <developerConnection>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk</developerConnection>
> > > > > > > > > > </scm>
> > > > > > > > > >
> > > > > > > > > > and the plugin is configured with the following tagbase element:
> > > > > > > > > >
> > > > > > > > > > <plugin>
> > > > > > > > > > <groupId>org.apache.maven.plugins</groupId>
> > > > > > > > > > <artifactId>maven-release-plugin</artifactId>
> > > > > > > > > > <version>2.0-beta-3</version>
> > > > > > > > > > <configuration>
> > > > > > > > > > <tagBase>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags</tagBase>
> > > > > > > > > > </configuration>
> > > > > > > > > > </plugin>
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > > > > They both use the same library - so the release plugin is for
> > > > > > > > > > > automating release related tasks, the scm plugin for development
> > > > > > > > > > > related tasks.
> > > > > > > > > > >
> > > > > > > > > > > Can you please repost the full SCM URL that gave you this error -
> > > > > > > > > > > there is still something wrong with it.
> > > > > > > > > > >
> > > > > > > > > > > - Brett
> > > > > > > > > > >
> > > > > > > > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > > > > > > > Thanks for the reply.
> > > > > > > > > > > > When I started to use the plugin 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
> > > > > > > > > > > > manner.  I have again used these prefixes and I still get a problem.
> > > > > > > > > > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.
> > > > > > > > > > > >
> > > > > > > > > > > > During my reading of the site I noticed that both the scm and the
> > > > > > > > > > > > release plugin are similar.  Is it right to think that the maven-scm
> > > > > > > > > > > > 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 completing a checkout/checkin, copy etc manually?  I just want to
> > > > > > > > > > > > know the thoughts behind each plugin.
> > > > > > > > > > > >
> > > > > > > > > > > > ----- Maven output -----
> > > > > > > > > > > >
> > > > > > > > > > > > [ERROR] BUILD ERROR
> > > > > > > > > > > > [INFO] ----------------------------------------------------
> > > > > > > > > > > > ---
> > > > > > > > > > > > [INFO] An error is occurred in the status process.
> > > > > > > > > > > >
> > > > > > > > > > > > Embedded error: Can't load the scm provider.
> > > > > > > > > > > > The scm url is invalid.
> > > > > > > > > > > >
> > > > > > > > > > > > ----- stack trace ------
> > > > > > > > > > > >
> > > > > > > > > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> > > > > > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > > > > > > > cmHelper.java:104)
> > > > > > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > > > > > > > > > > r.java:169)
> > > > > > > > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > > > > > > > > > > fications(PrepareReleaseMojo.java:510)
> > > > > > > > > > > >         ... 19 more
> > > > > > > > > > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
> > > > > > > > > > > > s invalid.
> > > > > > > > > > > >         at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > > > > > > > > > > itory(SvnScmProvider.java:84)
> > > > > > > > > > > >         at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > > > > > > > > > > ry(DefaultScmManager.java:126)
> > > > > > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > > > > > > > cmHelper.java:82)
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > > > > > > Your SCM URL should start:
> > > > > > > > > > > > >
> > > > > > > > > > > > > scm:svn:file://...
> > > > > > > > > > > > >
> > > > > > > > > > > > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > > > > > > > > > > > in the second argument above.
> > > > > > > > > > > > >
> > > > > > > > > > > > > - Brett
> > > > > > > > > > > >
> > > > > > > > > > > > ---------------------------------------------------------------------
> > > > > > > > > > > > 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
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ---------------------------------------------------------------------
> > > > > > > > > > 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
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > > ---------------------------------------------------------------------
> > > > > > > > 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
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > 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
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> --
> jvz.
>
> Jason van Zyl
> jason at maven.org
> http://maven.apache.org
>
> Three people can keep a secret provided two of them are dead.
>
>  -- Unknown
>
>
> ---------------------------------------------------------------------
> 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: [M2] - maven-release-plugin cannot load SCM provider

Posted by Jason van Zyl <ja...@maven.org>.

On Thu, 2005-11-10 at 00:20 +0000, Trent Rosenbaum wrote:
> I would be more than happy to help out with any documentation.
> What is the process for improving documents?  Write something then attach it to
> a jira issue to it can be picked up?

Yes, there are several components for documentation.

> Trent
> 
> On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > No problem. Perhaps you could help reword the docs to make it clearer
> > what tagBase does/is?
> >
> > - Brett
> >
> > On 11/9/05, Trent Rosenbaum <tr...@gmail.com> 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 the plugin I
> > > should be putting the whole URL with the prexfix because the URL
> > > specified int he developerConnection is being used to construct the
> > > tag  URL.
> > >
> > > Trent
> > >
> > > On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > Ah, sorry for the confusion.
> > > >
> > > > nulike the connections, tagBase is just the SVN URL (omit scm:svn) as
> > > > it is an SVN specific property.
> > > >
> > > > - Brett
> > > >
> > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > This is the feedback I got from running mvn release:prepare
> > > > >
> > > > > [INFO] [release:prepare]
> > > > > [INFO] What tag name should be used?
> > > > > 0.1.2
> > > > > [INFO] Tagging release with the label 0.1.2.
> > > > > Provider message:
> > > > > The svn tag command failed.
> > > > > Command output:
> > > > > svn: Error resolving case of 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie
> > > > > s\my_repo\bug-control-model\tags\0.1.2'
> > > > >
> > > > > [INFO] -------------------------------------------------------------------------
> > > > > ---
> > > > > [ERROR] BUILD ERROR
> > > > > [INFO] -------------------------------------------------------------------------
> > > > > ---
> > > > > [INFO] An error is occurred in the tag process.
> > > > >
> > > > >
> > > > > The URL for the tagBase is identical to the URL supplied within the
> > > > > developerConnection element but "tags" replaces "trunk".
> > > > >
> > > > > Trent
> > > > >
> > > > >
> > > > > On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > The bug is for the default of ../tags when used instead of a tagbase
> > > > > > as you have, so it is different.
> > > > > >
> > > > > > Above that exception, there should have been output from the svn
> > > > > > command. Does that reveal anything?
> > > > > >
> > > > > > - Brett
> > > > > >
> > > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > > I did not have this pom.xml checked  into SVN and so it was trying to
> > > > > > > work with the previous revision of my file and this did not have a SCM
> > > > > > > URL defined.  I have been able to get the plugin to prompt me for
> > > > > > > input regarding the tags, but I am falling over in the tagging process
> > > > > > > with the following exception:
> > > > > > >
> > > > > > > Is this the same exception that has lead to the creation of the
> > > > > > > following issue in jira?
> > > > > > >
> > > > > > > http://jira.codehaus.org/browse/MNG-883
> > > > > > >
> > > > > > >
> > > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in
> > > > > > > the tag process.
> > > > > > >
> > > > > > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred
> > > > > > > in the tag process.
> > > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
> > > > > > > eReleaseMojo.java:1414)
> > > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
> > > > > > > leaseMojo.java:246)
> > > > > > >
> > > > > > >
> > > > > > > thanks for taking to time to look into this.
> > > > > > > Trent
> > > > > > >
> > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > I thought I had used windows paths in the SCM URL before without
> > > > > > > > issues, but its worth trying:
> > > > > > > >
> > > > > > > > scm|svn|file:///d:/subversion...
> > > > > > > >
> > > > > > > > hth,
> > > > > > > > Brett
> > > > > > > >
> > > > > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > > > > This is the SCM URL for the project:
> > > > > > > > >
> > > > > > > > > <scm>
> > > > > > > > > <developerConnection>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk</developerConnection>
> > > > > > > > > </scm>
> > > > > > > > >
> > > > > > > > > and the plugin is configured with the following tagbase element:
> > > > > > > > >
> > > > > > > > > <plugin>
> > > > > > > > > <groupId>org.apache.maven.plugins</groupId>
> > > > > > > > > <artifactId>maven-release-plugin</artifactId>
> > > > > > > > > <version>2.0-beta-3</version>
> > > > > > > > > <configuration>
> > > > > > > > > <tagBase>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags</tagBase>
> > > > > > > > > </configuration>
> > > > > > > > > </plugin>
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > > > They both use the same library - so the release plugin is for
> > > > > > > > > > automating release related tasks, the scm plugin for development
> > > > > > > > > > related tasks.
> > > > > > > > > >
> > > > > > > > > > Can you please repost the full SCM URL that gave you this error -
> > > > > > > > > > there is still something wrong with it.
> > > > > > > > > >
> > > > > > > > > > - Brett
> > > > > > > > > >
> > > > > > > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > > > > > > Thanks for the reply.
> > > > > > > > > > > When I started to use the plugin 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
> > > > > > > > > > > manner.  I have again used these prefixes and I still get a problem.
> > > > > > > > > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.
> > > > > > > > > > >
> > > > > > > > > > > During my reading of the site I noticed that both the scm and the
> > > > > > > > > > > release plugin are similar.  Is it right to think that the maven-scm
> > > > > > > > > > > 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 completing a checkout/checkin, copy etc manually?  I just want to
> > > > > > > > > > > know the thoughts behind each plugin.
> > > > > > > > > > >
> > > > > > > > > > > ----- Maven output -----
> > > > > > > > > > >
> > > > > > > > > > > [ERROR] BUILD ERROR
> > > > > > > > > > > [INFO] ----------------------------------------------------
> > > > > > > > > > > ---
> > > > > > > > > > > [INFO] An error is occurred in the status process.
> > > > > > > > > > >
> > > > > > > > > > > Embedded error: Can't load the scm provider.
> > > > > > > > > > > The scm url is invalid.
> > > > > > > > > > >
> > > > > > > > > > > ----- stack trace ------
> > > > > > > > > > >
> > > > > > > > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> > > > > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > > > > > > cmHelper.java:104)
> > > > > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > > > > > > > > > r.java:169)
> > > > > > > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > > > > > > > > > fications(PrepareReleaseMojo.java:510)
> > > > > > > > > > >         ... 19 more
> > > > > > > > > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
> > > > > > > > > > > s invalid.
> > > > > > > > > > >         at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > > > > > > > > > itory(SvnScmProvider.java:84)
> > > > > > > > > > >         at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > > > > > > > > > ry(DefaultScmManager.java:126)
> > > > > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > > > > > > cmHelper.java:82)
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > > > > > Your SCM URL should start:
> > > > > > > > > > > >
> > > > > > > > > > > > scm:svn:file://...
> > > > > > > > > > > >
> > > > > > > > > > > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > > > > > > > > > > in the second argument above.
> > > > > > > > > > > >
> > > > > > > > > > > > - Brett
> > > > > > > > > > >
> > > > > > > > > > > ---------------------------------------------------------------------
> > > > > > > > > > > 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
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > ---------------------------------------------------------------------
> > > > > > > > > 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
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > ---------------------------------------------------------------------
> > > > > > > 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
> > > > > >
> > > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > 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
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

Three people can keep a secret provided two of them are dead.

 -- Unknown


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: [M2] - maven-release-plugin cannot load SCM provider

Posted by Jeff Jensen <je...@upstairstechnology.com>.

If I may suggest, what has worked for me in the past is to patch an existing
document file (they are in subversion) and attach to a JIRA like you said.
This makes is easier on the committers to review and apply - a patch.


> -----Original Message-----
> From: Trent Rosenbaum [mailto:trent.j.rosenbaum@gmail.com] 
> 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 something 
> then attach it to a jira issue to it can be picked up?
> 
> Trent
> 
> On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > No problem. Perhaps you could help reword the docs to make 
> it clearer 
> > what tagBase does/is?
> >
> > - Brett
> >
> > On 11/9/05, Trent Rosenbaum <tr...@gmail.com> 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 the plugin I 
> > > should be putting the whole URL with the prexfix because the URL 
> > > specified int he developerConnection is being used to 
> construct the 
> > > tag  URL.
> > >
> > > Trent
> > >
> > > On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > Ah, sorry for the confusion.
> > > >
> > > > nulike the connections, tagBase is just the SVN URL 
> (omit scm:svn) 
> > > > as it is an SVN specific property.
> > > >
> > > > - Brett
> > > >
> > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > This is the feedback I got from running mvn release:prepare
> > > > >
> > > > > [INFO] [release:prepare]
> > > > > [INFO] What tag name should be used?
> > > > > 0.1.2
> > > > > [INFO] Tagging release with the label 0.1.2.
> > > > > Provider message:
> > > > > The svn tag command failed.
> > > > > Command output:
> > > > > svn: Error resolving case of 
> > > > > 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie
> > > > > s\my_repo\bug-control-model\tags\0.1.2'
> > > > >
> > > > > [INFO] 
> > > > > 
> ----------------------------------------------------------------
> > > > > ---------
> > > > > ---
> > > > > [ERROR] BUILD ERROR
> > > > > [INFO] 
> > > > > 
> ----------------------------------------------------------------
> > > > > ---------
> > > > > ---
> > > > > [INFO] An error is occurred in the tag process.
> > > > >
> > > > >
> > > > > The URL for the tagBase is identical to the URL 
> supplied within 
> > > > > the developerConnection element but "tags" replaces "trunk".
> > > > >
> > > > > Trent
> > > > >
> > > > >
> > > > > On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > The bug is for the default of ../tags when used 
> instead of a 
> > > > > > tagbase as you have, so it is different.
> > > > > >
> > > > > > Above that exception, there should have been output 
> from the 
> > > > > > svn command. Does that reveal anything?
> > > > > >
> > > > > > - Brett
> > > > > >
> > > > > > On 11/8/05, Trent Rosenbaum 
> <tr...@gmail.com> wrote:
> > > > > > > I did not have this pom.xml checked  into SVN and 
> so it was 
> > > > > > > trying to work with the previous revision of my file and 
> > > > > > > this did not have a SCM URL defined.  I have been able to 
> > > > > > > get the plugin to prompt me for input regarding the tags, 
> > > > > > > but I am falling over in the tagging process with 
> the following exception:
> > > > > > >
> > > > > > > Is this the same exception that has lead to the 
> creation of 
> > > > > > > the following issue in jira?
> > > > > > >
> > > > > > > http://jira.codehaus.org/browse/MNG-883
> > > > > > >
> > > > > > >
> > > > > > > 
> org.apache.maven.lifecycle.LifecycleExecutionException: An 
> > > > > > > error is occurred in the tag process.
> > > > > > >
> > > > > > > Caused by: 
> org.apache.maven.plugin.MojoExecutionException: 
> > > > > > > An error is occurred in the tag process.
> > > > > > >         at 
> > > > > > > 
> org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelea
> > > > > > > se(Prepar
> > > > > > > eReleaseMojo.java:1414)
> > > > > > >         at 
> > > > > > > 
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(
> > > > > > > PrepareRe
> > > > > > > leaseMojo.java:246)
> > > > > > >
> > > > > > >
> > > > > > > thanks for taking to time to look into this.
> > > > > > > Trent
> > > > > > >
> > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > I thought I had used windows paths in the SCM 
> URL before 
> > > > > > > > without issues, but its worth trying:
> > > > > > > >
> > > > > > > > scm|svn|file:///d:/subversion...
> > > > > > > >
> > > > > > > > hth,
> > > > > > > > Brett
> > > > > > > >
> > > > > > > > On 11/8/05, Trent Rosenbaum 
> <tr...@gmail.com> wrote:
> > > > > > > > > This is the SCM URL for the project:
> > > > > > > > >
> > > > > > > > > <scm>
> > > > > > > > > 
> <developerConnection>scm:svn:file:///D:/subversion-1.2.0
> > > > > > > > > 
> _data/repositories/my_repo/bug-control-model/trunk</deve
> > > > > > > > > loperConnection>
> > > > > > > > > </scm>
> > > > > > > > >
> > > > > > > > > and the plugin is configured with the 
> following tagbase element:
> > > > > > > > >
> > > > > > > > > <plugin>
> > > > > > > > > <groupId>org.apache.maven.plugins</groupId>
> > > > > > > > > <artifactId>maven-release-plugin</artifactId>
> > > > > > > > > <version>2.0-beta-3</version> <configuration> 
> > > > > > > > > 
> <tagBase>scm:svn:file:///D:/subversion-1.2.0_data/reposi
> > > > > > > > > tories/my_repo/bug-control-model/tags</tagBase>
> > > > > > > > > </configuration>
> > > > > > > > > </plugin>
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 07/11/05, Brett Porter 
> <br...@gmail.com> wrote:
> > > > > > > > > > They both use the same library - so the 
> release plugin 
> > > > > > > > > > is for automating release related tasks, the scm 
> > > > > > > > > > plugin for development related tasks.
> > > > > > > > > >
> > > > > > > > > > Can you please repost the full SCM URL that 
> gave you 
> > > > > > > > > > this error - there is still something wrong with it.
> > > > > > > > > >
> > > > > > > > > > - Brett
> > > > > > > > > >
> > > > > > > > > > On 11/8/05, Trent Rosenbaum 
> <tr...@gmail.com> wrote:
> > > > > > > > > > > Thanks for the reply.
> > > > > > > > > > > When I started to use the plugin 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 manner.  I have again used these prefixes and I 
> still get a problem.
> > > > > > > > > > > Maven gave me the follow stacktrace 
> below.  I am using 2.0-beta-3 of the plugin.
> > > > > > > > > > >
> > > > > > > > > > > During my reading of the site I noticed that both 
> > > > > > > > > > > the scm and the release plugin are 
> similar.  Is it 
> > > > > > > > > > > right to think that the maven-scm 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 
> > > > > > > > > > > completing a checkout/checkin, copy etc 
> manually?  I just want to know the thoughts behind each plugin.
> > > > > > > > > > >
> > > > > > > > > > > ----- Maven output -----
> > > > > > > > > > >
> > > > > > > > > > > [ERROR] BUILD ERROR
> > > > > > > > > > > [INFO] 
> > > > > > > > > > > 
> ----------------------------------------------------
> > > > > > > > > > > ---
> > > > > > > > > > > [INFO] An error is occurred in the status process.
> > > > > > > > > > >
> > > > > > > > > > > Embedded error: Can't load the scm provider.
> > > > > > > > > > > The scm url is invalid.
> > > > > > > > > > >
> > > > > > > > > > > ----- stack trace ------
> > > > > > > > > > >
> > > > > > > > > > > Caused by: 
> org.apache.maven.scm.ScmException: Can't load the scm provider.
> > > > > > > > > > >         at 
> > > > > > > > > > > 
> org.apache.maven.plugins.release.helpers.ScmHelper.g
> > > > > > > > > > > etScmRepository(S
> > > > > > > > > > > cmHelper.java:104)
> > > > > > > > > > >         at 
> > > > > > > > > > > 
> org.apache.maven.plugins.release.helpers.ScmHelper.g
> > > > > > > > > > > etStatus(ScmHelpe
> > > > > > > > > > > r.java:169)
> > > > > > > > > > >         at 
> > > > > > > > > > > 
> org.apache.maven.plugins.release.PrepareReleaseMojo.
> > > > > > > > > > > checkForLocalModi
> > > > > > > > > > > fications(PrepareReleaseMojo.java:510)
> > > > > > > > > > >         ... 19 more
> > > > > > > > > > > Caused by: 
> > > > > > > > > > > 
> org.apache.maven.scm.repository.ScmRepositoryException: The 
> scm url i s invalid.
> > > > > > > > > > >         at 
> > > > > > > > > > > 
> org.apache.maven.scm.provider.svn.SvnScmProvider.mak
> > > > > > > > > > > eProviderScmRepos
> > > > > > > > > > > itory(SvnScmProvider.java:84)
> > > > > > > > > > >         at 
> > > > > > > > > > > 
> org.apache.maven.scm.manager.plexus.DefaultScmManage
> > > > > > > > > > > r.makeScmReposito
> > > > > > > > > > > ry(DefaultScmManager.java:126)
> > > > > > > > > > >         at 
> > > > > > > > > > > 
> org.apache.maven.plugins.release.helpers.ScmHelper.g
> > > > > > > > > > > etScmRepository(S
> > > > > > > > > > > cmHelper.java:82)
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On 07/11/05, Brett Porter 
> <br...@gmail.com> wrote:
> > > > > > > > > > > > Your SCM URL should start:
> > > > > > > > > > > >
> > > > > > > > > > > > scm:svn:file://...
> > > > > > > > > > > >
> > > > > > > > > > > > Maven has no knowledge of the SVN 
> protocols, just 
> > > > > > > > > > > > the scm type given in the second argument above.
> > > > > > > > > > > >
> > > > > > > > > > > > - Brett
> > > > > > > > > > >
> > > > > > > > > > > 
> ----------------------------------------------------
> > > > > > > > > > > ----------------- 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
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > 
> --------------------------------------------------------
> > > > > > > > > ------------- 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
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > 
> ------------------------------------------------------------
> > > > > > > --------- 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
> > > > > >
> > > > > >
> > > > >
> > > > > 
> ----------------------------------------------------------------
> > > > > ----- 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
> > > >
> > > >
> > >
> > > 
> --------------------------------------------------------------------
> > > - 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
> >
> >
> 
> ---------------------------------------------------------------------
> 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: [M2] - maven-release-plugin cannot load SCM provider

Posted by Trent Rosenbaum <tr...@gmail.com>.

I would be more than happy to help out with any documentation.
What is the process for improving documents?  Write something then attach it to
a jira issue to it can be picked up?

Trent

On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> No problem. Perhaps you could help reword the docs to make it clearer
> what tagBase does/is?
>
> - Brett
>
> On 11/9/05, Trent Rosenbaum <tr...@gmail.com> 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 the plugin I
> > should be putting the whole URL with the prexfix because the URL
> > specified int he developerConnection is being used to construct the
> > tag  URL.
> >
> > Trent
> >
> > On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > > Ah, sorry for the confusion.
> > >
> > > nulike the connections, tagBase is just the SVN URL (omit scm:svn) as
> > > it is an SVN specific property.
> > >
> > > - Brett
> > >
> > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > This is the feedback I got from running mvn release:prepare
> > > >
> > > > [INFO] [release:prepare]
> > > > [INFO] What tag name should be used?
> > > > 0.1.2
> > > > [INFO] Tagging release with the label 0.1.2.
> > > > Provider message:
> > > > The svn tag command failed.
> > > > Command output:
> > > > svn: Error resolving case of 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie
> > > > s\my_repo\bug-control-model\tags\0.1.2'
> > > >
> > > > [INFO] -------------------------------------------------------------------------
> > > > ---
> > > > [ERROR] BUILD ERROR
> > > > [INFO] -------------------------------------------------------------------------
> > > > ---
> > > > [INFO] An error is occurred in the tag process.
> > > >
> > > >
> > > > The URL for the tagBase is identical to the URL supplied within the
> > > > developerConnection element but "tags" replaces "trunk".
> > > >
> > > > Trent
> > > >
> > > >
> > > > On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > The bug is for the default of ../tags when used instead of a tagbase
> > > > > as you have, so it is different.
> > > > >
> > > > > Above that exception, there should have been output from the svn
> > > > > command. Does that reveal anything?
> > > > >
> > > > > - Brett
> > > > >
> > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > I did not have this pom.xml checked  into SVN and so it was trying to
> > > > > > work with the previous revision of my file and this did not have a SCM
> > > > > > URL defined.  I have been able to get the plugin to prompt me for
> > > > > > input regarding the tags, but I am falling over in the tagging process
> > > > > > with the following exception:
> > > > > >
> > > > > > Is this the same exception that has lead to the creation of the
> > > > > > following issue in jira?
> > > > > >
> > > > > > http://jira.codehaus.org/browse/MNG-883
> > > > > >
> > > > > >
> > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in
> > > > > > the tag process.
> > > > > >
> > > > > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred
> > > > > > in the tag process.
> > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
> > > > > > eReleaseMojo.java:1414)
> > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
> > > > > > leaseMojo.java:246)
> > > > > >
> > > > > >
> > > > > > thanks for taking to time to look into this.
> > > > > > Trent
> > > > > >
> > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > I thought I had used windows paths in the SCM URL before without
> > > > > > > issues, but its worth trying:
> > > > > > >
> > > > > > > scm|svn|file:///d:/subversion...
> > > > > > >
> > > > > > > hth,
> > > > > > > Brett
> > > > > > >
> > > > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > > > This is the SCM URL for the project:
> > > > > > > >
> > > > > > > > <scm>
> > > > > > > > <developerConnection>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk</developerConnection>
> > > > > > > > </scm>
> > > > > > > >
> > > > > > > > and the plugin is configured with the following tagbase element:
> > > > > > > >
> > > > > > > > <plugin>
> > > > > > > > <groupId>org.apache.maven.plugins</groupId>
> > > > > > > > <artifactId>maven-release-plugin</artifactId>
> > > > > > > > <version>2.0-beta-3</version>
> > > > > > > > <configuration>
> > > > > > > > <tagBase>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags</tagBase>
> > > > > > > > </configuration>
> > > > > > > > </plugin>
> > > > > > > >
> > > > > > > >
> > > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > > They both use the same library - so the release plugin is for
> > > > > > > > > automating release related tasks, the scm plugin for development
> > > > > > > > > related tasks.
> > > > > > > > >
> > > > > > > > > Can you please repost the full SCM URL that gave you this error -
> > > > > > > > > there is still something wrong with it.
> > > > > > > > >
> > > > > > > > > - Brett
> > > > > > > > >
> > > > > > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > > > > > Thanks for the reply.
> > > > > > > > > > When I started to use the plugin 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
> > > > > > > > > > manner.  I have again used these prefixes and I still get a problem.
> > > > > > > > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.
> > > > > > > > > >
> > > > > > > > > > During my reading of the site I noticed that both the scm and the
> > > > > > > > > > release plugin are similar.  Is it right to think that the maven-scm
> > > > > > > > > > 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 completing a checkout/checkin, copy etc manually?  I just want to
> > > > > > > > > > know the thoughts behind each plugin.
> > > > > > > > > >
> > > > > > > > > > ----- Maven output -----
> > > > > > > > > >
> > > > > > > > > > [ERROR] BUILD ERROR
> > > > > > > > > > [INFO] ----------------------------------------------------
> > > > > > > > > > ---
> > > > > > > > > > [INFO] An error is occurred in the status process.
> > > > > > > > > >
> > > > > > > > > > Embedded error: Can't load the scm provider.
> > > > > > > > > > The scm url is invalid.
> > > > > > > > > >
> > > > > > > > > > ----- stack trace ------
> > > > > > > > > >
> > > > > > > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> > > > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > > > > > cmHelper.java:104)
> > > > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > > > > > > > > r.java:169)
> > > > > > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > > > > > > > > fications(PrepareReleaseMojo.java:510)
> > > > > > > > > >         ... 19 more
> > > > > > > > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
> > > > > > > > > > s invalid.
> > > > > > > > > >         at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > > > > > > > > itory(SvnScmProvider.java:84)
> > > > > > > > > >         at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > > > > > > > > ry(DefaultScmManager.java:126)
> > > > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > > > > > cmHelper.java:82)
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > > > > Your SCM URL should start:
> > > > > > > > > > >
> > > > > > > > > > > scm:svn:file://...
> > > > > > > > > > >
> > > > > > > > > > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > > > > > > > > > in the second argument above.
> > > > > > > > > > >
> > > > > > > > > > > - Brett
> > > > > > > > > >
> > > > > > > > > > ---------------------------------------------------------------------
> > > > > > > > > > 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
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > > ---------------------------------------------------------------------
> > > > > > > > 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
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > 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
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > 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
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [M2] - maven-release-plugin cannot load SCM provider

Posted by Brett Porter <br...@gmail.com>.

No problem. Perhaps you could help reword the docs to make it clearer
what tagBase does/is?

- Brett

On 11/9/05, Trent Rosenbaum <tr...@gmail.com> 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 the plugin I
> should be putting the whole URL with the prexfix because the URL
> specified int he developerConnection is being used to construct the
> tag  URL.
>
> Trent
>
> On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > Ah, sorry for the confusion.
> >
> > nulike the connections, tagBase is just the SVN URL (omit scm:svn) as
> > it is an SVN specific property.
> >
> > - Brett
> >
> > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > This is the feedback I got from running mvn release:prepare
> > >
> > > [INFO] [release:prepare]
> > > [INFO] What tag name should be used?
> > > 0.1.2
> > > [INFO] Tagging release with the label 0.1.2.
> > > Provider message:
> > > The svn tag command failed.
> > > Command output:
> > > svn: Error resolving case of 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie
> > > s\my_repo\bug-control-model\tags\0.1.2'
> > >
> > > [INFO] -------------------------------------------------------------------------
> > > ---
> > > [ERROR] BUILD ERROR
> > > [INFO] -------------------------------------------------------------------------
> > > ---
> > > [INFO] An error is occurred in the tag process.
> > >
> > >
> > > The URL for the tagBase is identical to the URL supplied within the
> > > developerConnection element but "tags" replaces "trunk".
> > >
> > > Trent
> > >
> > >
> > > On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > The bug is for the default of ../tags when used instead of a tagbase
> > > > as you have, so it is different.
> > > >
> > > > Above that exception, there should have been output from the svn
> > > > command. Does that reveal anything?
> > > >
> > > > - Brett
> > > >
> > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > I did not have this pom.xml checked  into SVN and so it was trying to
> > > > > work with the previous revision of my file and this did not have a SCM
> > > > > URL defined.  I have been able to get the plugin to prompt me for
> > > > > input regarding the tags, but I am falling over in the tagging process
> > > > > with the following exception:
> > > > >
> > > > > Is this the same exception that has lead to the creation of the
> > > > > following issue in jira?
> > > > >
> > > > > http://jira.codehaus.org/browse/MNG-883
> > > > >
> > > > >
> > > > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in
> > > > > the tag process.
> > > > >
> > > > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred
> > > > > in the tag process.
> > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
> > > > > eReleaseMojo.java:1414)
> > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
> > > > > leaseMojo.java:246)
> > > > >
> > > > >
> > > > > thanks for taking to time to look into this.
> > > > > Trent
> > > > >
> > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > I thought I had used windows paths in the SCM URL before without
> > > > > > issues, but its worth trying:
> > > > > >
> > > > > > scm|svn|file:///d:/subversion...
> > > > > >
> > > > > > hth,
> > > > > > Brett
> > > > > >
> > > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > > This is the SCM URL for the project:
> > > > > > >
> > > > > > > <scm>
> > > > > > > <developerConnection>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk</developerConnection>
> > > > > > > </scm>
> > > > > > >
> > > > > > > and the plugin is configured with the following tagbase element:
> > > > > > >
> > > > > > > <plugin>
> > > > > > > <groupId>org.apache.maven.plugins</groupId>
> > > > > > > <artifactId>maven-release-plugin</artifactId>
> > > > > > > <version>2.0-beta-3</version>
> > > > > > > <configuration>
> > > > > > > <tagBase>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags</tagBase>
> > > > > > > </configuration>
> > > > > > > </plugin>
> > > > > > >
> > > > > > >
> > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > They both use the same library - so the release plugin is for
> > > > > > > > automating release related tasks, the scm plugin for development
> > > > > > > > related tasks.
> > > > > > > >
> > > > > > > > Can you please repost the full SCM URL that gave you this error -
> > > > > > > > there is still something wrong with it.
> > > > > > > >
> > > > > > > > - Brett
> > > > > > > >
> > > > > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > > > > Thanks for the reply.
> > > > > > > > > When I started to use the plugin 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
> > > > > > > > > manner.  I have again used these prefixes and I still get a problem.
> > > > > > > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.
> > > > > > > > >
> > > > > > > > > During my reading of the site I noticed that both the scm and the
> > > > > > > > > release plugin are similar.  Is it right to think that the maven-scm
> > > > > > > > > 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 completing a checkout/checkin, copy etc manually?  I just want to
> > > > > > > > > know the thoughts behind each plugin.
> > > > > > > > >
> > > > > > > > > ----- Maven output -----
> > > > > > > > >
> > > > > > > > > [ERROR] BUILD ERROR
> > > > > > > > > [INFO] ----------------------------------------------------
> > > > > > > > > ---
> > > > > > > > > [INFO] An error is occurred in the status process.
> > > > > > > > >
> > > > > > > > > Embedded error: Can't load the scm provider.
> > > > > > > > > The scm url is invalid.
> > > > > > > > >
> > > > > > > > > ----- stack trace ------
> > > > > > > > >
> > > > > > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> > > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > > > > cmHelper.java:104)
> > > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > > > > > > > r.java:169)
> > > > > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > > > > > > > fications(PrepareReleaseMojo.java:510)
> > > > > > > > >         ... 19 more
> > > > > > > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
> > > > > > > > > s invalid.
> > > > > > > > >         at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > > > > > > > itory(SvnScmProvider.java:84)
> > > > > > > > >         at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > > > > > > > ry(DefaultScmManager.java:126)
> > > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > > > > cmHelper.java:82)
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > > > Your SCM URL should start:
> > > > > > > > > >
> > > > > > > > > > scm:svn:file://...
> > > > > > > > > >
> > > > > > > > > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > > > > > > > > in the second argument above.
> > > > > > > > > >
> > > > > > > > > > - Brett
> > > > > > > > >
> > > > > > > > > ---------------------------------------------------------------------
> > > > > > > > > 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
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > ---------------------------------------------------------------------
> > > > > > > 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
> > > > > >
> > > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > 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
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
>
> ---------------------------------------------------------------------
> 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: [M2] - maven-release-plugin cannot load SCM provider

Posted by Trent Rosenbaum <tr...@gmail.com>.

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 int he developerConnection is being used to construct the
tag  URL.

Trent

On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> Ah, sorry for the confusion.
>
> nulike the connections, tagBase is just the SVN URL (omit scm:svn) as
> it is an SVN specific property.
>
> - Brett
>
> On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > This is the feedback I got from running mvn release:prepare
> >
> > [INFO] [release:prepare]
> > [INFO] What tag name should be used?
> > 0.1.2
> > [INFO] Tagging release with the label 0.1.2.
> > Provider message:
> > The svn tag command failed.
> > Command output:
> > svn: Error resolving case of 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie
> > s\my_repo\bug-control-model\tags\0.1.2'
> >
> > [INFO] -------------------------------------------------------------------------
> > ---
> > [ERROR] BUILD ERROR
> > [INFO] -------------------------------------------------------------------------
> > ---
> > [INFO] An error is occurred in the tag process.
> >
> >
> > The URL for the tagBase is identical to the URL supplied within the
> > developerConnection element but "tags" replaces "trunk".
> >
> > Trent
> >
> >
> > On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > > The bug is for the default of ../tags when used instead of a tagbase
> > > as you have, so it is different.
> > >
> > > Above that exception, there should have been output from the svn
> > > command. Does that reveal anything?
> > >
> > > - Brett
> > >
> > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > I did not have this pom.xml checked  into SVN and so it was trying to
> > > > work with the previous revision of my file and this did not have a SCM
> > > > URL defined.  I have been able to get the plugin to prompt me for
> > > > input regarding the tags, but I am falling over in the tagging process
> > > > with the following exception:
> > > >
> > > > Is this the same exception that has lead to the creation of the
> > > > following issue in jira?
> > > >
> > > > http://jira.codehaus.org/browse/MNG-883
> > > >
> > > >
> > > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in
> > > > the tag process.
> > > >
> > > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred
> > > > in the tag process.
> > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
> > > > eReleaseMojo.java:1414)
> > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
> > > > leaseMojo.java:246)
> > > >
> > > >
> > > > thanks for taking to time to look into this.
> > > > Trent
> > > >
> > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > I thought I had used windows paths in the SCM URL before without
> > > > > issues, but its worth trying:
> > > > >
> > > > > scm|svn|file:///d:/subversion...
> > > > >
> > > > > hth,
> > > > > Brett
> > > > >
> > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > This is the SCM URL for the project:
> > > > > >
> > > > > > <scm>
> > > > > > <developerConnection>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk</developerConnection>
> > > > > > </scm>
> > > > > >
> > > > > > and the plugin is configured with the following tagbase element:
> > > > > >
> > > > > > <plugin>
> > > > > > <groupId>org.apache.maven.plugins</groupId>
> > > > > > <artifactId>maven-release-plugin</artifactId>
> > > > > > <version>2.0-beta-3</version>
> > > > > > <configuration>
> > > > > > <tagBase>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags</tagBase>
> > > > > > </configuration>
> > > > > > </plugin>
> > > > > >
> > > > > >
> > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > They both use the same library - so the release plugin is for
> > > > > > > automating release related tasks, the scm plugin for development
> > > > > > > related tasks.
> > > > > > >
> > > > > > > Can you please repost the full SCM URL that gave you this error -
> > > > > > > there is still something wrong with it.
> > > > > > >
> > > > > > > - Brett
> > > > > > >
> > > > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > > > Thanks for the reply.
> > > > > > > > When I started to use the plugin 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
> > > > > > > > manner.  I have again used these prefixes and I still get a problem.
> > > > > > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.
> > > > > > > >
> > > > > > > > During my reading of the site I noticed that both the scm and the
> > > > > > > > release plugin are similar.  Is it right to think that the maven-scm
> > > > > > > > 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 completing a checkout/checkin, copy etc manually?  I just want to
> > > > > > > > know the thoughts behind each plugin.
> > > > > > > >
> > > > > > > > ----- Maven output -----
> > > > > > > >
> > > > > > > > [ERROR] BUILD ERROR
> > > > > > > > [INFO] ----------------------------------------------------
> > > > > > > > ---
> > > > > > > > [INFO] An error is occurred in the status process.
> > > > > > > >
> > > > > > > > Embedded error: Can't load the scm provider.
> > > > > > > > The scm url is invalid.
> > > > > > > >
> > > > > > > > ----- stack trace ------
> > > > > > > >
> > > > > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > > > cmHelper.java:104)
> > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > > > > > > r.java:169)
> > > > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > > > > > > fications(PrepareReleaseMojo.java:510)
> > > > > > > >         ... 19 more
> > > > > > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
> > > > > > > > s invalid.
> > > > > > > >         at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > > > > > > itory(SvnScmProvider.java:84)
> > > > > > > >         at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > > > > > > ry(DefaultScmManager.java:126)
> > > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > > > cmHelper.java:82)
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > > Your SCM URL should start:
> > > > > > > > >
> > > > > > > > > scm:svn:file://...
> > > > > > > > >
> > > > > > > > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > > > > > > > in the second argument above.
> > > > > > > > >
> > > > > > > > > - Brett
> > > > > > > >
> > > > > > > > ---------------------------------------------------------------------
> > > > > > > > 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
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > 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
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > 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
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [M2] - maven-release-plugin cannot load SCM provider

Posted by Brett Porter <br...@gmail.com>.

Ah, sorry for the confusion.

nulike the connections, tagBase is just the SVN URL (omit scm:svn) as
it is an SVN specific property.

- Brett

On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> This is the feedback I got from running mvn release:prepare
>
> [INFO] [release:prepare]
> [INFO] What tag name should be used?
> 0.1.2
> [INFO] Tagging release with the label 0.1.2.
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Error resolving case of 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie
> s\my_repo\bug-control-model\tags\0.1.2'
>
> [INFO] -------------------------------------------------------------------------
> ---
> [ERROR] BUILD ERROR
> [INFO] -------------------------------------------------------------------------
> ---
> [INFO] An error is occurred in the tag process.
>
>
> The URL for the tagBase is identical to the URL supplied within the
> developerConnection element but "tags" replaces "trunk".
>
> Trent
>
>
> On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> > The bug is for the default of ../tags when used instead of a tagbase
> > as you have, so it is different.
> >
> > Above that exception, there should have been output from the svn
> > command. Does that reveal anything?
> >
> > - Brett
> >
> > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > I did not have this pom.xml checked  into SVN and so it was trying to
> > > work with the previous revision of my file and this did not have a SCM
> > > URL defined.  I have been able to get the plugin to prompt me for
> > > input regarding the tags, but I am falling over in the tagging process
> > > with the following exception:
> > >
> > > Is this the same exception that has lead to the creation of the
> > > following issue in jira?
> > >
> > > http://jira.codehaus.org/browse/MNG-883
> > >
> > >
> > > org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in
> > > the tag process.
> > >
> > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred
> > > in the tag process.
> > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
> > > eReleaseMojo.java:1414)
> > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
> > > leaseMojo.java:246)
> > >
> > >
> > > thanks for taking to time to look into this.
> > > Trent
> > >
> > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > I thought I had used windows paths in the SCM URL before without
> > > > issues, but its worth trying:
> > > >
> > > > scm|svn|file:///d:/subversion...
> > > >
> > > > hth,
> > > > Brett
> > > >
> > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > This is the SCM URL for the project:
> > > > >
> > > > > <scm>
> > > > > <developerConnection>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk</developerConnection>
> > > > > </scm>
> > > > >
> > > > > and the plugin is configured with the following tagbase element:
> > > > >
> > > > > <plugin>
> > > > > <groupId>org.apache.maven.plugins</groupId>
> > > > > <artifactId>maven-release-plugin</artifactId>
> > > > > <version>2.0-beta-3</version>
> > > > > <configuration>
> > > > > <tagBase>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags</tagBase>
> > > > > </configuration>
> > > > > </plugin>
> > > > >
> > > > >
> > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > They both use the same library - so the release plugin is for
> > > > > > automating release related tasks, the scm plugin for development
> > > > > > related tasks.
> > > > > >
> > > > > > Can you please repost the full SCM URL that gave you this error -
> > > > > > there is still something wrong with it.
> > > > > >
> > > > > > - Brett
> > > > > >
> > > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > > Thanks for the reply.
> > > > > > > When I started to use the plugin 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
> > > > > > > manner.  I have again used these prefixes and I still get a problem.
> > > > > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.
> > > > > > >
> > > > > > > During my reading of the site I noticed that both the scm and the
> > > > > > > release plugin are similar.  Is it right to think that the maven-scm
> > > > > > > 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 completing a checkout/checkin, copy etc manually?  I just want to
> > > > > > > know the thoughts behind each plugin.
> > > > > > >
> > > > > > > ----- Maven output -----
> > > > > > >
> > > > > > > [ERROR] BUILD ERROR
> > > > > > > [INFO] ----------------------------------------------------
> > > > > > > ---
> > > > > > > [INFO] An error is occurred in the status process.
> > > > > > >
> > > > > > > Embedded error: Can't load the scm provider.
> > > > > > > The scm url is invalid.
> > > > > > >
> > > > > > > ----- stack trace ------
> > > > > > >
> > > > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > > cmHelper.java:104)
> > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > > > > > r.java:169)
> > > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > > > > > fications(PrepareReleaseMojo.java:510)
> > > > > > >         ... 19 more
> > > > > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
> > > > > > > s invalid.
> > > > > > >         at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > > > > > itory(SvnScmProvider.java:84)
> > > > > > >         at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > > > > > ry(DefaultScmManager.java:126)
> > > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > > cmHelper.java:82)
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > > Your SCM URL should start:
> > > > > > > >
> > > > > > > > scm:svn:file://...
> > > > > > > >
> > > > > > > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > > > > > > in the second argument above.
> > > > > > > >
> > > > > > > > - Brett
> > > > > > >
> > > > > > > ---------------------------------------------------------------------
> > > > > > > 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
> > > > > >
> > > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > 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
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
>
> ---------------------------------------------------------------------
> 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: [M2] - maven-release-plugin cannot load SCM provider

Posted by Trent Rosenbaum <tr...@gmail.com>.

This is the feedback I got from running mvn release:prepare

[INFO] [release:prepare]
[INFO] What tag name should be used?
0.1.2
[INFO] Tagging release with the label 0.1.2.
Provider message:
The svn tag command failed.
Command output:
svn: Error resolving case of 'scm:svn:file:\d:\subversion-1.2.0_data\repositorie
s\my_repo\bug-control-model\tags\0.1.2'

[INFO] -------------------------------------------------------------------------
---
[ERROR] BUILD ERROR
[INFO] -------------------------------------------------------------------------
---
[INFO] An error is occurred in the tag process.


The URL for the tagBase is identical to the URL supplied within the
developerConnection element but "tags" replaces "trunk".

Trent


On 08/11/05, Brett Porter <br...@gmail.com> wrote:
> The bug is for the default of ../tags when used instead of a tagbase
> as you have, so it is different.
>
> Above that exception, there should have been output from the svn
> command. Does that reveal anything?
>
> - Brett
>
> On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > I did not have this pom.xml checked  into SVN and so it was trying to
> > work with the previous revision of my file and this did not have a SCM
> > URL defined.  I have been able to get the plugin to prompt me for
> > input regarding the tags, but I am falling over in the tagging process
> > with the following exception:
> >
> > Is this the same exception that has lead to the creation of the
> > following issue in jira?
> >
> > http://jira.codehaus.org/browse/MNG-883
> >
> >
> > org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in
> > the tag process.
> >
> > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred
> > in the tag process.
> >         at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
> > eReleaseMojo.java:1414)
> >         at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
> > leaseMojo.java:246)
> >
> >
> > thanks for taking to time to look into this.
> > Trent
> >
> > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > I thought I had used windows paths in the SCM URL before without
> > > issues, but its worth trying:
> > >
> > > scm|svn|file:///d:/subversion...
> > >
> > > hth,
> > > Brett
> > >
> > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > This is the SCM URL for the project:
> > > >
> > > > <scm>
> > > > <developerConnection>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk</developerConnection>
> > > > </scm>
> > > >
> > > > and the plugin is configured with the following tagbase element:
> > > >
> > > > <plugin>
> > > > <groupId>org.apache.maven.plugins</groupId>
> > > > <artifactId>maven-release-plugin</artifactId>
> > > > <version>2.0-beta-3</version>
> > > > <configuration>
> > > > <tagBase>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags</tagBase>
> > > > </configuration>
> > > > </plugin>
> > > >
> > > >
> > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > They both use the same library - so the release plugin is for
> > > > > automating release related tasks, the scm plugin for development
> > > > > related tasks.
> > > > >
> > > > > Can you please repost the full SCM URL that gave you this error -
> > > > > there is still something wrong with it.
> > > > >
> > > > > - Brett
> > > > >
> > > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > > Thanks for the reply.
> > > > > > When I started to use the plugin 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
> > > > > > manner.  I have again used these prefixes and I still get a problem.
> > > > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.
> > > > > >
> > > > > > During my reading of the site I noticed that both the scm and the
> > > > > > release plugin are similar.  Is it right to think that the maven-scm
> > > > > > 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 completing a checkout/checkin, copy etc manually?  I just want to
> > > > > > know the thoughts behind each plugin.
> > > > > >
> > > > > > ----- Maven output -----
> > > > > >
> > > > > > [ERROR] BUILD ERROR
> > > > > > [INFO] ----------------------------------------------------
> > > > > > ---
> > > > > > [INFO] An error is occurred in the status process.
> > > > > >
> > > > > > Embedded error: Can't load the scm provider.
> > > > > > The scm url is invalid.
> > > > > >
> > > > > > ----- stack trace ------
> > > > > >
> > > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > cmHelper.java:104)
> > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > > > > r.java:169)
> > > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > > > > fications(PrepareReleaseMojo.java:510)
> > > > > >         ... 19 more
> > > > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
> > > > > > s invalid.
> > > > > >         at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > > > > itory(SvnScmProvider.java:84)
> > > > > >         at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > > > > ry(DefaultScmManager.java:126)
> > > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > > cmHelper.java:82)
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > > Your SCM URL should start:
> > > > > > >
> > > > > > > scm:svn:file://...
> > > > > > >
> > > > > > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > > > > > in the second argument above.
> > > > > > >
> > > > > > > - Brett
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > 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
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > 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
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [M2] - maven-release-plugin cannot load SCM provider

Posted by Brett Porter <br...@gmail.com>.

The bug is for the default of ../tags when used instead of a tagbase
as you have, so it is different.

Above that exception, there should have been output from the svn
command. Does that reveal anything?

- Brett

On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> I did not have this pom.xml checked  into SVN and so it was trying to
> work with the previous revision of my file and this did not have a SCM
> URL defined.  I have been able to get the plugin to prompt me for
> input regarding the tags, but I am falling over in the tagging process
> with the following exception:
>
> Is this the same exception that has lead to the creation of the
> following issue in jira?
>
> http://jira.codehaus.org/browse/MNG-883
>
>
> org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in
> the tag process.
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred
> in the tag process.
>         at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
> eReleaseMojo.java:1414)
>         at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
> leaseMojo.java:246)
>
>
> thanks for taking to time to look into this.
> Trent
>
> On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > I thought I had used windows paths in the SCM URL before without
> > issues, but its worth trying:
> >
> > scm|svn|file:///d:/subversion...
> >
> > hth,
> > Brett
> >
> > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > This is the SCM URL for the project:
> > >
> > > <scm>
> > > <developerConnection>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk</developerConnection>
> > > </scm>
> > >
> > > and the plugin is configured with the following tagbase element:
> > >
> > > <plugin>
> > > <groupId>org.apache.maven.plugins</groupId>
> > > <artifactId>maven-release-plugin</artifactId>
> > > <version>2.0-beta-3</version>
> > > <configuration>
> > > <tagBase>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags</tagBase>
> > > </configuration>
> > > </plugin>
> > >
> > >
> > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > They both use the same library - so the release plugin is for
> > > > automating release related tasks, the scm plugin for development
> > > > related tasks.
> > > >
> > > > Can you please repost the full SCM URL that gave you this error -
> > > > there is still something wrong with it.
> > > >
> > > > - Brett
> > > >
> > > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > > Thanks for the reply.
> > > > > When I started to use the plugin 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
> > > > > manner.  I have again used these prefixes and I still get a problem.
> > > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.
> > > > >
> > > > > During my reading of the site I noticed that both the scm and the
> > > > > release plugin are similar.  Is it right to think that the maven-scm
> > > > > 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 completing a checkout/checkin, copy etc manually?  I just want to
> > > > > know the thoughts behind each plugin.
> > > > >
> > > > > ----- Maven output -----
> > > > >
> > > > > [ERROR] BUILD ERROR
> > > > > [INFO] ----------------------------------------------------
> > > > > ---
> > > > > [INFO] An error is occurred in the status process.
> > > > >
> > > > > Embedded error: Can't load the scm provider.
> > > > > The scm url is invalid.
> > > > >
> > > > > ----- stack trace ------
> > > > >
> > > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > cmHelper.java:104)
> > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > > > r.java:169)
> > > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > > > fications(PrepareReleaseMojo.java:510)
> > > > >         ... 19 more
> > > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
> > > > > s invalid.
> > > > >         at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > > > itory(SvnScmProvider.java:84)
> > > > >         at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > > > ry(DefaultScmManager.java:126)
> > > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > > cmHelper.java:82)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > > Your SCM URL should start:
> > > > > >
> > > > > > scm:svn:file://...
> > > > > >
> > > > > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > > > > in the second argument above.
> > > > > >
> > > > > > - Brett
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > 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
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
>
> ---------------------------------------------------------------------
> 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: [M2] - maven-release-plugin cannot load SCM provider

Posted by Trent Rosenbaum <tr...@gmail.com>.

I did not have this pom.xml checked  into SVN and so it was trying to
work with the previous revision of my file and this did not have a SCM
URL defined.  I have been able to get the plugin to prompt me for
input regarding the tags, but I am falling over in the tagging process
with the following exception:

Is this the same exception that has lead to the creation of the
following issue in jira?

http://jira.codehaus.org/browse/MNG-883


org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in
the tag process.

Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred
in the tag process.
        at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
eReleaseMojo.java:1414)
        at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
leaseMojo.java:246)


thanks for taking to time to look into this.
Trent

On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> I thought I had used windows paths in the SCM URL before without
> issues, but its worth trying:
>
> scm|svn|file:///d:/subversion...
>
> hth,
> Brett
>
> On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > This is the SCM URL for the project:
> >
> > <scm>
> > <developerConnection>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk</developerConnection>
> > </scm>
> >
> > and the plugin is configured with the following tagbase element:
> >
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-release-plugin</artifactId>
> > <version>2.0-beta-3</version>
> > <configuration>
> > <tagBase>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags</tagBase>
> > </configuration>
> > </plugin>
> >
> >
> > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > They both use the same library - so the release plugin is for
> > > automating release related tasks, the scm plugin for development
> > > related tasks.
> > >
> > > Can you please repost the full SCM URL that gave you this error -
> > > there is still something wrong with it.
> > >
> > > - Brett
> > >
> > > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > > Thanks for the reply.
> > > > When I started to use the plugin 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
> > > > manner.  I have again used these prefixes and I still get a problem.
> > > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.
> > > >
> > > > During my reading of the site I noticed that both the scm and the
> > > > release plugin are similar.  Is it right to think that the maven-scm
> > > > 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 completing a checkout/checkin, copy etc manually?  I just want to
> > > > know the thoughts behind each plugin.
> > > >
> > > > ----- Maven output -----
> > > >
> > > > [ERROR] BUILD ERROR
> > > > [INFO] ----------------------------------------------------
> > > > ---
> > > > [INFO] An error is occurred in the status process.
> > > >
> > > > Embedded error: Can't load the scm provider.
> > > > The scm url is invalid.
> > > >
> > > > ----- stack trace ------
> > > >
> > > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > cmHelper.java:104)
> > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > > r.java:169)
> > > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > > fications(PrepareReleaseMojo.java:510)
> > > >         ... 19 more
> > > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
> > > > s invalid.
> > > >         at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > > itory(SvnScmProvider.java:84)
> > > >         at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > > ry(DefaultScmManager.java:126)
> > > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > > cmHelper.java:82)
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > > Your SCM URL should start:
> > > > >
> > > > > scm:svn:file://...
> > > > >
> > > > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > > > in the second argument above.
> > > > >
> > > > > - Brett
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > 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
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [M2] - maven-release-plugin cannot load SCM provider

Posted by Brett Porter <br...@gmail.com>.

I thought I had used windows paths in the SCM URL before without
issues, but its worth trying:

scm|svn|file:///d:/subversion...

hth,
Brett

On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> This is the SCM URL for the project:
>
> <scm>
> <developerConnection>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk</developerConnection>
> </scm>
>
> and the plugin is configured with the following tagbase element:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.0-beta-3</version>
> <configuration>
> <tagBase>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags</tagBase>
> </configuration>
> </plugin>
>
>
> On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > They both use the same library - so the release plugin is for
> > automating release related tasks, the scm plugin for development
> > related tasks.
> >
> > Can you please repost the full SCM URL that gave you this error -
> > there is still something wrong with it.
> >
> > - Brett
> >
> > On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > > Thanks for the reply.
> > > When I started to use the plugin 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
> > > manner.  I have again used these prefixes and I still get a problem.
> > > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.
> > >
> > > During my reading of the site I noticed that both the scm and the
> > > release plugin are similar.  Is it right to think that the maven-scm
> > > 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 completing a checkout/checkin, copy etc manually?  I just want to
> > > know the thoughts behind each plugin.
> > >
> > > ----- Maven output -----
> > >
> > > [ERROR] BUILD ERROR
> > > [INFO] ----------------------------------------------------
> > > ---
> > > [INFO] An error is occurred in the status process.
> > >
> > > Embedded error: Can't load the scm provider.
> > > The scm url is invalid.
> > >
> > > ----- stack trace ------
> > >
> > > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > cmHelper.java:104)
> > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > > r.java:169)
> > >         at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > > fications(PrepareReleaseMojo.java:510)
> > >         ... 19 more
> > > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
> > > s invalid.
> > >         at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > > itory(SvnScmProvider.java:84)
> > >         at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > > ry(DefaultScmManager.java:126)
> > >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > > cmHelper.java:82)
> > >
> > >
> > >
> > >
> > >
> > > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > > Your SCM URL should start:
> > > >
> > > > scm:svn:file://...
> > > >
> > > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > > in the second argument above.
> > > >
> > > > - Brett
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
>
> ---------------------------------------------------------------------
> 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: [M2] - maven-release-plugin cannot load SCM provider

Posted by Trent Rosenbaum <tr...@gmail.com>.

This is the SCM URL for the project:

<scm>
<developerConnection>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk</developerConnection>
</scm>

and the plugin is configured with the following tagbase element:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-3</version>
<configuration>
<tagBase>scm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags</tagBase>
</configuration>
</plugin>


On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> They both use the same library - so the release plugin is for
> automating release related tasks, the scm plugin for development
> related tasks.
>
> Can you please repost the full SCM URL that gave you this error -
> there is still something wrong with it.
>
> - Brett
>
> On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> > Thanks for the reply.
> > When I started to use the plugin 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
> > manner.  I have again used these prefixes and I still get a problem.
> > Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.
> >
> > During my reading of the site I noticed that both the scm and the
> > release plugin are similar.  Is it right to think that the maven-scm
> > 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 completing a checkout/checkin, copy etc manually?  I just want to
> > know the thoughts behind each plugin.
> >
> > ----- Maven output -----
> >
> > [ERROR] BUILD ERROR
> > [INFO] ----------------------------------------------------
> > ---
> > [INFO] An error is occurred in the status process.
> >
> > Embedded error: Can't load the scm provider.
> > The scm url is invalid.
> >
> > ----- stack trace ------
> >
> > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
> >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > cmHelper.java:104)
> >         at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> > r.java:169)
> >         at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> > fications(PrepareReleaseMojo.java:510)
> >         ... 19 more
> > Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
> > s invalid.
> >         at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> > itory(SvnScmProvider.java:84)
> >         at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> > ry(DefaultScmManager.java:126)
> >         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> > cmHelper.java:82)
> >
> >
> >
> >
> >
> > On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > > Your SCM URL should start:
> > >
> > > scm:svn:file://...
> > >
> > > Maven has no knowledge of the SVN protocols, just the scm type given
> > > in the second argument above.
> > >
> > > - Brett
> >
> > ---------------------------------------------------------------------
> > 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
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [M2] - maven-release-plugin cannot load SCM provider

Posted by Brett Porter <br...@gmail.com>.

They both use the same library - so the release plugin is for
automating release related tasks, the scm plugin for development
related tasks.

Can you please repost the full SCM URL that gave you this error -
there is still something wrong with it.

- Brett

On 11/8/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> Thanks for the reply.
> When I started to use the plugin 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
> manner.  I have again used these prefixes and I still get a problem.
> Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.
>
> During my reading of the site I noticed that both the scm and the
> release plugin are similar.  Is it right to think that the maven-scm
> 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 completing a checkout/checkin, copy etc manually?  I just want to
> know the thoughts behind each plugin.
>
> ----- Maven output -----
>
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------------------
> ---
> [INFO] An error is occurred in the status process.
>
> Embedded error: Can't load the scm provider.
> The scm url is invalid.
>
> ----- stack trace ------
>
> Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
>         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> cmHelper.java:104)
>         at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
> r.java:169)
>         at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
> fications(PrepareReleaseMojo.java:510)
>         ... 19 more
> Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
> s invalid.
>         at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
> itory(SvnScmProvider.java:84)
>         at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
> ry(DefaultScmManager.java:126)
>         at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
> cmHelper.java:82)
>
>
>
>
>
> On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> > Your SCM URL should start:
> >
> > scm:svn:file://...
> >
> > Maven has no knowledge of the SVN protocols, just the scm type given
> > in the second argument above.
> >
> > - Brett
>
> ---------------------------------------------------------------------
> 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: [M2] - maven-release-plugin cannot load SCM provider

Posted by Trent Rosenbaum <tr...@gmail.com>.

Thanks for the reply.
When I started to use the plugin 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
manner.  I have again used these prefixes and I still get a problem.
Maven gave me the follow stacktrace below.  I am using 2.0-beta-3 of the plugin.

During my reading of the site I noticed that both the scm and the
release plugin are similar.  Is it right to think that the maven-scm
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 completing a checkout/checkin, copy etc manually?  I just want to
know the thoughts behind each plugin.

----- Maven output -----

[ERROR] BUILD ERROR
[INFO] ----------------------------------------------------
---
[INFO] An error is occurred in the status process.

Embedded error: Can't load the scm provider.
The scm url is invalid.

----- stack trace ------

Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider.
        at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
cmHelper.java:104)
        at org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelpe
r.java:169)
        at org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModi
fications(PrepareReleaseMojo.java:510)
        ... 19 more
Caused by: org.apache.maven.scm.repository.ScmRepositoryException: The scm url i
s invalid.
        at org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepos
itory(SvnScmProvider.java:84)
        at org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmReposito
ry(DefaultScmManager.java:126)
        at org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(S
cmHelper.java:82)

On 07/11/05, Brett Porter <br...@gmail.com> wrote:
> Your SCM URL should start:
>
> scm:svn:file://...
>
> Maven has no knowledge of the SVN protocols, just the scm type given
> in the second argument above.
>
> - Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [M2] - maven-release-plugin cannot load SCM provider

Posted by Brett Porter <br...@gmail.com>.

Your SCM URL should start:

scm:svn:file://...

Maven has no knowledge of the SVN protocols, just the scm type given
in the second argument above.

- Brett

On 11/7/05, Trent Rosenbaum <tr...@gmail.com> wrote:
> 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 source code and so I am sure the SVN setup is fine.
>
> I get the following error back from maven:
>
> [INFO] An error is occurred in the status process.
>
> Embedded error: Can't load the scm provider.
> The scm url is invalid.
>
> I have looked at the mini-guide and have the following setup in my pom.xml:
>
> <scm>
> <developerConnection>
> file:///D:/subversion-1.2.0_data/repositories/my_repo/<my project>/trunk
> </developerConnection>
> </scm>
>
> and the plugin is setup with the following values
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <configuration>
> <tagBase>
> file:///D:/subversion-1.2.0_data/repositories/my_repo/<my project>/tags
> </tagBase>
> </configuration>
> </plugin>
>
> I then run the following command:
>
> mvn release:prepare
>
> Within the mini-guide the example shows the use of a SVN URL over SSH,
> I went back and double checked the valid URLs for SVN, (using the
> Subversion docs) and the above developerConnection String looks fine
> to me.
>
> I have been searching the mailing list and different sites for any
> info.  How do I define the SCM provider to be used by the plugin?  The
> maven-release-plugin docs show a scmManager element for the
> configuration but I am not sure how to use it.  If the
> developerConnection URL contained the svn:// or svn+ssh:// then I
> could understand that the plugin would be able to locate and load the
> provider.
>
> Does anyone have any thoughts on this problem?
> Many thanks
>
> Trent
>
> ---------------------------------------------------------------------
> 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