SVN 1.7 pluging problem

[Stanislav Zaluzhsky]

Hello,

The plugin version 1.7 throws:


at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:127)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:209)
... 23 more
Caused by: org.apache.maven.plugin.PluginContainerException: A
required class wa
s missing while executing com.google.code.maven-svn-revision-number-
plugin:maven
-svn-revision-number-plugin:1.7:revision: org/tmatesoft/sqljet/core/
SqlJetExcept
ion
-----------------------------------------------------
realm = plugin>com.google.code.maven-svn-revision-number-
plugin:maven-svn-rev
ision-number-plugin:1.7
strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
urls[0] = file:/C:/Users/admin/.m2/repository/com/google/code/maven-
svn-revision
-number-plugin/maven-svn-revision-number-plugin/1.7/maven-svn-revision-
number-pl
ugin-1.7.jar
urls[1] = file:/C:/Users/admin/.m2/repository/org/tmatesoft/svnkit/
svnkit/1.7.0-
SNAPSHOT/svnkit-1.7.0-SNAPSHOT.jar
urls[2] = file:/C:/Users/admin/.m2/repository/backport-util-concurrent/
backport-
util-concurrent/3.1/backport-util-concurrent-3.1.jar
urls[3] = file:/C:/Users/admin/.m2/repository/org/codehaus/plexus/
plexus-interpo
lation/1.11/plexus-interpolation-1.11.jar
urls[4] = file:/C:/Users/admin/.m2/repository/org/codehaus/plexus/
plexus-utils/1
.5.15/plexus-utils-1.5.15.jar
urls[5] = file:/C:/Users/admin/.m2/repository/junit/junit/3.8.1/
junit-3.8.1.jar
Number of foreign imports: 1
import: Entry[import from realm ClassRealm[maven.api, parent: null]]

Note that plugin maven-svn-revision-number-plugin has been installed
manually to local repository. But I'm not sure that it can cause such
problem.

Pls suggest me what to do.

[Oleg Estekhin]

Hi

The following line from your log explains what is wrong:
===
A required class was missing while executing com.google.code.maven-svn-
revision-number-plugin:maven-svn-revision-number-plugin:1.7:revision:
org/tmatesoft/sqljet/core/SqlJetException
===

It means that you did not configure your pom with additional
repositories with TMateSoft artifacts.
If you really want to install artifacts manually into your local
repository you can try to get the required artifacts from the
http://maven.tmatesoft.com/content/repositories/releases/ and
http://maven.tmatesoft.com/content/repositories/snapshots/ but this is
really non-maven way of doing things and it will cause you a lot of
problems in the long run.

The better way would be to follow the instructions in the
http://code.google.com/p/maven-svn-revision-number-plugin/wiki/svn7
and let the maven handle all the required dependencies, as it was
meant to be.


On 29 янв, 23:51, Stanislav Zaluzhsky <stanislav.zaluzh...@gmail.com>
wrote:

[Oleg Estekhin]

I have re-read your initial message more carefully - plugin version
1.7 has nothing to do with svn 1.7, it just unfortunate version
numbering coincidence, and it is funny that it was me who got caught
by it =)

In that case you can simply follow the usual plugin usage from the
http://maven-svn-revision-number-plugin.googlecode.com/svn/site/usage.html
and let the maven handle all required dependencies automatically. I
would really suggest you against installing plugins in your local
repository manually.

On 30 янв, 10:33, Oleg Estekhin <oleg.estek...@gmail.com> wrote:
> Hi
>
> The following line from your log explains what is wrong:
> ===
> A required class was missing while executing com.google.code.maven-svn-
> revision-number-plugin:maven-svn-revision-number-plugin:1.7:revision:
> org/tmatesoft/sqljet/core/SqlJetException
> ===
>
> It means that you did not configure your pom with additional
> repositories with TMateSoft artifacts.
> If you really want to install artifacts manually into your local

> repository you can try to get the required artifacts from thehttp://maven.tmatesoft.com/content/repositories/releases/andhttp://maven.tmatesoft.com/content/repositories/snapshots/but this is

> really non-maven way of doing things and it will cause you a lot of
> problems in the long run.
>

> The better way would be to follow the instructions in thehttp://code.google.com/p/maven-svn-revision-number-plugin/wiki/svn7

[Stanislav Zaluzhsky]

Hi,

 I see that plugin version 1.7 could mix up the things, but my original problem was that after upgrade of local repository version to 1.7.0 maven-svn-revision-number-plugin starts returning unversioned value with workingCopyDirectory.revision variable.
 That's why I was trying to follow http://code.google.com/p/maven-svn-revision-number-plugin/wiki/svn7 but with no successes, after that trying to install dependency manually and again....you can see the exception in the first mail from me.

So pls suggest me the best way.

wbr,
Stanislav,

2012/1/30 Oleg Estekhin <oleg.e...@gmail.com>

[Stanislav Zaluzhsky]

Hi,

 I see that plugin version 1.7 could mix up the things, but my original problem was that after upgrade of local repository version to 1.7.0 maven-svn-revision-number-plugin starts returning unversioned value with workingCopyDirectory.revision variable.

 That's why I was trying to follow http://code.google.com/p/maven-svn-revision-number-plugin/wiki/svn7 but with no success, after that manual dependency installation brings me an exception.

So pls suggest me the best way on how to deal with SVN 1.7

wbr,

2012/1/30 Oleg Estekhin <oleg.e...@gmail.com>