I want to issue commands like `-Dmaven.test.skip=true -Dcheckstyle.skip`

In netbeans 7 how do I skip testing and add maven additional parameters when building a maven project?

I am building my project using Maven. My maven version is apache-maven-3.0.4. I am using Eclipse Luna. When I try to build my project I get the following error

&gt; [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:2.7:resources (default-resources) on project OrionCommunity: Mark invalid -&gt; [Help 1].

Following is the stack trace when I run mvn clean install `-X`:

    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 1:53.295s
    [INFO] Finished at: Thu Oct 09 20:00:26 IST 2014
    [INFO] Final Memory: 9M/25M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:2.7:resources (default-resources) on project OrionCommunity: Mark invalid -&gt; [Hel
    p 1]
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:2.7:resources (default-resources)
     on project OrionCommunity: Mark invalid
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
            at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
            at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
            at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
            at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
    Caused by: org.apache.maven.plugin.MojoExecutionException: Mark invalid
            at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo.java:306)
            at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
            ... 19 more
    Caused by: org.apache.maven.shared.filtering.MavenFilteringException: Mark invalid
            at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:129)
            at org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources(DefaultMavenResourcesFiltering.java:264)
            at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo.java:300)
            ... 21 more
    Caused by: java.io.IOException: Mark invalid
            at java.io.BufferedReader.reset(BufferedReader.java:485)
            at org.apache.maven.shared.filtering.MultiDelimiterInterpolatorFilterReaderLineEnding.read(MultiDelimiterInterpolatorFilterReaderLineEnding.java:416)
            at org.apache.maven.shared.filtering.MultiDelimiterInterpolatorFilterReaderLineEnding.read(MultiDelimiterInterpolatorFilterReaderLineEnding.java:205)
            at java.io.Reader.read(Reader.java:123)
            at org.apache.maven.shared.utils.io.IOUtil.copy(IOUtil.java:181)
            at org.apache.maven.shared.utils.io.IOUtil.copy(IOUtil.java:168)
            at org.apache.maven.shared.utils.io.FileUtils.copyFile(FileUtils.java:1856)
            at org.apache.maven.shared.utils.io.FileUtils.copyFile(FileUtils.java:1804)
            at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:114)
            ... 23 more

My maven repository is under D:/mavenrepo. I have completely deleted all the jars present in the repo and did a clean install. But I still get this error.

Maven:Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:2.7:resources

I am using a different plugin (ant4eclipse) to jar my files. What is the best way to avoid the maven-jar plugin from executing?

 - I tried to remove the `&lt;plugin&gt;maven-jar-plugin&lt;/plugin&gt;`
 - I tried to `&lt;exclude&gt; ** / * &lt; / exclude&gt;`
 - I tried to `&lt;skip&gt;true&lt;/skip&gt;`

None worked



What is the best way to avoid maven-jar?

I get this error when trying to compile a Vaadin WAR:

    Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.1.1:war (default-war) on project testvaadin-web: Error assembling WAR: webxml attribute is required (or pre-existing WEB-INF/web.xml if executing in update mode) -&gt; [Help 1]

I know this error means that maven cannot find my web.xml, but in the &quot;Book of Vaadin&quot; it says that **web.xml is not needed** when using Servlet API 3.0 and the Annotation `@WebServlet` in your UI class. 

I am compiling my widgetsets in a separate profile (according to [this](http://bluegulf.wordpress.com/2012/10/18/tutorial-of-setting-up-eclipsemavenvaadinjetty-project-ide-2/) guide) and it compiles fine when I rnu this profile. However, when I compile only the web-project, I get above mentioned error.

What gives?

Do I override the maven behaviour somehow? Vaadin didn&#39;t even create a WEB-INF directory. I guess I could create WEB-INF folder and keep a &quot;ghost&quot; web.xml in there to keep maven happy, but that doesn&#39;t seem right. 

Am I missing something?

Does anyone know a good solution to this?


webxml attribute is required with Servlet 3.0

I&#39;m reading about Maven right now and everywhere in a text I see this word (mojo). I approximately understand what it means, but I would not refuse from a good explanation. I tried to google, but found only non-maven explanations.

POJO - ok, but MOJO? Maven Old Java Object?


What is MOJO in Maven?

I would like to have a Maven goal trigger the execution of a java class. I&#39;m trying to migrate over a &lt;code&gt;Makefile&lt;/code&gt; with the lines:

    neotest:
        mvn exec:java -Dexec.mainClass=&quot;org.dhappy.test.NeoTraverse&quot;

And I would like &lt;code&gt;mvn neotest&lt;/code&gt; to produce what &lt;code&gt;make neotest&lt;/code&gt; does currently.

Neither the &lt;a href=&quot;http://mojo.codehaus.org/exec-maven-plugin/usage.html&quot;&gt;exec plugin documentation&lt;/a&gt; nor the &lt;a href=&quot;http://maven.apache.org/ant-tasks/&quot;&gt;Maven Ant tasks&lt;/a&gt; pages had any sort of straightforward example.

Currently, I&#39;m at:

    &lt;plugin&gt;
      &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
      &lt;artifactId&gt;exec-maven-plugin&lt;/artifactId&gt;
      &lt;version&gt;1.1&lt;/version&gt;
      &lt;executions&gt;&lt;execution&gt;
        &lt;goals&gt;&lt;goal&gt;java&lt;/goal&gt;&lt;/goals&gt;
      &lt;/execution&gt;&lt;/executions&gt;
      &lt;configuration&gt;
        &lt;mainClass&gt;org.dhappy.test.NeoTraverse&lt;/mainClass&gt;
      &lt;/configuration&gt;
    &lt;/plugin&gt;

I don&#39;t know how to trigger the plugin from the command line, though.

How do I execute a program using Maven?

I have determined that two [JAXB][1] plugins for [Maven][2] 2 exist, with some different configurations. 

The one is from Sun: http://jaxb.dev.java.net/jaxb-maven2-plugin/, the other from Mojohaus: http://mojohaus.org/jaxb2-maven-plugin/

Which of these two plugins can be recommended?

------------

Thanks Matt. On my little research project, I found that there&#39;s quite another plugin comming from the sunners:

&lt;!-- language: xml --&gt;

    &lt;groupId&gt;com.sun.tools.xjc.maven2&lt;/groupId&gt;  
    &lt;artifactId&gt;maven-jaxb-plugin&lt;/artifactId&gt;  

and that one:

&lt;!-- language: xml --&gt;

    &lt;groupId&gt;org.jvnet.jaxb2.maven2&lt;/groupId&gt;
    &lt;artifactId&gt;maven-jaxb2-plugin&lt;/artifactId&gt;

and still the one from Codehouse.

  [1]: http://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding
  [2]: http://en.wikipedia.org/wiki/Apache_Maven

Difference of Maven JAXB plugins

I&#39;m trying to compile my Android project and I&#39;m getting this error

    [INFO] Exception in thread &quot;main&quot; java.lang.UnsupportedClassVersionError: com/android/dx/command/Main : Unsupported major.minor version 52.0
    [INFO] 	at java.lang.ClassLoader.defineClass1(Native Method)
    [INFO] 	at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
    [INFO] 	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
    [INFO] 	at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
    [INFO] 	at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
    [INFO] 	at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
    [INFO] 	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    [INFO] 	at java.security.AccessController.doPrivileged(Native Method)
    [INFO] 	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    [INFO] 	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
    [INFO] 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    [INFO] 	at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
    [INFO] 	at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------

I&#39;ve been reading in other post that try to compile with Java 8 might cause that error but not my case, I have the following Java version:

    java version &quot;1.7.0_79&quot;
    OpenJDK Runtime Environment (IcedTea 2.5.5) (7u79-2.5.5-0ubuntu0.14.04.2)
    OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)

OS: Linux Mint
(I&#39;m not have Java 8 installed.)
Build: MAVEN

Can anyone help me with this?


Unsupported major.minor version 52.0 in my app

I thought I was an experienced Maven user, but I am having a mental block on how to do this!

I&#39;ve been able to use the Maven sql plugin to drop, create, and install a schema in a database via plugin executions I&#39;ve defined and bound to the `pre-integration-test` phase.

However, now I&#39;d like to use that same sql plugin to insert some sample data whenever I want from the command line -- that is, not bound to any lifecycle goal.  There are a few different sets of sample data, so I&#39;d like to define a few different executions.

But is there a way to run one of these executions from the command line by using the execution ID perhaps?

Run a single Maven plugin execution?

I created a new simple Maven project in a new Workspace.

When I open the `pom.xml`&#39;s `Dependencies` view in Eclipse editor, and I choose `Add..` dependency, there&#39;s no search results no matter what search criteria I input in the search fields: 

It instantly give me, for example, `Results for &#39;spring&#39; (0)`.

In my other workspace, with my existing projects I don&#39;t have this problem.

Is there a way to fix that ?






Eclipse : Maven search dependencies doesn&#39;t work

I&#39;m putting Maven build around cluster of amateur, poorly written and frankly - primitive C/C++ code (meaning some C, some C++). Problem is - there&#39;s lots of it in circulation currently and cannot be easily replaced. Building it requires a lot of tribal knowledge (you have to go from cube to cube just to find out how to compile/build various parts) and releasing is total nightmare. (No - I&#39;m not going to rewrite it, plz don&#39;t ask)
My question is - should I use `maven-native-plugin` to replace multitude of short makefiles or use `exec-maven-plugin` to simply execute these? 
I had [pretty good experience][1] so far with the latter doing .NET and don&#39;t know if I should invest into `native` plugin or stay with `exec`? If you had experience with &quot;Mavenizing&quot; C/C++ I would love to get some advice.


  [1]: http://dev.bostone.us/2009/10/08/using-maven-to-manage-net-projects/

Using Maven for C/C++ projects

I use maven to build a multi module project. My module 2 depends on Module 1 src at compile scope and module 1 tests in test scope.

Module 2 -

       &lt;dependency&gt;
           &lt;groupId&gt;blah&lt;/groupId&gt;
           &lt;artifactId&gt;MODULE1&lt;/artifactId&gt;
           &lt;version&gt;blah&lt;/version&gt;
           &lt;classifier&gt;tests&lt;/classifier&gt;
           &lt;scope&gt;test&lt;/scope&gt;
       &lt;/dependency&gt;

This works fine. Say my module 3 depends on Module1 src and tests at compile time. 

Module 3 -

       &lt;dependency&gt;
           &lt;groupId&gt;blah&lt;/groupId&gt;
           &lt;artifactId&gt;MODULE1&lt;/artifactId&gt;
           &lt;version&gt;blah&lt;/version&gt;
           &lt;classifier&gt;tests&lt;/classifier&gt;
           &lt;scope&gt;compile&lt;/scope&gt;
       &lt;/dependency&gt;

When I run `mvn clean install`, my build runs till module 3, fails at module 3 as it couldn&#39;t resolve the module 1 test dependency. Then I do a `mvn install` on module 3 alone, go back and run `mvn install` on my parent pom to make it build. How can I fix this?

Maven test dependency in multi module project

I am following the [tutorial][1] for creating a maven plugin and cannot run mvn install without getting errors. The info complains that i don&#39;t have the required mojo descriptors when the annotations should be generating them for me. I am running maven 3.0.5 and using intellij as my ide. here is my Main class:

	@Mojo(name = &quot;modify-connector&quot;)
	public class ComplianceMojo extends AbstractMojo {

		@Parameter
		private String artifactId;

		@Parameter
		private String version;

		@Override
		public void execute() throws MojoExecutionException, MojoFailureException {
			File jar = new File(getPluginContext().get(&quot;project.build.directory&quot;) + &quot;/&quot;
					+ getPluginContext().get(&quot;project.build.finalname&quot;) + &quot;/&quot; + artifactId + &quot;-&quot; + version);
			if(jar.exists()){
				getLog().info(&quot;The file exists! &quot; + jar.getAbsolutePath());
			} else {
				getLog().info(&quot;The file does not exist: &quot; + jar.getAbsolutePath());
			}
		}
	}

And here is my pom.xml

	&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
	&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot;
			 xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
			 xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
		&lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;

		&lt;groupId&gt;mysql-jdbc-compliance-maven-plugin&lt;/groupId&gt;
		&lt;artifactId&gt;mysql-jdbc-compliance-maven-plugin&lt;/artifactId&gt;
		&lt;version&gt;1.0-SNAPSHOT&lt;/version&gt;
		&lt;packaging&gt;maven-plugin&lt;/packaging&gt;

		&lt;dependencies&gt;
			&lt;dependency&gt;
				&lt;groupId&gt;org.apache.maven&lt;/groupId&gt;
				&lt;artifactId&gt;maven-plugin-api&lt;/artifactId&gt;
				&lt;version&gt;2.0&lt;/version&gt;
			&lt;/dependency&gt;
			&lt;dependency&gt;
				&lt;groupId&gt;org.apache.maven.plugin-tools&lt;/groupId&gt;
				&lt;artifactId&gt;maven-plugin-annotations&lt;/artifactId&gt;
				&lt;version&gt;3.2&lt;/version&gt;
				&lt;scope&gt;provided&lt;/scope&gt;
			&lt;/dependency&gt;
		&lt;/dependencies&gt;

	&lt;/project&gt;

&lt;b&gt;Note:&lt;/b&gt; I had to separately add the annotations dependency as the main plugin api did not contain these classes. when i run mvn install on my project, the output is as follows:

	[INFO] ------------------------------------------------------------------------
	[INFO] BUILD FAILURE
	[INFO] ------------------------------------------------------------------------
	[INFO] Total time: 0.867s
	[INFO] Finished at: Wed Sep 25 17:45:55 EST 2013
	[INFO] Final Memory: 8M/244M
	[INFO] ------------------------------------------------------------------------
	[ERROR] Failed to execute goal org.apache.maven.plugins:maven-plugin-plugin:2.9:descriptor (default-descriptor) on project mysql-jdbc-compliance-maven-plugin: Error extracting plugin descriptor: &#39;No mojo definitions were found for plugin: mysql-jdbc-compliance-maven-plugin:mysql-jdbc-compliance-maven-plugin.&#39; -&gt; [Help 1]
	[ERROR] 
	[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
	[ERROR] Re-run Maven using the -X switch to enable full debug logging.
	[ERROR] 
	[ERROR] For more information about the errors and possible solutions, please read the following articles:
	[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

[1]: http://maven.apache.org/guides/plugin/guide-java-plugin-development.html

Basic maven plugin project not working, Mojo plugin descriptors not generating

On Windows 7, I am trying to send the output of a **maven-3** command to a text file.

I call the command from the root of the project I am trying to analyze.

The command is:

    mvn dependency:tree -Dverbose -Dincludes=commons-collections -DoutputFile=C:\Users\myname\Documents\output.txt

When I run the command without the `outputFile` parameter, I see the output sent to the console.

But when I use it with the `outputFile` parameter, the output file is empty.

Any idea what I am missing here?

Send maven output to file

Since I updated to Maven 3 I get the following warning messages at each build :

How can I get rid of these warnings?

    [INFO] Scanning for projects...
    [WARNING] 
    [WARNING] Some problems were encountered while building the effective model for proj:id:jar:3.1
    [WARNING] &#39;build.plugins.plugin.version&#39; for org.apache.maven.plugins:maven-javadoc-plugin is missing. @ line 195, column 15
    [WARNING] &#39;build.plugins.plugin.version&#39; for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 204, column 15
    [WARNING] &#39;build.plugins.plugin.version&#39; for org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 227, column 15
    [WARNING] &#39;build.plugins.plugin.version&#39; for org.apache.maven.plugins:maven-jar-plugin is missing. @ line 215, column 15
    [WARNING] &#39;reporting.plugins.plugin.version&#39; for org.codehaus.mojo:jdepend-maven-plugin is missing. @ line 271, column 15
    [WARNING] 
    [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
    [WARNING] 
    [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.



Maven 3 warnings about build.plugins.plugin.version

I have following dependency in pom.xml:

    &lt;dependency&gt;
        &lt;groupId&gt;org.projectlombok&lt;/groupId&gt;
        &lt;artifactId&gt;lombok&lt;/artifactId&gt;
        &lt;version&gt;1.16.8&lt;/version&gt;
    &lt;/dependency&gt;

When I run `mvn clean install`, I have following error:

    Caused by: java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
        at java.lang.ClassLoader.findClass (ClassLoader.java:711)
        at java.lang.ClassLoader.loadClass (ClassLoader.java:566)
        at lombok.launch.ShadowClassLoader.loadClass (ShadowClassLoader.java:418)

I tried to use java `1.8, 1.9, 1.10`. And I tried lombok `1.6.10, 1.6.12, 1.6.20`. All of them have the same problem.

Caused by: java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags when using lombok

I have a Maven web project in my repo.  

I am a Maven noob but still I understand the fact that there are plugins which we need to configure only then we could run plugin specific commands.

**Facts:**

I have a sonar server running on my local machine at port 9000.

I have not added any sonar specific plugin in my POM.xml

**Reference:**

http://www.sonarsource.org/we-had-a-dream-mvn-sonarsonar/

**Observation:**

But still when I run `mvn sonar:sonar` in my project from command line it works fine.

Matter of the fact is **I have NOT configured sonar plugin in my POM.xml Even then from where the hell Maven is picking up and understanding &quot;sonar:sonar&quot; goal/command?**

**Question / curiosity:**

I don&#39;t want the working knowledge of sonar itself. I want to know why `mvn sonar:sonar` works without configuring a sonar plugin in my pom.xml

WHY and how?

Why does the Maven command &quot;mvn sonar:sonar&quot; work without any plugin configuration in my &quot;pom.xml&quot;?

I am using maven-assembly plugin to create a jar of my application, including its dependencies as follows:

    &lt;assembly&gt;
        &lt;id&gt;macosx&lt;/id&gt;
        &lt;formats&gt;
           &lt;format&gt;tar.gz&lt;/format&gt;
           &lt;format&gt;dir&lt;/format&gt;
        &lt;/formats&gt;
        &lt;dependencySets&gt;
            &lt;dependencySet&gt;
                &lt;includes&gt;
                    &lt;include&gt;*:jar&lt;/include&gt;
                &lt;/includes&gt;
                &lt;outputDirectory&gt;lib&lt;/outputDirectory&gt;
            &lt;/dependencySet&gt;
        &lt;/dependencySets&gt;
    &lt;/assembly&gt;

(I omitted some other stuff that is not related to the question)

So far this has worked fine because it creates a `lib` directory with all dependencies. However, I recently added a new dependency whose scope is `system`, and it does not copy it to the `lib` output directory. i must be missing something basic here, so I call for help.

The dependency that I just added is:

    &lt;dependency&gt;
      &lt;groupId&gt;sourceforge.jchart2d&lt;/groupId&gt;
      &lt;artifactId&gt;jchart2d&lt;/artifactId&gt;
      &lt;version&gt;3.1.0&lt;/version&gt;
      &lt;scope&gt;system&lt;/scope&gt;
      &lt;systemPath&gt;${project.basedir}/external/jchart2d-3.1.0.jar&lt;/systemPath&gt;
    &lt;/dependency&gt;

The only way I was able to include this dependency was by adding the following to the assembly element:
    
    &lt;files&gt;
        &lt;file&gt;
            &lt;source&gt;external/jchart2d-3.1.0.jar&lt;/source&gt;
            &lt;outputDirectory&gt;lib&lt;/outputDirectory&gt;
        &lt;/file&gt;
    &lt;/files&gt;

However, this forces me to change the pom and the assembly file whenever this jar is renamed, if ever. Also, it seems just wrong.

I have tried with `&lt;scope&gt;runtime&lt;/scope&gt;` in the `dependencySets` and `&lt;include&gt;sourceforge.jchart2d:jchart2d&lt;/include&gt;` with no luck.

So how do you include a `system` scoped jar to your assembly file in maven 2?

Thanks a lot

Maven 2 assembly with dependencies: jar under scope &quot;system&quot; not included

I am trying to use the solution [described here][1] to solve the annoying &quot;Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:build-helper-maven-plugin:1.7:add-source (execution: default, phase: generate-sources)&quot; when I place the following plugin on my pom.xml:

    &lt;plugin&gt;
    &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
    &lt;artifactId&gt;build-helper-maven-plugin&lt;/artifactId&gt;
    &lt;executions&gt;
        &lt;execution&gt;
            &lt;phase&gt;generate-sources&lt;/phase&gt;
            &lt;goals&gt;&lt;goal&gt;add-source&lt;/goal&gt;&lt;/goals&gt;
            &lt;configuration&gt;
                &lt;sources&gt;
                    &lt;source&gt;src/bootstrap/java&lt;/source&gt;
                &lt;/sources&gt;
            &lt;/configuration&gt;
        &lt;/execution&gt;
    &lt;/executions&gt;
	&lt;/plugin&gt;

But when I run mvn clean install I get this:

Reason: POM &#39;org.eclipse.m2e:lifecycle-mapping&#39; not found in repository: Unable to download the artifact from any repository

Does anyone have a clue on how to make m2e and maven happy?

[1]:https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html

m2e lifecycle-mapping not found

I just started using Maven and I read that plugins are additional components that can be used.   
A typical structure of `pom.xml` file is

&lt;!-- language: xml-lang --&gt;

    &lt;project&gt;
      &lt;groupId&gt;org.koshik.javabrains&lt;/groupId&gt;
      &lt;artifactId&gt;JarName&lt;/artifactId&gt; (A fldernamed JarName was created) 
      &lt;version&gt;1.0-SNAPSHOT&lt;/version&gt;
      &lt;packaging&gt;jar&lt;/packaging&gt;
    
      &lt;name&gt;JarName&lt;/name&gt;
      &lt;url&gt;http://maven.apache.org&lt;/url&gt;
    
      &lt;properties&gt;
        &lt;project.build.sourceEncoding&gt;UTF-8&lt;/project.build.sourceEncoding&gt;
      &lt;/properties&gt;
    
      &lt;dependencies&gt;
        &lt;dependency&gt;
          &lt;groupId&gt;junit&lt;/groupId&gt;
          &lt;artifactId&gt;junit&lt;/artifactId&gt;
          &lt;version&gt;3.8.1&lt;/version&gt;
          &lt;scope&gt;test&lt;/scope&gt;
        &lt;/dependency&gt;
      &lt;/dependencies&gt;
    &lt;/project&gt;

**Question**: Where should I insert a `plugin` tag? such as the following:

    &lt;plugin&gt;
      &lt;groupId&gt;org.jibx&lt;/groupId&gt;
      &lt;artifactId&gt;jibx-maven-plugin&lt;/artifactId&gt;
      &lt;version&gt;1.2.4&lt;/version&gt;
      &lt;executions&gt;
        &lt;execution&gt;
          &lt;goals&gt;
            &lt;goal&gt;bind&lt;/goal&gt;
          &lt;/goals&gt;
        &lt;/execution&gt;
      &lt;/executions&gt;
    &lt;/plugin&gt;

Before the dependency or after the `dependency` tag? Does it matter?

Plugins in Maven and POM.xml

I am fairly new to Maven and pom.xml. Is there a way I can find out which of my dependencies that are outdated, so that I can update version numbers in my pom.xml.

In other languages, for instance, Ruby has the command `gem list outdated` that gives me a list of dependencies (rubygems) I can update


I am using IntelliJ Idea if that can help.



All Maven Plugin Solutions on Gang of Coders

Total of 21 Maven Plugin Solutions