Buen producto!!

Estimado amigo, ?Cómo está usted recientemente? decirte una gran sorpresa! Ktpshop compa?ía es una empresa de comercio electrónico de productos que ha clasificado superior Asia --- (www.ktpshop.info) y cuenta con la cooperación con Nokia, Sony, HP, etc durante muchos a?os, la calidad del producto e

Re: SNAPSHOT for parent pom versioning

adata.xml file of the > seta.config:seta-general-configuration:1.0-SNAPSHOT artifact? > > On Mon, May 18, 2009 at 09:24, Bocalinda wrote: > > Hi Anders, > > > > Thanks a lot.. You are right, I need to specifically specify to update on > > each build. > > When I do so, I c

Re: SNAPSHOT for parent pom versioning

ettings.xml: > > http://maven.apache.org/ref/2.0.8/maven-settings/settings.html#class_releases > > Here's a blog about this: > > http://jlorenzen.blogspot.com/2008/07/maven-not-downloading-latest-snapshots.html > > /Anders > > On Fri, May 15, 2009 at 12:14, Boca

SNAPSHOT for parent pom versioning

Hi List, According to the documentation, when specifying a version as -SNAPSHOT, Maven downloads the artifact on each build. I specify: config seta-general-configuration 1.0-SNAPSHOT and expected Maven to download the parent pom again from the repository, however, this doesn't s

Re: Referencing plugin properties

u, May 14, 2009 at 11:08 AM, Bocalinda wrote: > > > Hi List, > > > > It is possible to reference pom properties with ${project.version} for > > example. > > But how can I reference plugin properties? > > > > I would like to reference the webapp directory.

Profile activation on project property

Hi List, I have been struggling since a few days now with the following problem. I want a profile to be enabled based on a project property, in my case project.packaging. I've tried doing this in the following way: project.packaging war Unfortunately the profile is

Referencing plugin properties

Hi List, It is possible to reference pom properties with ${project.version} for example. But how can I reference plugin properties? I would like to reference the webapp directory. The property is called webappDirectory, but I can't seem to get it's value. Thanks.

Re: Cargo and multi-module projects

Btw, your solution didn't work for me (activating based on a property set in another module). It seems that the profiles are being parsed before the property is set in my module. 2009/5/12 Bocalinda > Hi Jesse, > > As a workaround for the profile activation by packaging type

Re: Cargo and multi-module projects

Hi Jesse, As a workaround for the profile activation by packaging type, it may be an option to use: ${project.packaging} war Cheers, Pieter 2009/5/11 > Hi Pieter, > > On Mon, May 11, 2009 at 11:47 AM, Bocalinda wrote: > > > > What e

Profile activation using multiple properties

Hi List, Stating from the Maven Definitive Guide: "Activations can contain one of more selectors including JDK versions, Operating System parameters, files, and properties. A profile is activated when all activation criteria has been satisfied." Unfortunately, it seems that is is not possible to

Re: Cargo and multi-module projects

ation-test stop P.D. Thanks for creating the JIRA case, would definitely be useful! Cheers, Pieter 2009/5/11 > Hi Bocalinda, > > On Mon, May 11, 2009 at 11:28 A

Re: Cargo and multi-module projects

Hi Jesse, Glad I'm not the only one who is trying such thing. Great solution you just gave me, I hope this works for me as well. Big thanks! 2009/5/11 > Hi Bocalinda, > > On Mon, May 11, 2009 at 10:28 AM, Bocalinda wrote: > > > > In order to achieve automatic tes

Cargo and multi-module projects

Hi List, In order to achieve automatic testing of my projects, I use Cargo to automatically deploy newly generated war files to a Tomcat server. All the specifics to the automatic testing (depedencies, plugin configuration, etc) are contained inside of a super pom. Because I have multitudes of pr