Maven setup

25 views
Skip to first unread message

2sense

unread,
Jun 25, 2009, 5:27:23 AM6/25/09
to Salve
Hi,

I am having problems getting maven to work with the 1.1 salve plugin.

I have this in my pom

<build>
<plugins>
<plugin>
<groupId>salve</groupId>
<version>${salve.version}</version>
<artifactId>maven-salve-plugin</artifactId>
<configuration>
<verbose>true</verbose>
</configuration>
<executions>
<execution>
<goals>
<goal>instrument</goal>
<goal>instrument-test</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>

<repositories>
<repository>
<id>salve.repository</id>
<name>Salve Maven2 Repository</name>
<url>http://salve.googlecode.com/svn/maven2</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>


mvn install command is failing with this error:

[INFO]
------------------------------------------------------------------------
Downloading: http://repo1.maven.org/maven2/salve/maven-salve-plugin/1.1/maven-salve-plugin-1.1.jar
[INFO] Unable to find resource 'salve:maven-salve-plugin:maven-plugin:
1.1' in repository central (http://repo1.maven.org/maven2)
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] A required plugin was not found: Plugin could not be found -
check that the goal name is correct: Unable to download the artifact
from any repository

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=salve -DartifactId=maven-salve-
plugin -Dversion=1.1 -Dpackaging=maven-plugin -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=salve -DartifactId=maven-salve-
plugin -Dversion=1.1 -Dpackaging=maven-plugin -Dfile=/path/to/file -
Durl=[url] -DrepositoryId=[id]


salve:maven-salve-plugin:maven-plugin:1.1

from the specified remote repositories:
central (http://repo1.maven.org/maven2)


salve:maven-salve-plugin:maven-plugin:1.1

from the specified remote repositories:
central (http://repo1.maven.org/maven2)

Igor Vaynberg

unread,
Jun 25, 2009, 11:46:29 AM6/25/09
to salve...@googlegroups.com
try adding

<pluginRepositories>
<pluginRepository>
<id>salve.repository</id>
<name>Salve Maven2 Repository</name>
<url>http://salve.googlecode.com/svn/maven2</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>

-igor

jd

unread,
Jun 25, 2009, 11:41:09 PM6/25/09
to Salve
Cool, thanks. Just confirming that this is not needed in 1.1?


<dependency>
<groupId>salve</groupId>
<artifactId>salve-depend</artifactId>
<version>${salve.version}</version>
</dependency>
<dependency>
<groupId>salve</groupId>
<artifactId>salve-depend-inst</artifactId>
<version>${salve.version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>salve</groupId>
<artifactId>salve-depend-guice</artifactId>
<version>${salve.version}</version>
</dependency>

Igor Vaynberg

unread,
Jun 25, 2009, 11:42:27 PM6/25/09
to salve...@googlegroups.com
wdym its not needed? it is needed if you want to use @dependency

-igor

John Patterson

unread,
Jun 25, 2009, 11:50:26 PM6/25/09
to salve...@googlegroups.com
OK, I thought that perhaps through some maven magic the plugin might
be able to instrument the code without the project dependencies. The
documentation says that the <dependency> part is only required in
"legacy" versions. Perhaps this could be updated.

http://code.google.com/p/salve/wiki/ConfiguringInstrumentation

Igor Vaynberg

unread,
Jun 26, 2009, 12:01:02 AM6/26/09
to salve...@googlegroups.com
i believe the "differences" were referring to the plugin configuration
only. anyways, i updated the page. thanks.

-igor

John Patterson

unread,
Jun 26, 2009, 1:16:47 AM6/26/09
to salve...@googlegroups.com
Cheers. Awesome compact project.
Reply all
Reply to author
Forward
0 new messages