How to set the JDK target used into MANIFEST.MF Build-Jdk

Hi all, currently I am trying to set properly the JDK target used when jarring my modules. What I have tried is: build plugins !-- maven2 jar plugin configuration -- plugin

Castor 1.0 pom is missing into http://repo1.maven.org/maven2/castor/castor/1.0/

Hi all, I want to notify you that Castor 1.0 pom is missing into http://repo1.maven.org/maven2/castor/castor/1.0/. This should be corrected. Thank you. Regards, Dobri

How do I change the default goal of a war plugin

How do I change the default goal of a war so that it produces an exploded war instead of .war file when I run the package goal? I am trying to do the following, but it seems not working: plugin groupIdorg.apache.maven.plugins/groupId

Re: Can i use variables within the parentartifactId section?

Hi Baz, my observations are that it is not possible to use a placeholder for the groupId, artifactId, version of the parent pom for example. As you said the CLI -D option is not taken into consideration. Anyway, m2 take this option into consideration at some later stage, but not when it identifies

Assembly plugin with several descriptors

Hi all, currently I am trying to execute an assembly that makes use of two descriptors. I want to package a given artifact as a ZIP (i.e. my product eclipse plugin) and then include it in an artifact (i.e. my product distribution) that has a DIR and ZIP format set. The problem is that in the first

Updating assembly plugin failed using Maven 2.0.7

Hi all, I have an issue updating the assembly plugin from 2.2-beta-1 to 2.2-beta-2 version. The exception thrown is the following: OS name: linux version: 2.6.9-55.elsmp arch: i386 [exec] [DEBUG] Building Maven user-level plugin registry from: '/home/buildsag/.m2/plugin-registry.xml'

Re: Maven 2.0.7 and relativePath/

here. -Original Message- From: Dobri Kitipov [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 11:54 PM To: Maven Users List Subject: Re: Maven 2.0.7 and relativePath/ Hi Brian, thank you! You are right this placeholders in g/a/v are causing me lots of troubles. But anyway

Re: Maven 2.0.7 and relativePath/

Yes, right. Thanks! On Fri, May 9, 2008 at 11:24 AM, Brian E. Fox [EMAIL PROTECTED] wrote: You can use snapshots, you should still not use properties in parent.* or project.groupId / project.artifactId / project.version -Original Message- From: Dobri Kitipov [mailto:[EMAIL

Re: Maven 2.0.7 and relativePath/

not have properties in the g/a/v of either the parent section or the primary declaration of an artifact (project.group...etc) as this will surely cause you lots of headaches. -Original Message- From: Dobri Kitipov [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 7:50 AM To: users

Maven 2.0.7 and relativePath/

Hi all, I did not find a good explanation about the usage of relativePath/ in the net. I am interested if I have e.g.: parent groupIdcom.mycomp/groupId artifactIdmycomp-parent-pom/artifactId version${mycomp.version}/version

Maven assembly with more than one descriptor

Hi all, I want to provide in my assmbly plugin configuration two descriptors (i.e. mycomp-eclipse-bin-assembly.xml and mycomp-bin-assembly.xml) and be guaranteed in the order of execution. I mean the first one listed is executed prior the second one: plugin

Trying to deploy an artifact with all its dependencies from local to remote repository with maven-deploy plugin.

Hi all, I want to ask how to update my mirror repository. The case is the following. I want to use the latest maven-assembly-plugin. I succeeded to download it locally in my local repository. Now I want to share this plugin and all its dependencies with my team. To do so I need to deploy this