Re: How replace the maven-jar-plugin with my own one ?

If your jar is a modified version of maven-jar-plugin, the simplest way is to use a specific version that only exists locally at your location (or/and deployed in your corp repository). This is the quickest, but maybe dirtiest way to do that. If you created your own packaging since your build

[INFO] Error building POM (may not be this project's POM). - Project ID: unknown:maven-resources-plugin

I am new to Maven, so please bear with me if the solution to my problem seems simple. I have created a simpel test project using the following pom.xml: *** project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;

Add an argument to jar plugin

Hi, I would like to add a parameter to the execution of the jar command: -J-Dsun.misc.JarIndex.metaInfFilenames=true (see: http://bugs.sun.com/view_bug.do?bug_id=2183678) Reading the doc of m-jar-p I don't see a way to do that. Do you know if this is possible to give argument to the jar

Re: Add an argument to jar plugin

That would be because maven-jar-plugin does _not_ fork the jar command but builds the jar itself On 31 May 2010 11:00, Julien HENRY henr...@yahoo.fr wrote: Hi, I would like to add a parameter to the execution of the jar command: -J-Dsun.misc.JarIndex.metaInfFilenames=true (see:

Re: Easy way to disable surefire during failsafe?

Thanks, Stephen Custom variable to skip surefire is fine for now. Stephen Connolly-2 wrote: file a JIRA for this enhancement until then the solution is to define a property in your pom with value false project ... properties skipUnitTestsfalse/skipUnitTests /properties ...

Re: [INFO] Error building POM (may not be this project's POM). - Project ID: unknown:maven-resources-plugin

I'm guessing that you're getting some html/xml response from the firewall which is stored and interpreted as the pom by Maven. Have you configured your mirror (the artifactory instance) in settings.xml correctly? /Anders On Mon, May 31, 2010 at 10:05, Kenneth Petersen k...@lpk.dk wrote: I am

Maven 3.0-beta-1: maven-surefire-plugin's version not defined in the root-pom anymore?

Hi, I am building a NexusPlugin (packaging type: nexus-plugin). Compilation is fine, but the test execution is problematic. 3.0-alpha-6: Automatically provides me with plugin artifactIdmaven-surefire-plugin/artifactId version2.4.3/version /plugin

Re: Maven 3.0-beta-1: maven-surefire-plugin's version not defined in the root-pom anymore?

A change between alpha-7 and beta-1 is that almost no plugin versions are locked down in the super-POM any more. This change was triggered by this jira: http://jira.codehaus.org/browse/MNG-4453 /Anders On Mon, May 31, 2010 at 13:50, Heix, Andreas andreas.h...@sap.com wrote: Hi, I am building

Re : Add an argument to jar plugin

Thanks Stephen. I will contribute a patch to add a parameter to maven-archiver and plexus-archiver. This parameter will be named indexMetaInfFilenames and will have the same behavior than -Dsun.misc.JarIndex.metaInfFilenames=true in Sun JDK 1.6.0_18+. Regards, Julien - Message

SV: [INFO] Error building POM (may not be this project's POM). - Project ID: unknown:maven-resources-plugin

My settings.xml is as follows: ?xml version=1.0 encoding=UTF-8? settings xsi:schemaLocation=http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd; xmlns=http://maven.apache.org/SETTINGS/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; mirrors

Module dependency with unit test

I think this is a basic Maven module question, but I'm not spotting anything via google. I assume that when unit testing a multi-module project I can unit test module-by-module instead of having to do the entire parent project. Generally, I have a multi-module project hierarchy. I have the

Re: Module dependency with unit test

If you're working on the projects A and B independently, you need to have artifact A in a repo first. The easiest way is to do a mvn install on project A first. That will install that into the local repo so it can be found/used by other projects (on your computer). So, now you can build project B.

RE: Module dependency with unit test

When I get this type of error, I must install the snapshot into my local repo (.m2/...) or install the snapshot into our local nexus repository so the snapshot can be resolved. Luke Bishop RhinoCorps Ltd Co. V: 505.314.9717 M: 505.366.7257 E: lbis...@rhinocorps.com or

Re: Module dependency with unit test

You can also use the --also-make option in combination with the --projects option to only run the builds you want. So on the Master run mvn --projects B --also-make or shorthand, mvn --pl B -am. See also http://blog.redfin.com/devblog/2009/09/maven_reactor_tricks.html Hth, Nick Stolwijk ~Java

[ANN] Maven Doxia Tools 1.2.1 Released

The Maven team is pleased to announce the release of the Maven Doxia Tools, version 1.2.1 This shared component has some utilities that are useful when integrating Doxia in Maven, mainly for site generation and report creation. The main entry point is the SiteTool Plexus component.