Re: Properties files in a WAR artifact...

Hi Nelz, Let me throw some ideas at you and take what you can. Here is what I do for all our internal projects: In the project's parent POM I have this: profile-db-postgresql org.postgresql.Driver someusername somepassword jdbc:postgresql://lo

Re: properties in settings.xml do not interpolate

Mark Proctor-4 wrote: > > > > > > default > > > > ... > > > > > I've used settings.xml interpolation with success. I'm curious about what maven thinks is the value for "activateByDefault" in the above. Is it true or false? My hunch is "false

Re: properties-files

It seems this will solve my problem if I find a way to pass the properties to a schemaexport-task run from the antrun-plugin. It is a quite simple: You could pass properties to ant target using ant's property task

Re: properties-files

Wayne Fay wrote: You are looking for Profiles in conjunction with Resource Filtering. Thanks for the tip. It seems this will solve my problem if I find a way to pass the properties to a schemaexport-task run from the antrun-plugin. -- Regards Erik ---

Re: properties-files

You are looking for Profiles in conjunction with Resource Filtering. Wayne On 2/19/07, Erik Drolshammer <[EMAIL PROTECTED]> wrote: Hi! I have a Maven-based project which utilize a couple of properties-files like hibernate.properties and log4j.properties. Because these are often modified by the

RE: Properties for pom.xml

des on my repository. > I only need to load them into the pom.xml so that it could see them, > Is there a way to do so? > Thanks again! > Zvi. > > -Original Message- > From: franz see [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 04, 2007 5:35 PM > To: u

RE: Properties for pom.xml

! Zvi. -Original Message- From: franz see [mailto:[EMAIL PROTECTED] Sent: Sunday, February 04, 2007 5:35 PM To: users@maven.apache.org Subject: Re: Properties for pom.xml Good day, Pardon, my answer was incomplete :-) You may want to use [1] to get the resource, and use [2] to declare

Re: Properties for pom.xml

Good day, Pardon, my answer was incomplete :-) You may want to use [1] to get the resource, and use [2] to declare that file as a filter file ( a file containing properties ). Cheers, Franz [1] http://maven.apache.org/plugins/maven-remote-resources-plugin/ [2] http://maven.apache.org/plugins/m

Re: Properties for pom.xml

Good day to you, Rahamin, You may want to take a look at [1]. Cheers, Franz [1] http://maven.apache.org/plugins/maven-remote-resources-plugin/ Rahamim, Zvi (Zvi) wrote: > > Hi, > Is there a way to tell my pom.xml to load properties from a property > file that resides in a remote repository?

Re: Properties file exclusion from a Jar in Maven2

http://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html On 12/8/06, Morgovsky, Alexander (US - Glen Mills) <[EMAIL PROTECTED]> wrote: I am trying to exclude abc.properties from being put into the /classes directory when a jar is created. I try to do it like this.

Re: Properties in profiles

Try creating two profiles, and set one to true. Don't set any properties in the main section of the pom. On 12/5/06, Laura Hinojosa <[EMAIL PROTECTED]> wrote: Hi all! I'm trying to create a pom for my project that has two different deployment environments, which are mutually exclusive, but I n

Re: Properties/Variables in pom?

Hi! AFAIK, this only works _within_ the POM itself (i.e. in the configuration section of plugins). I don´t know if it works for the file-filtering stuff. CU, Gunther Gareth Tilley schrieb: Hi All, Gunther Popp-2 wrote: - All (platform-specific) Environment variables (Just add the pref

Re: Properties/Variables in pom?

Hi All, Gunther Popp-2 wrote: > > - All (platform-specific) Environment variables (Just add the prefix > env. For example ${env.M2_HOME} returns the Maven2 installation path). > Has anyone actually been able to get this working? All of the filtering works fine for me, but the environment var

Re: Properties for artifact names?

Hi Owen, there are may ways to skin the cat - I would say give it a try ... :-) Cheers, Siegfried Goeschl Owen Jacobson wrote: Good morning. I need to put the correct filename for a given artifact into a file at build time. Are there properties usable for resource substitution that, given a

Re: properties in plugins vs. pom

dan tran wrote: > > when you are in pom.xml, ${someVar} means a reference of a variable under > root of the pom > Ah, so within the pom, the "project." prefix is optional. It looks like it is also optional when filtering resource files. But not when annotating plugins. That's still a little an

Re: properties in plugins vs. pom

I am wrong ;-) when you are in pom.xml, ${someVar} means a reference of a variable under root of the pom However, maven also aware of other key vars such as ${project}, ${settetings} etc. Therefore ${project.artifactId} and ${artifactId} are the same thing ${basedir} ${project.basedir}

Re: properties in plugins vs. pom

dan tran wrote: > > inconsistency i guess, I suggest to always start with ${project} > I'm surprised at the implication: different code handles variable replacement here vs. there. Inconsistencies like this can be maddening. Could I file this as a jira? Maybe I'll even supply a patch. :-)

Re: properties in plugins vs. pom

inconsistency i guess, I suggest to always start with ${project} -D On 10/12/06, pjungwir <[EMAIL PROTECTED]> wrote: Hello, I'm developing a plugin in maven 2.0.4. My plugin has a property annotated like this: /** * @parameter default-value="${artifactId}.exe" */ private File outfile;

Re: properties in assembly descriptor.xml?

Please make sure this issue is listed in JIRA, under: http://jira.codehaus.org/browse/MASSEMBLY and I'll try to take a look at it before the 2.2 release. I agree that this would be useful, though...fwiw. -john On 9/13/06, leonid_ilyevsky <[EMAIL PROTECTED]> wrote: I checked it today, does n

Re: properties in assembly descriptor.xml?

I checked it today, does not work. I can use properties in the same pom.xml file, but not in the assembly descriptor. What is the problem? dan tran wrote: > > yes, assembly descriptor supports interpolation. > > -D > > > On 6/20/06, Claus Myglegaard Vagner <[EMAIL PROTECTED]> wrote: >> >> Hi

Re: properties file valorization during integration

Yes, profiles with filters are the proper way to do this, generally. Wayne On 6/27/06, Sebastien Moreno <[EMAIL PROTECTED]> wrote: ok after good reading I see the potential issue in using profiles to put different filters file: ... src/test/filter

Re: properties file valorization during integration

ok after good reading I see the potential issue in using profiles to put different filters file: ... src/test/filters/dico.properties src/main/resources

Re: properties file valorization during integration

ok after good reading I see the potential issue in using profiles to put different filters file: ... src/test/filters/dico.properties src/main/resources

Re: properties file valorization during integration

Hi Wayne "filter resources during build" could be acceptable, but how notify the build to use a filter file for a specified environment? For example, in the pom we can write: ... src/test/filters/dico.properties src/main/resources

Re: properties file valorization during integration

Generally this is handled during the package phase with filters. I'm not aware of any existing plugins which would take an existing Maven artifact (out of local repo, I suppose) and change properties values for a specific environment. I'm assuming the existing "filter resources during build" stuf

Re: properties in assembly descriptor.xml?

yes, assembly descriptor supports interpolation. -D On 6/20/06, Claus Myglegaard Vagner <[EMAIL PROTECTED]> wrote: Hi, I have serveral assembly descriptor files. Is it possible to get properties (from pom,settings,filters) available in the assembly descriptor files? This would be useful fo

Re: properties in M2

To get properties in M2 try adding the properties tag in your POM : valuehere You can refer to the http://maven.apache.org/ref/2.0.3-SNAPSHOT/maven-model/maven.html#class_prerequisitesmodel Hope that helps, Javed On 5/16/06, anita kulshreshtha <[EMAIL PROTECTED]> wrote: Hi, Is it

RE: Properties/Variables in pom?

Hi Gunther, >-Original Message- >From: ext Gunther Popp [mailto:[EMAIL PROTECTED] >Take a look at the Getting Started Guide >(http://maven.apache.org/guides/getting-started/index.html), >section "How do I filter resource files?". It explains how to >reference the elements of the pom.

Re: Properties/Variables in pom?

Hi Andreas! Take a look at the Getting Started Guide (http://maven.apache.org/guides/getting-started/index.html), section "How do I filter resource files?". It explains how to reference the elements of the pom.xml/settings.xml using property-names. I´m currently working on a book that covers

Re: Properties/Variables in pom?

I'll explain a bit more... you see how the pom.xml is laid out, right? {$basedir}target/classes ${basedir}target/test-classes there is a super-pom which is the parent of all the pom.xml that users create, in that super pom a mess of these things are defined as the defaults for t

Re: Properties/Variables in pom?

Most of your pom's element can be referenced as ${project.x.y}, so ${project.build.directory} by default is path_to_your "target" dir. -D On 3/17/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > > Hi Dan, > > >-Original Message- > >From: ext dan tran [mailto:[EMAIL PROTECTED] > >

RE: Properties/Variables in pom?

Hi Dan, >-Original Message- >From: ext dan tran [mailto:[EMAIL PROTECTED] >Sent: 17 March, 2006 20:03 >You can use the pom itself, ie ${project.build.directory} > >-D Sorry, I don't understand, what you're trying to tell me :-) Can you please add one or two sentences :-) Is ${project.

RE: Properties/Variables in pom?

Hi Wayne, >-Original Message- >From: ext Wayne Fay [mailto:[EMAIL PROTECTED] >Sent: 17 March, 2006 20:06 >Short answer: not anywhere that I've seen. > >If you do some research and get a list, feel free to respond >back to the mailing list, update the Wiki/Confluence, etc. ok I'll come

Re: Properties/Variables in pom?

> Are the default properties documented at all somewhere? Short answer: not anywhere that I've seen. If you do some research and get a list, feel free to respond back to the mailing list, update the Wiki/Confluence, etc. Wayne

Re: Properties/Variables in pom?

You can use the pom itself, ie ${project.build.directory} -D On 3/17/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > > Hi, > > Are the default properties documented at all somewhere? > > _ ___ _ > //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com > `-` >

RE: Properties/Variables in pom?

Hi, Are the default properties documented at all somewhere? _ ___ _ //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com `-` Andreas Ebbert-Karroum    Software Design Engineer - Nokia Networks Services / Middleware    phone: +49-211-94123928, fax: +49-211-9

RE: properties on a windows platform

Denis Fuenzalida wrote on Friday, February 10, 2006 4:18 PM: > Always use forward slashes, even in windows, so you can avoid > misleading paths, such as: c:\this\other\some.properties -> the first > '\t' gets translated as a 'tab' character > > use "c:/this/other/some.properties" instead > > Se

Re: properties on a windows platform

Always use forward slashes, even in windows, so you can avoid misleading paths, such as: c:\this\other\some.properties -> the first '\t' gets translated as a 'tab' character use "c:/this/other/some.properties" instead See http://javaalmanac.com/egs/java.util/Props.html for examples. Greetings,

RE: properties on a windows platform

ER [mailto:[EMAIL PROTECTED] Sent: Thursday, February 09, 2006 6:22 PM To: Maven Users List Subject: Re: properties on a windows platform Did you tried with double-quotes : org.apache.jetspeed.server.home="F:/Platform/Apache Software Foundation/Tomcat 5.5/" Or you can try with

Re: properties on a windows platform

Did you tried with double-quotes : org.apache.jetspeed.server.home="F:/Platform/Apache Software Foundation/Tomcat 5.5/" Or you can try with the short name (8.3) org.apache.jetspeed.server.home=F:/Platform/Apache~1/Tomcat~1/ Arnaud On 2/10/06, Garner Andrews <[EMAIL PROTECTED]> wrote: > By the w

RE: properties on a windows platform

By the way, I have tried using backslashes, (e.g. F:/Platform/Apache\ Software\ Foundation/Tomcat\ 5.5/) and I still get the following error: 'F:\Platform\Apache' is not recognized as an internal or external command, operable program or batch file. Thanks again, Garner C. Garner Andrews Enter

Re: properties files

Try: ${build.sourceDirectory} **/*.properties ...and if you wanted to do the same thing for test-resources, you'd have an additional section of the form []+ in your build section. -john Kevin Galligan wrote: I know that we should use the resourc

Re: Properties in resource directory

it looks like a bug - it should be in the maven-project component. - Brett On 11/10/05, Nitko2 <[EMAIL PROTECTED]> wrote: > I have pom.xml with following snippet: > > > src\JavaSource > > > src\JavaSource > > > and it works. > If I use property like this > > > sr

Re: properties inheritance

Here it is full details abt this problem. I have a property which is using in all modules project.xml file which recognizes source directory. I have specified this at top level project.properties file. if i have given the property of ${basesrc} in project.properteis this is the out put.(i

Re: properties inheritance

Here it is full details abt this problem. I have a property which is using in all modules project.xml file which recognizes source directory. I have specified this at top level project.properties file. if i have given the property of ${basesrc} in project.properteis this is the out put.(i

Re: properties inheritance

that should work. I will verify that it is fixed in 1.0.2 which is being released today. - Brett On Mon, 6 Dec 2004 21:22:33 -0800 (PST), rajas kumar <[EMAIL PROTECTED]> wrote: > > i am using version 1.0. > Yaa i am extending other project.xml files also. > > > > Brett Porter <[EMAIL PROTE

Re: properties inheritance

i am using version 1.0. Yaa i am extending other project.xml files also. Brett Porter <[EMAIL PROTECTED]> wrote: what version of Maven are you using? When you say inherited, are you actually extending other project.xml files? - Brett On Mon, 6 Dec 2004 20:49:53 -0800 (PST), rajas kumar wrote

Re: properties inheritance

what version of Maven are you using? When you say inherited, are you actually extending other project.xml files? - Brett On Mon, 6 Dec 2004 20:49:53 -0800 (PST), rajas kumar <[EMAIL PROTECTED]> wrote: > Hai maven users, > >I am facing with a problem of properties in heritance. I have a ser

RE: Properties inheritance

It will work in RC3, I committed the fix this week. You should not be overriding maven.home.local in a project - that is a user preference and belongs in ~/build.properties. maven.repo.remote is a funny one - It is usually a site preference (has to be implemented as a user preference as there is

Re: Properties inheritance

Hi Carlos, "Carlos Sanchez" <[EMAIL PROTECTED]> writes: > You can set the property in the top level project' maven.xml so it's > inherited by the subprojects > > var="maven.repo.remote">http://www.ibiblio.org/maven,http://oness.sourceforg > e.net/maven Hmm, from my experience failed dependencie

RE: Properties inheritance

ato Massimiliano (TLAB) > [mailto:[EMAIL PROTECTED] > Enviado el: jueves, 29 de abril de 2004 16:58 > Para: Maven Users List > Asunto: RE: Properties inheritance > > I did what you suggested and to solve the remote repository > problem I had to update the default remote.repo

RE: Properties inheritance

I did what you suggested and to solve the remote repository problem I had to update the default remote.repo from ibibilio to mine, inside the maven.jar file -Original Message- From: Roland Huss [mailto:[EMAIL PROTECTED] Sent: Thursday, April 29, 2004 4:55 PM To: [EMAIL PROTECTED] Subject:

Re: properties and values in maven.xml

hmm. That command gives this output [Fatal Error] :1:1: Content is not allowed in prolog. BUILD FAILED File.. file:/homedir/robshep/projects/jbeast/maven.xml Element... j:parse Line.. 55 Column 61 Content is not allowed in prolog. Where is the best reference for maven.xml/jelly script

Re: properties and values in maven.xml

Maybe they are immutable?? JAT, Marco - Original Message - From: "Sri Sankaran" <[EMAIL PROTECTED]> To: "Maven Users List" <[EMAIL PROTECTED]> Sent: Tuesday, March 30, 2004 10:18 PM Subject: RE: properties and values in maven.xml Have you tried some

RE: properties and values in maven.xml

Have you tried something like Sri -Original Message- From: Rob Shepherd [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 1:36 PM To: Maven Users List Subject: properties and values in maven.xml I'm having trouble getting to grips with the scripting. I'm proficient at ant so i

Re: Properties scope between plugin

[EMAIL PROTECTED] wrote: When defining propert "a.b" in plugin aPlugin, then using the bPlugin, is it possible to access default properties defined in aPlugin (e.g. ${a.b})? I tried, and i faild. Is there a workaround? workaround for what ? what did you try ? something like this should work :

RE: Properties inheritence

Slated for 1.1. Please search the archives before posting. - Brett > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 3 December 2003 12:28 AM > To: [EMAIL PROTECTED] > Subject: Properties inheritence > > > How are the project.properties process

Re: Properties of dependencies

[EMAIL PROTECTED] wrote: Maven's properties are named after the plugin they are used by, e.g. war.bundle is used by the war plugin. 'module' and 'runtime' are not used by maven or it's plugins. At least by plugins kept in our CVS repository. mm

Re: Properties of dependencies

Maven's properties are named after the plugin they are used by, e.g. war.bundle is used by the war plugin. 'module' and 'runtime' are not used by maven or it's plugins. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Pub Key:http://blogs.codehaus.org/peopl

RE: properties

Jamie McCrindle <[EMAIL PROTECTED]> wrote on 26/09/2003 07:14:04 PM: > here's the problem: > > we have a main project (multiproject type project) and then a whole bunch of > component projects. normally, the directory structure should look something > like this: > > [parent] > --main > --a >

RE: properties

sedir=.. maven.multiproject.excludes=main/project.xml for the multiproject plugin, or -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 25 September 2003 23:40 > To: 'Maven Users List' > Subject: RE: properties > > > I'm not sure what you are tryin

RE: properties

I'm not sure what you are trying to achieve. ${basedir} should always be set to the executing project's directory. - Brett > -Original Message- > From: Jamie McCrindle [mailto:[EMAIL PROTECTED] > Sent: Thursday, 25 September 2003 7:29 PM > To: Maven Users List > Subject: properties > >

RE: properties in a dependency

> -Original Message- > From: Joe Germuska [mailto:[EMAIL PROTECTED] > > The docs for the War plugin explain that this is the way to indicate > that a dependency is copied into the webapp or war. See > Thank you!! I downloade

Re: properties in a dependency

The docs for the War plugin explain that this is the way to indicate that a dependency is copied into the webapp or war. See The XML in project.xml mostly just provides values for bean properties of an instance of org.apache.maven

<    1   2