Re: Maven - ERROR: Maven JVM terminated unexpectedly with exit code 0

This looks to me like the tool that you're using is calling System.exit(0). On 27/07/2011, at 5:47 PM, RockyJerald wrote: > Hi All, > > I have written pom.xml for auto deployment process between hudson and > deployment servers. > > The script which i return its working perfectly i can see the

Re: gitflow releases with maven?

On 28/07/2011, at 2:23 AM, Lars Fischer wrote: >> After the git flow release is finnished, both master and develop sit at the >> next -SNAPSHOT version, >> this actually works out nice as it means you can then at some point do a >> "git flow hotfix start..." >> if need be to patch the last relea

RE: Why would "unpack-dependencies" sometimes not do its job?

> -Original Message- > From: KARR, DAVID (ATTSI) > Sent: Thursday, July 28, 2011 7:03 AM > To: Maven Users List > Subject: RE: Why would "unpack-dependencies" sometimes not do its job? > > > -Original Message- > > From: Brian Fox [mailto:bri...@infinity.nu] > > Sent: Wednesday, Jul

RE: Why would "unpack-dependencies" sometimes not do its job?

> -Original Message- > From: Brian Fox [mailto:bri...@infinity.nu] > Sent: Wednesday, July 27, 2011 8:49 AM > To: Maven Users List > Subject: Re: Why would "unpack-dependencies" sometimes not do its job? > > default is: > > overWriteIfNewer=true > overWriteReleases = false > overWriteSnap

Re: How to use the latest version from dependencies (not from all repository)

On 28/07/2011 7:39 AM, boraldo wrote: Suppose I have the following artifacts. I will omit groups for simplicity. A:1.0 A:2.0 A:3.0 B:1.0 depends on A:1.0 C:1.0 depends on A:2.0 D:1.0 depends on B:1.0, C:1.0 I want D to use the latest version of A that is inherited from it's dependencies (not fr

How to use the latest version from dependencies (not from all repository)

Suppose I have the following artifacts. I will omit groups for simplicity. A:1.0 A:2.0 A:3.0 B:1.0 depends on A:1.0 C:1.0 depends on A:2.0 D:1.0 depends on B:1.0, C:1.0 I want D to use the latest version of A that is inherited from it's dependencies (not from repository). In this case it is 2.0.

Re: release plugin tagging with -SNAPSHOT

http://jira.codehaus.org/browse/MRELEASE-697 On Thu, Jul 28, 2011 at 2:30 AM, Barrie Treloar wrote: > On Thu, Jul 28, 2011 at 1:46 PM, Benson Margulies > wrote: >> Never mind this here, I isolated this to 2.2 and made a JIRA. > > Can you post the Jira so I can look at the summary of the proble

Maven + Seam 3 Create modular application

Hi, I'm new to Maven. I started to develop a very big application with Seam 3. The architecture of the software will be modular. I need a way to divide each module into his own .jar/.war file and compile them together. Can you give me example how to edit the pom.xml file in order to achieve my g

Re: release plugin tagging with -SNAPSHOT

+1 under git, was just thinking I should raise a bug for it when I saw this email. Watched and voted.. On 28/07/2011, at 7:30 PM, Julien HENRY wrote: > We are facing the same issue. This is a regression since last release of > m-release-p. The proposed tag name contains a -SNAPSHOT.

Re: release plugin tagging with -SNAPSHOT

Hi, We are facing the same issue. This is a regression since last release of m-release-p. The proposed tag name contains a -SNAPSHOT. http://jira.codehaus.org/browse/MRELEASE-697 Regards, Julien - Mail original - > De : Barrie Treloar > À : Maven Users List > Cc : > Envoyé le :

Re: how do i get maven-gpg-plugin to sign with primary key rather than sub key

David Smith googlemail.com> writes: > > how do i get maven-gpg-plugin to sign with sub key rather than primary key? > > Details: > I am using the maven-gpg-plugin to sign some files prior to uploading to oss.sonatype.org maven repo. > This repo seems to expect the files to be signed with the