Re: Profiles and deployment

It's somewhat difficult to follow what you've got set up here. You can set up several distinct executions of the maven-surefire-plugin with different include/exclude patterns for different tests, controlled by profiles, if you really need to. You can turn test execution on and off entirely with t

Re: Profiles not activating

Thanks! I was aware of that, but it wasn't the problem. My posting (almost immediately after) was that someone appears to have edited the settings file commenting out the aforementioned profile. I should have explained the problem to the bear first. Probably a corner case, but normally all prof

Re: Profiles not activating

Mykel Alvis wrote: > I have a profile in settings.xml that defines a remote repo. That profile > is > > > eclipselink > > false > > >

Re: Profiles

Anyone? orid wrote: > > Hi, > > I came across a problem i can't seam to solve. > I have a set of properties that i need to use in all maven modules. All > modules inherit from the same parent pom. > So far no problem: I defined the properties in the parent pom properties > section and they are

RE: Profiles & Filters - sharing common config

>>But the reference >>is created to the ${sibling_project}/target/classes directory not to >>the artifact produced. So whatever you were going to put into the JAR >>will be in the ${sibling_project}/target/classes directory It's actually a little more screwy than that. It depends on the phas

Re: Profiles & Filters - sharing common config

On 28-Feb-09, at 4:47 PM, Les Hazlewood wrote: Does the remote-resources and dependency plugins require the artifact they're depending on to be in a repository (even the local one)? Yes. The assumption for both of those plugins is that you're requesting the given resource or artifact from

Re: Profiles & Filters - sharing common config

s Hazlewood > Sent: Saturday, February 28, 2009 7:48 PM > To: Maven Users List > Subject: Re: Profiles & Filters - sharing common config > > Does the remote-resources and dependency plugins require the artifact > they're depending on to be in a repository (even the

RE: Profiles & Filters - sharing common config

ck-dependencies will. -Original Message- From: les.hazlew...@anjinllc.com [mailto:les.hazlew...@anjinllc.com] On Behalf Of Les Hazlewood Sent: Saturday, February 28, 2009 7:48 PM To: Maven Users List Subject: Re: Profiles & Filters - sharing common config Does the remote-resources and depend

Re: Profiles & Filters - sharing common config

Does the remote-resources and dependency plugins require the artifact they're depending on to be in a repository (even the local one)? My 'producer' module is a peer to my 'consumer' module. The consumer requires the resources .jar from the producer. I want to run 'mvn package' and have my build

Re: Profiles & Filters - sharing common config

Ahh - I see your approach Jason - using a .vm template. Nice - I'll work with that. Thanks again! Best, Les On Fri, Feb 27, 2009 at 11:03 AM, Les Hazlewood wrote: > Before trying the .tgz file, I wanted to see if I could make it work as > suggested. However, placing the template web.xml file

Re: Profiles & Filters - sharing common config

Before trying the .tgz file, I wanted to see if I could make it work as suggested. However, placing the template web.xml file in src/main/resourcesdidn't work - the consumer's target\maven-shared-archive-resources directory is empty. Here is my relevant config: producer module maven

Re: Profiles & Filters - sharing common config

Thanks Jason, I'll give it a shot right now. Best, Les On Thu, Feb 26, 2009 at 11:54 PM, Jason van Zyl wrote: > There is a bug in the remote-resources-plugin it seems. So I adjusted > slightly and here's a version that works: > > http://people.apache.org/~jvanzyl/les2.tgz

Re: Profiles & Filters - sharing common config

There is a bug in the remote-resources-plugin it seems. So I adjusted slightly and here's a version that works: http://people.apache.org/~jvanzyl/les2.tgz I put the resources in the standard src/main/resources, and then specified the web.xml in the WAR plugin. Not a hard bug to fix but thi

Re: Profiles & Filters - sharing common config

Let me try and whip something up. On 26-Feb-09, at 4:35 PM, Les Hazlewood wrote: Hi all, I'm having a hell of a time getting this to work with web.xml files. Is there an example I can look at that produces a bundle and then consumes one? If there are any uses of this where the template f

Re: Profiles & Filters - sharing common config

Hi all, I'm having a hell of a time getting this to work with web.xml files. Is there an example I can look at that produces a bundle and then consumes one? If there are any uses of this where the template file is an XML file, that'd be really useful. I'm trying to do this using a web.xml file

Re: Profiles & Filters - sharing common config

The remote-resources-plugin. This is exactly how we share license templates across projects. So if you have a web.xml template you want to be used across many projects I would take a look at On 25-Feb-09, at 4:33 PM, Les Hazlewood wrote: I have a webapp that can be deployed as one

Re: Profiles & Filters - sharing common config

On 26/02/2009, at 11:33 AM, Les Hazlewood wrote: I have a webapp that can be deployed as one .war (development) or as two separate .war files (production w/ firewall in between the two). I have 3 web modules to reflect this. web-colocated web-front web-back The web.xml file for each .war

Re: profiles and how to differentiate the build

On Mon, Jul 14, 2008 at 1:10 PM, fuppes <[EMAIL PROTECTED]> wrote: > when I create several profiles for my environments (e.g. integration_test, > system_test, user_test, ...) and i perfrom the build, how do I seperate the > builds in my repository? (because the packages {ear, war} are differend >

Re: Profiles and Resources (wsdl)

The solution is to specify resources in maven-war-plugin http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html Kinski wrote: > > Hi, > > I am re-factoring a legacy web services app as a Maven project which is > now complete apart from one obstacle. I am u

Re: Profiles and/or assemblies?

Some people leverage the JNDI features of their container and insert the proper values for the environment into JNDI. Then you don't include environment-specific values in the jar/war/ear at all. The other trouble you run into when you are trying to build an environment-specific package is that yo

Re: Profiles and Dependencies in Maven ANT Task

Hi Cody, I have forgot to mention that the main build is still done with ant and maven-ant-tasks are used to resolve dependencies. So, unluckily, the example proposed does not really apply... -- View this message in context: http://www.nabble.com/Profiles-and-Dependencies-in-Maven-ANT-Task-tp

Re: Profiles and Dependencies in Maven ANT Task

you can try the example: maven-antrun-plugin start-hsqldb site

Re: Profiles and resources

My apologies. I do too much rambling late nights without getting to the point. Let me clarify. Making a distinction between production resources and development resources is important even outside of the idea of profiles. Consider the following: res | conf | | | mytemplate.xsl |

RE: Profiles and resources

[EMAIL PROTECTED] wrote: > Hi, > > i am struggeling with profiles and resources. > > I have > src/main/resources/application.properties > src/main/dev-resources/application.properties > > my profiles in pom.xml > > > > production >

Re: Profiles and resources

so what is best practice here? even my exclude statemnt doesn't help as i thought. If i run "production" profile after development profile without mvn clean i don't get the right version. thats all much too difficult in my opinion. regards Janning Am Dienstag, 12. Februar 2008 05:03 schrieb C

Re: Profiles and resources

I'll respond by saying there is no garaunteed order of operations with resource copying (as well as other actions that take place within the same build phase). Your pom states that both resources from development and production should be considered when the env property is set to development. (Inc

Re: Profiles and filtering - global files

On Dec 4, 2007 3:40 AM, heimlich <[EMAIL PROTECTED]> wrote: > The problem is that each subproject tries to refer to the 'filters' > directory IN ITS OWN directory structure, > not the one at the top. > > The reason for this structure is that I want: > > ONE conf.properties > ONE filter file per pr

Re: Profiles and filtering - global files

You could make a system variable PROJECT_ROOT other than that I don't know. On Dec 13, 2007 11:56 PM, heimlich <[EMAIL PROTECTED]> wrote: > > Thanks a lot, Mick. That ought to do the trick. One question though, is > there > any way to avoid having a hardcoded path as projectRoot? What I'm looking

Re: Profiles and filtering - global files

Thanks a lot, Mick. That ought to do the trick. One question though, is there any way to avoid having a hardcoded path as projectRoot? What I'm looking for is some way of defining the top-level pom directory (e.g. ${toplevel.project.dir} that points to the directory where I started my mvn command)

Re: Profiles and filtering - global files

I have solved that issue by setting a projectRoot variable: local C:/viewstore/esp_lynx_dap/esp/dap Then my filter is: local ${projectRoot}/src

Re: Profiles and filtering - global files

Yes, i got this problem too this week. On Dec 4, 2007 7:40 AM, heimlich <[EMAIL PROTECTED]> wrote: > > Hi all, > > I'm in a bit of a pickle, and I'm hoping someone can help me out. > > I have an extensive Maven project with the following layout: > > project A, packaging: pom > project A.A, packa

Re: profiles qustion

Sonar, Nishant wrote: > Hi > > > > We work with profiles in maven as > > > > Mvn -Pprofile1,profile2 > > > > On pom > > > > > > > > profile1 > > > > > > ... > > > > > > > > > > profile2 > > > > > > ... > > > > >

Re: profiles qustion

If you just move the "common" stuff out of the profiles, and into the normal section of the pom, then it will be shared by both profiles. Wayne On 10/14/07, Sonar, Nishant <[EMAIL PROTECTED]> wrote: > Hi > > > > We work with profiles in maven as > > > > Mvn -Pprofile1,profile2 > > > > On pom > >

Re: Profiles in maven - help!

Have you enabled filtering for this? Federico. On Thu, 2007-08-16 at 16:10 -0500, Vaidya, Supriya A (US - Chicago) wrote: > HI: > > I have a profiles.xml in my project root folder, that has the following > structure: > > > > > development > >

Re: Profiles

ile is active. If I'm wrong I'd love to know because I would find this very useful. Regards, Christopher -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Friday, June 15, 2007 2:02 PM To: Maven Users List Subject: Re: Profiles yes you have to set the activ

RE: Profiles

Cheers, Jim -Original Message- From: Chris Helck [mailto:[EMAIL PROTECTED] Sent: Friday, June 15, 2007 1:59 PM To: Maven Users List Subject: RE: Profiles If you use activeByDefault then isn't the profile always active? I don't believe you can have a default profile that

RE: Profiles

al Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Friday, June 15, 2007 2:02 PM To: Maven Users List Subject: Re: Profiles yes you have to set the activeByDefault to true http://maven.apache.org/ref/2.0.4/maven-settings/settings.html#class_act ivation Arnaud On 15/06/07,

Re: Profiles

yes you have to set the activeByDefault to true http://maven.apache.org/ref/2.0.4/maven-settings/settings.html#class_activation Arnaud On 15/06/07, Jon Strayer <[EMAIL PROTECTED]> wrote: Is it possible to have a default profile that is activated only when no other profile is activated? -- Ess

Re: Profiles and inheritance

Hallo from what i've read in this list somewhere: profiles are not inherited to sub-modules. so the profile will not appear as activated. but nontheless the effects of a parent-pom profile are inherited to the child-modules. so es you should be able to define a profile in the parent pom and u

Re: Profiles, filtering resources and optional content

On 14/03/07, Piotr Bzdyl <[EMAIL PROTECTED]> wrote: Actually, I thought about this solution but unfortunately the common part of the conf.properties is so big that I would not like to keep it in two separate places and need to remember to change these common parts in two (or even more if I will n

Re: Profiles, filtering resources and optional content

An alternative to filtering the same resource is to split it into two and profile it. So you'd move src/main/resources/conf.properties to, say: * src/main/profiles/prod/resources/conf.properties * src/main/profiles/dev/resources/conf.properties Configure the profiles in your POM accordingly, an

Re: Profiles, filtering resources and optional content

Hi, Mark Hobson wrote: > > An alternative to filtering the same resource is to split it into two > and profile it. So you'd move src/main/resources/conf.properties to, > say: > > * src/main/profiles/prod/resources/conf.properties > * src/main/profiles/dev/resources/conf.properties > Actuall

Re: profiles / text substitution

You want to use profiles plus filters. This is certainly possible, and in fact rather simple with Maven2. Much more information on these topics is available in the Better Builds With Maven free e-book from www.mergere.com. Also this blog post should probably be helpful: http://sujitpal.blogspot.

Re: profiles / ear content . how to do this?

I did this on a previous project like this :- EAR pom.xml mygroup myartifact /myroot name ${myartifact.optional.war.excluded} then either in the parent pom.xml or in settings.xml you can define a property with a different setting per profile e.g.

Re: profiles / ear content . how to do this?

http://maven.apache.org/plugins/maven-ear-plugin/howto.html The ear plugin configuration to generate the application.xml can be different per profile. Eric On 9/18/06, Marco Mistroni <[EMAIL PROTECTED]> wrote: hi all, i have a usecase in which i have to deploy an ear.. if the .ear is set to

Re: Profiles for sub-projects

Why not use: However, this bit is not working: ${basedir}\plugin.xml /Henrik On 6/12/06, Boden, David <[EMAIL PROTECTED]> wrote: I've managed to track this down. The profiles work correctly. However, this bit is not working: plugin.xml It is not looking

RE: Profiles for sub-projects

I've managed to track this down. The profiles work correctly. However, this bit is not working: plugin.xml It is not looking for plugin.xml at ${basedir}/plugin.xml for each sub-project as I'd expect. Instead, for each subproject it's just evaluating the same multi-project-bas

Re: Profiles in pom.xml, settings.xml and profiles.xml

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Profiles are a little strange, in that there are two different types. The profiles specified in the POM are allowed to modify many, many things, but are specific to that POM. They are also inextricably linked to that POM, obviously. The profiles spec

Re: Profiles not working?

yes, but that is what the activation is for. Please file a JIRA issue for investigation. On 11/9/05, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Mvn -Pwindows should do it. > > -Original Message- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Mike Whittemore > Sent: Tuesday, November 08

RE: Profiles not working?

Mvn -Pwindows should do it. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Mike Whittemore Sent: Tuesday, November 08, 2005 3:48 PM To: users@maven.apache.org Subject: Profiles not working? We have all our source code in ClearCase on Unix, under the "vobs" directory