maven-plugin

I am wondering which sonar-maven-plugin in which version I should use. As far as I know there is a org.codehaus.mojo version and two org.codehaus.sonar versions ( sonar-maven3-plugin , sonar-maven-plugin ). As far as I understand the sonar-maven3-plugin is now deprecated and the org.codehaus.sonar:sonar-maven-plugin should be used instead. However those org.codehaus.sonar version are tied to a certain version of the sonar server, therefore it makes probably no sense to use them directly. To be able to deal with this there is the org.codehaus. mojo :sonar-maven-plugin which checks which sonar

I'm trying to use maven-plugin-testing-harness version 2.1 with the following test case: public class FooTest extends AbstractMojoTestCase { @Override protected void setUp() throws Exception { super.setUp(); } public void testSomething() throws Exception { // todo } } The test fails at the setUp() call: org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException role: org.apache.maven.repository.RepositorySystem roleHint: at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:257) at org.codehaus.plexus

This used to work before I upgraded Jenkins to 1.494. Now I get this error in Jenkins when using the build promotion plugin to copy the war artifact to the snapshot repo: ERROR: Failed to deploy artifacts: Could not transfer artifact com.blah.data:RestWebServices:war:1.0-20121224.163825-2 from/to archiva.apache.snapshots (http://10.31.31.64:8080/archiva/repository/snapshots): Failed to transfer file: http://10.31.31.64:8080/archiva/repository/snapshots/com/blah/data/RestWebServices/1.0-SNAPSHOT/RestWebServices-1.0-20121224.163825-2.war. Return code is: 401, ReasonPhrase:Unauthorized. org

I have a problem with maven assembly plugin. I have a maven project which use several jars. Each jar contains configuration files. With another project, I use maven assembly plugin to assemble all configurations in unique jar. All work fine but unfortunately, two files are the same name and the second overwrites the first. I don't achieve to tell maven to merge the two files instead of overwrite. Someone knows how to do that ? Thanks. It is not exactly what you are looking for, but I would use http://maven.apache.org/plugins/maven-antrun-plugin/ plugin to run ant concat task http://ant.apache

Is there any to get the entire remote repository, say from http://repo1.maven.org/maven2/ , to my local repository (to %USERPROFILE% )? From http://maven.apache.org/community.html : Being a Good Maven Citizen The concept of a public repository built into the core architecture of Maven makes it necessarily community-centric. There are a few simple things that Maven users may do to help keep that community thriving. Be a Kind Public Repository User The best thing that a user can do is to set up their own remote repository mirror containing the projects needed. There are several tools to make

I am using the Maven-Shade-Plugin to create a runnable Uber-jar. According to the last frame on this page , the size of the jar can be minimized by using: <configuration> <minimizeJar>true</minimizeJar> </configuration> But this feature does not take into consideration the classes that are declared in the log4j.properties file. Hence, e.g. org.apache.log4j.appender.TimeAndSizeRollingAppender is not included in the Uber-jar, even though it’s declared in the log4j.properties file. I believe I will face the same problem with Spring. If my code only refers to interface A and my Spring file

I'm trying to add the svn.revision to project version as a build number and can't seem to do so. My jar has the correct name durin packaging, but its installed in the my local repository it is as if ${buildNumber} is/was undefined when the version was set. I get foo-1.0.0-SNAPSHOT- ${buildNumber} instead of foo-1.0.0-SNAPSHOT- 304 Any idea what I'm doing wrong or is adding a revision to the project version a bad idea? Thanks for the help. <project> ... <version>1.0.0-${release.identifier}-${buildNumber}</version> <properties> <release.identifier>SNAPSHOT</release.identifier> </properties> ...