Re: release plugin tagging with -SNAPSHOT

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 problem please? - To unsubscribe, e-mail: users-u

Re: release plugin tagging with -SNAPSHOT

Never mind this here, I isolated this to 2.2 and made a JIRA. On Wed, Jul 27, 2011 at 11:59 PM, Benson Margulies wrote: > Here's some dialog with release:prepare > > [INFO] Checking dependencies and plugins for snapshots ... > What is the release version for "Parent POM for the Juggernaut > compo

release plugin tagging with -SNAPSHOT

Here's some dialog with release:prepare [INFO] Checking dependencies and plugins for snapshots ... What is the release version for "Parent POM for the Juggernaut components"? (com.basistech.jug:jug-parent) 57: : What is SCM release tag or label for "Parent POM for the Juggernaut components"? (com.

Re: dependency:copy and transitive dependencies of artifactItems

You can't, copy-dependencies is intended to work on the current project, and copy is intended to simply fetch another artifact only. On Wed, Jul 27, 2011 at 4:15 PM, cowwoc wrote: > Brian, > > How do specify a project argument for "copy-dependencies"? That is, I need > to copy the dependencies of

Re: dependency:copy and transitive dependencies of artifactItems

Brian, How do specify a project argument for "copy-dependencies"? That is, I need to copy the dependencies of another project (not the current one). Thanks, Gili Brian Fox-2 wrote: > > It does not support transitivity yet. You can use copy-dependencies and > combinations of the filters to get

Re: help with mvn release:prepare

this is a known bug introduced in 2.2. The work around is to passed in -Dtag=your-artifact-id-your-version -D On Wed, Jul 27, 2011 at 11:58 AM, Andrew Eisenberg wrote: > Hi all, > > I am having some trouble with the release:prepare goal. I am trying to > release version 2.5.1-1 of my artifact.  

Re: Set specific plugin versions for a project - issue in plugin-registry.xml/maven-metada-local.xml

; > Since these projects are unrelated, they can't be glued together via a > parent pom. I don't see why not. Consider the following example: http://img.skitch.com/20110727-b3j3j8fk2rg4s2h9exm225skyd.png You just need to have a hierarchy of parent poms. Sure, if you update the top Co

help with mvn release:prepare

Hi all, I am having some trouble with the release:prepare goal. I am trying to release version 2.5.1-1 of my artifact. The currently released version is 2.5.1. The version number in the pom.xml is 2.5.1-1-SNAPSHOT. And the artifact is in a standard svn repository. I run mvn release:prepare and

Re: Set specific plugin versions for a project - issue in plugin-registry.xml/maven-metada-local.xml

On Wed, Jul 27, 2011 at 10:05 PM, Ansgar Konermann wrote: > Am 27.07.2011 08:16, schrieb Kasun Gajasinghe: >> We don't allow downloading of different versions of same plugin which >> in most cases does the 'same' job! So, we need the ability to set a >> default plugin versions that are available o

Re: Set specific plugin versions for a project - issue in plugin-registry.xml/maven-metada-local.xml

Am 27.07.2011 08:16, schrieb Kasun Gajasinghe: > We don't allow downloading of different versions of same plugin which > in most cases does the 'same' job! So, we need the ability to set a > default plugin versions that are available on the gentoo system. Hi Kasun, what about this: configure a loc

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

default is: overWriteIfNewer=true overWriteReleases = false overWriteSnapshots=false Setting the releases or snapshots to true will cause it to ignore the if newer check. On Wed, Jul 27, 2011 at 11:13 AM, KARR, DAVID (ATTSI) wrote: >> -Original Message- >> From: Brian Fox [mailto:bri...

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

> -Original Message- > From: Brian Fox [mailto:bri...@infinity.nu] > Sent: Tuesday, July 26, 2011 5:01 PM > To: Maven Users List > Subject: Re: Why would "unpack-dependencies" sometimes not do its job? > > you can set a flag to tell it to always unpack. I forget the exact > param, but it's

Re: Should I use classifiers to differentiate between "devel" and "production" builds?

On 27/07/2011 9:43 AM, Daniel Serodio (lists) wrote: Ansgar Konermann wrote: Am 25.07.2011 22:13, schrieb Daniel Serodio (lists): Do you think using a classifier to differentiate artifacts built for development and production is "hacky", is is this an appropriate solution? Use the same *artif

Re: gitflow releases with maven?

2011/7/26 Mark Derricutt : > Before cutting the release, I start a new release branch, do the maven > release, then when I'm happy, finish the release branch, THEN push to origin > > $ git flow release start 3.4.5 > $ mvn release:prepare release:perform > $ git flow release finish 3.4.5 > $ git pu

Re: Should I use classifiers to differentiate between "devel" and "production" builds?

On Wed, Jul 27, 2011 at 8:43 AM, Daniel Serodio (lists) < daniel.lis...@xxx.com.br> wrote: > Ansgar Konermann wrote: > >> Am 25.07.2011 22:13, schrieb Daniel Serodio (lists): >> >>> Do you think using a classifier to differentiate artifacts built for >>> development and production is "hacky", is i

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

> [ServerConnectionImpl.close():332] : Closing DM connection > [ServerConnectionImpl.close():352] : Unregistered all listeners > [ServerConnectionImpl.closeJMX():372] : Closed JMX connection > [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection > [ServerConnectionImpl.closeJMX():3

Re: Should I use classifiers to differentiate between "devel" and "production" builds?

Ansgar Konermann wrote: Am 25.07.2011 22:13, schrieb Daniel Serodio (lists): Do you think using a classifier to differentiate artifacts built for development and production is "hacky", is is this an appropriate solution? Use the same *artifacts* for all stages and allow for *configuring* the r

Re: mvn install problem

Prabin, The error log says that it can't find the parent pom file specified in the agentj-core module in your source. Since maven can't find the pom file in remote repositories, I assume you have the parent pom file included in your source. So, look for the pom.xml file with both groupId and artifa

mvn install problem

hello everybody, I am very new in using and installing maven. When I try to mvn install maven in directory ns-allinone-2.34/ns-2.34/agentj, it gives following error; prabin@prabin-desktop:~$ cd $AGENTJ prabin@prabin-desktop:~/ns-allinone-2.34/ns-2.34/agentj$ mvn install [INFO] Scanning for project

installing maven-2.2.1 in ubuntu 10.04

hello everybody, I am very new in using and installing maven. When I try to mvn install maven in directory ns-allinone-2.34/ns-2.34/agentj, it gives following error; prabin@prabin-desktop:~$ cd $AGENTJ prabin@prabin-desktop:~/ns-allinone-2.34/ns-2.34/agentj$ mvn install [INFO] Scanning for project

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

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 application in web logic server. The application has been deployed in the web logic server. No issues in that. All the remaining task is