Re: properties in maven-remote-resources-plugin

Solved. The remote project was packaging type pom. Perhaps a mention of this could be added to the documentation? Thanks, Delany On Fri, 9 Apr 2021 at 14:14, Delany wrote: > Hi. I'm able to use the maven-remote-resources-plugin when the source > project is included in the reactor, but not

Re: properties in maven-remote-resources-plugin

Hi. I'm able to use the maven-remote-resources-plugin when the source project is included in the reactor, but not when I'm just building the destination project. So for example `mvn clean install -pl :commondb,:credmanagementdb` yields [INFO] --- maven-remote-resources-plugin:1.7.0:bundle

Re: properties in maven-remote-resources-plugin

Ok, no images thank you. So I was barking up the wrong tree using the properties tag in the plugin. I still don't know what I did wrong, but it works now. Now there's another issue. If I bundle resources in a *descriptorgenerator* directory, the process goal will create an empty

Re: properties in maven-remote-resources-plugin

please try to write: 1.12 in you pom.xml = it defines a custom property with the value you want this will permit "dbs:commondb:${dep.dbs.commondb}" to get the value replaced Notice that images are removed, then we don't understand what you're trying to show Regards, Hervé Le

Re: properties in maven-remote-resources-plugin

I didn't want to give you all the context, because that complicates the problem which I carefully worded in the initial email: "I don't want to hardcode the version number of the remote project into this plugin config, so I've used a property made available in a parent pom." The fact that I

Re: properties in maven-remote-resources-plugin

I’m honestly unclear on your precise scenario. 1. If you are expecting a dependency to have a pom with a variable in it, that then you would specify before using it, then Maven doesn’t work that way. (And if you think about it, it creates a chicken-egg problem.) 2. If you are expecting to use

Re: properties in maven-remote-resources-plugin

Thanks I know how to use properties, but this plugin doesn't, it seems. It has some special way of importing them: https://maven.apache.org/plugins/maven-remote-resources-plugin/process-mojo.html [image: image.png] It can do this org.test:shared-resources:${project.version} But this is the

Re: properties in maven-remote-resources-plugin

The tag is documented here: https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#properties > On Feb 23, 2021, at 3:34 AM, Delany wrote: > > I don't want to hardcode the version

Re: properties in maven-remote-resources-plugin

Well I gave it my best shot maven-remote-resources-plugin process-remote-resources process dbs:commondb:${bully} 3

Re: Properties Files

Converting projects to Maven is not always a direct process. You might want to check out the document below. It talks about a systematic approach to converting projects to Maven, based on the artifacts that are created.

Re: Properties Files

What is their purpose now if you are not using Ant? If these are properties for the build, they should be inside the parent POM as properties. Ron On 18/08/2015 10:02 AM, aalok singhvi wrote: It's a migration of an ant project. It's java project. Presently ant gets build properties file on

Re: Properties Files

It's a migration of an ant project. It's java project. Presently ant gets build properties file on compile time. On Aug 18, 2015 9:56 AM, Ron Wheeler rwhee...@artifact-software.com wrote: What are you building? What language and technology stack? What are the properties files used for -

Re: Properties Files

Hi, For build time use, the simplest way is to put directly properties in pom.xml (parent or childs depending on how/where it is used). See https://maven.apache.org/guides/introduction/introduction-to-the-pom.html , last part. If you have lots of them it could eventually be externalized with

Re: Properties Files

What are you building? What language and technology stack? What are the properties files used for - run-time? If so, where do you want them to end up when you install your app? How are you installing it? Ron On 18/08/2015 7:02 AM, aalok singhvi wrote: Hello, I have a properties files. I

Re: properties that are not being resolved

The File vs String types note is the relevant part IIRC... It's not just file vs string though On Tuesday, 25 March 2014, Henrik Østerlund Gram henrik.g...@gmail.com wrote: Thanks for the link. It was quite informative, but I'm again a little confused because it is stated in your explanation,

Re: properties that are not being resolved

Hi, Out of curiosity, why don't you use the seemingly equivalent mojo buildnumber maven plugin? May not be your issue, but may be the plugin you're using doesn't create properties in the right way (no offense, just trying to guess)? My 2 cents Le 23 mars 2014 22:37, Henrik Østerlund Gram

Re: properties that are not being resolved

The one at http://mojo.codehaus.org/buildnumber-maven-plugin/create-mojo.html ? It states in the first couple of lines that it only works with subversion and I'm using git. Aside from that, I can't really see why it would make a difference; how many ways are there to set properties? I did

Re: properties that are not being resolved

It doesn't matter which plugin you use to set the property. What does matter is when the property substitution takes place. It normally happens in the very beginning of the Maven build when the pom is read, before the build lifecycle is executed and way before your plugin is executed. So you need

Re: properties that are not being resolved

Ok, I see. Any chance of such a change making it into the official ear-plugin? I think it would be generally useful to be able to reference properties in the env-entry values. Could post a pull request if desired, but judging by the months old ones at

Re: properties that are not being resolved

Hi Henrik, FYI, my projects use buildnumber-maven-plugin with git and it works great. Probably the docs are just out of date. Regards, Curtis On Mar 24, 2014 3:05 AM, Henrik Østerlund Gram henrik.g...@gmail.com wrote: The one at

Re: properties that are not being resolved

Hi, Hi Henrik, FYI, my projects use buildnumber-maven-plugin with git and it works great. Probably the docs are just out of date. That looks like. I have created the following JIRA ticket for this. https://jira.codehaus.org/browse/MBUILDNUM-119 If you have supplementals/infos etc. don't

Re: properties that are not being resolved

Please read my answer to a similar question on Stack Overflow: http://stackoverflow.com/questions/14725197/reading-properties-file-from-pom-file-in-maven/14727072#14727072 On 23 March 2014 21:36, Henrik Østerlund Gram henrik.g...@gmail.com wrote: I stumbled over some rather strange behaviour

Re: properties that are not being resolved

Thanks for the link. It was quite informative, but I'm again a little confused because it is stated in your explanation, the configuration sections will have mojo-injected properties evaluated, but that isn't the case in my example. I was trying to have such properties evaluated in a envEntries

Re: Properties within source code

Hi Nick, I think you missed the filtering part. I are supposed to enable the filtering by filerteringtrue/filtering See http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html As you can see there, it also possible to put you variables in a separate properties file. Hopes it

Re: Properties within source code

I know that this may not address your question directly, but I suggest that you change your approach. Rather than build two different artifacts for debugging or not debugging, I suggest that you make the a runtime configuration. Look into various logging frameworks (log4j, log back) that will

Re: Properties within source code

There is support for generating source code from some form of template. Usually requires a plugin for the template engine, or antrun and build-helper:add-source You would keep the template outside if src/main/java and then the generated source goes to something like target/generated-source/...

RE: Properties within source code

List Subject: Re: Properties within source code I know that this may not address your question directly, but I suggest that you change your approach. Rather than build two different artifacts for debugging or not debugging, I suggest that you make the a runtime configuration. Look into various

Re: Properties file exlusion from dependency

Is this possible? If so, how can I do it? Please spell out what you are thinking for those of us who are unable to interpret what you are asking about. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For

Re: Properties file exlusion from dependency

On Tue, Aug 14, 2012 at 8:53 AM, Wright, Omari omari.wri...@solers.comwrote: Is this possible? If so, how can I do it? You might be asking: I depend on an artifact. It has a properties file in it that gets read or is otherwise present on the classpath. This interferes with my system. I

Re: properties not getting shared

Ok, a bit more clarity - the child build that fails has a dependency on another child which has a dependency on something with ${foo.version}. Once that dependency is attempted to be resolved transitively, the property is NOT expanded to the -D value, but simply whatever was set in the top level

Re: Properties in settings.xml does not work for system scoped dependencies

the correct scope for those deps should be provided imho. the problem you have is getting the deps you need, system scope is just a workaround. ideally you would create an uberjar from the geologic jar and just install that into your repo manager. the focus should be on taking a jar and making

RE: Properties in settings.xml does not work for system scoped dependencies

of the provide jars should they not? /James -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: 15 November 2011 08:26 To: Maven Users List Subject: Re: Properties in settings.xml does not work for system scoped dependencies the correct scope for those deps

Re: Properties in settings.xml does not work for system scoped dependencies

-Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: 15 November 2011 08:26 To: Maven Users List Subject: Re: Properties in settings.xml does not work for system scoped dependencies the correct scope for those deps should be provided imho. the problem you

Re: Properties in settings.xml does not work for system scoped dependencies

Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: 15 November 2011 08:26 To: Maven Users List Subject: Re: Properties in settings.xml does not work for system scoped dependencies the correct scope for those deps should be provided imho. the problem you have is getting the deps you need

Re: Properties in settings.xml does not work for system scoped dependencies

Hi there, I've been a maven user since the early 1.0 days and have contributed patches at various times for the ejb-plugin, ear-plugin and others. I've also had the unfortunate experience of having to use WebLogic 10+ to create useable maven poms for our projects. In fact, when I read the OP I

Re: Properties in settings.xml does not work for system scoped dependencies

No possible licensing restriction can prevent you from having your own shared repository with nexus or archiva or artifactory and pushing whatever you want to it. For that matter, it's not too hard to write a script that calls install:install-file on each of a pile of jar files. You can't do this

Re: Properties in settings.xml does not work for system scoped dependencies

Last time I went through this I never came all the way to a complete list but I do remember there were lots of jars missing. I guess I'll have to reiterate this again since system scope doesn't seem to be supported anymore. /Bengt 2011/11/12 Wayne Fay wayne...@gmail.com What else do you need?

Re: Properties in settings.xml does not work for system scoped dependencies

System scoped dependencies are dead. Ignore their zombie like walking about. Stop fighting maven and just install the jars into a repo On 11 November 2011 16:02, Bengt Rodehav be...@rodehav.com wrote: We are using maven 3.0.3 and have problems using property values defined in our local

Re: Properties in settings.xml does not work for system scoped dependencies

System scoped dependencies are dead. Ignore their zombie like walking about. Stop fighting maven and just install the jars into a repo I agree, but shouldn't we kill system entirely at some point (I mean in the code) -- if we see a system-scoped dependency, we just fail the build with an

Re: Properties in settings.xml does not work for system scoped dependencies

On 11 November 2011 16:31, Wayne Fay wayne...@gmail.com wrote: System scoped dependencies are dead. Ignore their zombie like walking about. Stop fighting maven and just install the jars into a repo I agree, but shouldn't we kill system entirely at some point (I mean in the code) -- if we see

Re: Properties in settings.xml does not work for system scoped dependencies

Stephen and Wayne, I agree that using system scope is undesirable. However, there is a reason why maven has had this support - it is needed in real life. In my case, I use Weblogic. When first trying to migrate our old ant based build system to maven, I started out by trying to put the Weblogic

Re: Properties in settings.xml does not work for system scoped dependencies

Does this no longer work? http://docs.oracle.com/cd/E12840_01/wls/docs103/client/t3.html On Nov 11, 2011 3:38 PM, Bengt Rodehav be...@rodehav.com wrote: Stephen and Wayne, I agree that using system scope is undesirable. However, there is a reason why maven has had this support - it is

Re: Properties in settings.xml does not work for system scoped dependencies

It works but the full client is not enough for us to be able to build our application. Den 11 nov 2011 23:11 skrev Ryan Connolly ryn...@gmail.com: Does this no longer work? http://docs.oracle.com/cd/E12840_01/wls/docs103/client/t3.html On Nov 11, 2011 3:38 PM, Bengt Rodehav be...@rodehav.com

Re: Properties in settings.xml does not work for system scoped dependencies

What else do you need? Why not full client + some reasonable (small) handful of other dependencies? Wayne On Fri, Nov 11, 2011 at 5:00 PM, Bengt Rodehav be...@rodehav.com wrote: It works but the full client is not enough for us to be able to build our application. Den 11 nov 2011 23:11 skrev

Re: Properties in the archetype

Doesn't anybody have an idea? On 06.11.2010 19:09, Asmann, Roland wrote: Hi all, I'm having some problems with properties in archetypes. I read that it is possible to have files and directories renamed with properties (http://jira.codehaus.org/browse/ARCHETYPE-191), but this seems to be

Re: Properties in the archetype

I tried using this some time ago and remember this cannot be used for generic properties, only for groupId (if I remember correctly). The archetype plugin has some limitations at the moment. I hope this can be improved soon. Joachim On 11/18/2010 12:36 PM, Asmann, Roland wrote: Doesn't

Re: properties inheritance does not work on windows os

On Thu, 11 Nov 2010 14:34:05 +0100 chemit che...@codelutin.com wrote: Hi guys, I was testing some of my mojo on windows platform (xp) and how surprised I was to see there is some big problems. I had some [ERROR] 'dependencies.dependency.version' for

Re: properties inheritance does not work on windows os

that mold. -Original Message- From: chemit [mailto:che...@codelutin.com] Sent: Thursday, November 11, 2010 9:42 AM To: users@maven.apache.org Subject: Re: properties inheritance does not work on windows os On Thu, 11 Nov 2010 08:27:24 -0600 Yanko, Curtis curt_ya...@uhc.com

RE: properties inheritance does not work on windows os

?? -Original Message- From: Vincent Latombe [mailto:vincent.lato...@gmail.com] Sent: Friday, November 12, 2010 7:56 AM To: Maven Users List Subject: Re: properties inheritance does not work on windows os I think what Benjamin meant is : please provide an sample project

Re: RE: properties inheritance does not work on windows os

Users List Subject: Re: properties inheritance does not work on windows os I think what Benjamin meant is : please provide an sample project to reproduce your problem. Vincent 2010/11/11 Yanko, Curtis curt_ya...@uhc.com Very odd indeed, we use properties quite pervasively and I haven't

RE: properties inheritance does not work on windows os

obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Subject: RE: properties inheritance does not work on windows os Date: Fri, 12 Nov 2010 06:58:40 -0600 From: curt_ya...@uhc.com To: users

Re: properties inheritance does not work on windows os

On Fri, 12 Nov 2010 09:19:33 -0500 Martin Gainty mgai...@hotmail.com wrote: I will make reproductible small project to show the problem. I just try to test on windows but for my part it does not block me since I do not use windows; it was just to test if it works for people which like to use our

Re: properties inheritance does not work on windows os

On Thu, 11 Nov 2010 14:34:05 +0100 chemit che...@codelutin.com wrote: Hi guys, I was testing some of my mojo on windows platform (xp) and how surprised I was to see there is some big problems. I had some [ERROR] 'dependencies.dependency.version' for

Re: properties inheritance does not work on windows os

chemit wrote: Is those problem are known? I did not see anything about this on the list, which means one thing to me : windows users does not use maven (this was my troll sorry ;)). Hope something will be done soon about it ;) http://www.chiark.greenend.org.uk/~sgtatham/bugs.html Benjamin

RE: properties inheritance does not work on windows os

- From: Benjamin Bentmann [mailto:benjamin.bentm...@udo.edu] Sent: Thursday, November 11, 2010 9:18 AM To: Maven Users List Subject: Re: properties inheritance does not work on windows os chemit wrote: Is those problem are known? I did not see anything about this on the list

Re: properties inheritance does not work on windows os

On Thu, 11 Nov 2010 15:17:48 +0100 Benjamin Bentmann benjamin.bentm...@udo.edu wrote: chemit wrote: Is those problem are known? I did not see anything about this on the list, which means one thing to me : windows users does not use maven (this was my troll sorry ;)). Hope something

RE: properties inheritance does not work on windows os

Is this only on Maven 3.0? We haven't crossed that bridge yet. -Original Message- From: chemit Hi guys, I was testing some of my mojo on windows platform (xp) and how surprised I was to see there is some big problems. I had some [ERROR]

Re: properties inheritance does not work on windows os

To: Maven Users List Subject: Re: properties inheritance does not work on windows os chemit wrote: Is those problem are known? I did not see anything about this on the list, which means one thing to me : windows users does not use maven (this was my troll sorry ;)). Hope

Re: properties inheritance does not work on windows os

On Thu, 11 Nov 2010 08:27:24 -0600 Yanko, Curtis curt_ya...@uhc.com wrote: Is this only on Maven 3.0? We haven't crossed that bridge yet. Good point, I have just try with version 2.2.1 and result is the same. I really don't understand why this works on linux but not under windows, there is

RE: properties inheritance does not work on windows os

@maven.apache.org Subject: Re: properties inheritance does not work on windows os On Thu, 11 Nov 2010 08:24:45 -0600 Yanko, Curtis curt_ya...@uhc.com wrote: We use Windows in some places and I have never run into this and yes, we use lots of properties and inheritance. The problem seems

RE: properties inheritance does not work on windows os

@maven.apache.org Subject: Re: properties inheritance does not work on windows os On Thu, 11 Nov 2010 08:27:24 -0600 Yanko, Curtis curt_ya...@uhc.com wrote: Is this only on Maven 3.0? We haven't crossed that bridge yet. Good point, I have just try with version 2.2.1 and result is the same. I

Re: properties in assembly plugin

Stefano Nichele-2 wrote: Hi All, in my assembly file I have several fileSets sections and some of them are used to copy some files under PATH/lib , others PATH/bin, others in PATH/licenses. My issue is the I'd like to have PATH configured just in one place and not replicated in all

Re: properties in assembly plugin

Thanks and sorry it was easy ... ste On 03/03/2010 12.59, Andreas M wrote: Stefano Nichele-2 wrote: Hi All, in my assembly file I have several fileSets sections and some of them are used to copy some files underPATH/lib , othersPATH/bin, others inPATH/licenses. My issue is the I'd

Re: properties in settings.xml

Hello, Yes, it is. I've found that putting the real path in the pom.xml works fine, but I can't use a variable as the path. The problem I have with putting it in the pom makes the pom very specific rather then the settings.xml. I'm open for other suggestions on how to accomplish the

RE: properties in settings.xml

l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Sat, 14 Nov 2009 09:20:29 -0500 Subject: Re: properties

Re: properties in settings.xml

Hello, I'd rather not have to modify Maven for this. I'm also not looking for regular expressions, but rather just interpolation of the variables defined by other profiles. I guess the problem is the order in which the profiles are defined? Is there a way to set a variable without using

Re: properties in settings.xml

James Russo wrote: Hello, Yes, it is. I've found that putting the real path in the pom.xml works fine, but I can't use a variable as the path. The problem I have with putting it in the pom makes the pom very specific rather then the settings.xml. I'm open for other suggestions on how

Re: properties in settings.xml

Activate the nsis profile in your settings.xml and use the same profile id (without an activation element) in your POM. Perfect. I'm going to go this route. -jr

Re: Properties file in Maven

No, not in core Maven. However, I found this plugin: http://haroon.sis.utoronto.ca/zarar/properties-maven-plugin/ However, if you want to use properties in resource files the resource plugin can handle external files when doing the filtering:

Re: properties references

Out of a logical (design) perspective that sounds weird. The parent shouldn't have any dependency on the siblings; it's the other way around. Are you talking about a parent project or an aggregating project? /Anders On Tue, Sep 15, 2009 at 10:39, Valentin Jacquemin jacquem...@gmail.comwrote:

Re: properties references

Here is my structure: pom | ejb | |- pom |web |- pom In parent pom i use the glassfish plugin to deploy each artifact produced (ejb, web). In the glassfish plugin i have to specify each component to deploy and I wanted to fetch the build directory,

Re: properties references

What you have is an aggregating pom, which happens to be the parent pom as well (I guess). Why not create a separate project that does the deployment? It should have dependencies on the artifacts that you want to deploy. You shouldn't configure the glassfish deploy plugin to use a build/target

Re: properties references

Or is it some kind of feature for developers to easily get it deployed? No no it's only a personal prototype that i am creating on my own... I am not really accustomed to maven yet. Creating a separate project for the deployment could be the way for me. Thanks! Valentin Jacquemin On Tue, Sep

Re: properties references

I created a pom dedicated for the deployment and declared dependencies on my ejb/web projects but now how can I reference the artifact in the repository from glassfish-plugin elements? I am a beginner sorry... Valentin Jacquemin On Tue, Sep 15, 2009 at 11:15 AM, Valentin Jacquemin

Re: properties references

I'm not familiar with the glassfish plugin. Eitehr the plugin has built in support for using an artifact dependency or you have to use the dependency plugin to first fetch the (jar) artifact and then point the glassfish plugin to use that jar. dependency plugin goal:

Re: Properties conditional on phase?

tell us a bit more about *why* you think you need to do this and we might be able to point you towards tge maven way Sent from my [rhymes with myPod] ;-) On 24 Jul 2009, at 18:17, Mark H. Wood mw...@iupui.edu wrote: I want to have a property defined only during certain phases -- I want to

Re: properties vs pluginManagement

Hi Jim, Jim Sellers wrote at Donnerstag, 14. Mai 2009 22:37: Hi all. I've got a question for how to best configure plugins in a corporate parent pom. One way is to configure the plug in the pluginManagement section, the other is to use the properties that the plugin uses. eg. build

RE: properties vs pluginManagement

-Original Message- From: Jim Sellers [mailto:jim.sell...@gmail.com] Sent: Thursday, May 14, 2009 1:38 PM To: Maven Users List Subject: properties vs pluginManagement Hi all. I've got a question for how to best configure plugins in a corporate parent pom. One way is to configure the

RE: Properties: backslashes in pathname on Windows

ant's ${file.separator} ?? -Original Message- From: stug23 [mailto:pat.poden...@gmail.com] Sent: Thursday, April 23, 2009 8:56 PM To: users@maven.apache.org Subject: Properties: backslashes in pathname on Windows Is there a way in Maven 2.0.9 to end up with forward slashes in a

Re: Properties: backslashes in pathname on Windows

I found a Maven plugin at Google that can replace tokens which I applied to the filtered xml file. This does remove the backslashes, however I think a much better solution would be for Maven to have a simple and direct means of obtaining a file:URL with correct form via a Maven project property.

Re: Properties files proper location

Markos Fragkakis wrote: Hi, I am having some problems that I expected to be common, however I could not find a solution online for either. I want create a maven project for a swing application. My IDE is Eclipse. In order to run, the application needs to read a a couple of text

Re: Properties files proper location

Hello Markos, Maybe you could place fail-safe-params.properties with default settings within jar, thus within src/main/resources, and support them to be overridden by user using external params.properties file. Regards, Stevo. On Sat, Apr 18, 2009 at 2:52 PM, Markos Fragkakis

Re: Properties files proper location

My take on this is that there is no 'standard' by the book so-to-speak maven way of doing this. The standard thing in maven is to create one artifact per project so its standard to include files, etc in jar but not to externalize them. But that doesn't solve your problem. However, like you

Re: properties substitution problem in pom

I got it to work by being less aggressive about using property placeholders; now the dependencyManagement dependencies use a specific groupId and artifactId. Likewise for the dependency section in the cars-download pom. But I'm still confused about why it wasn't working. It seems like it's

Re: properties in archetypes?

[EMAIL PROTECTED] wrote on 18/06/2008 16:50:05: Can we make use of our own properties/variables in archetypes? The m2eclipse plugin allows us to define properties to be used at arcetype generation time. The problem is, I've not see a single references as to _how_ to do this!??? For

Re: Properties.

Remove all your neurons first and then use: mvn invest:property :D (sorry)

Re: Properties files exclude from jar artifact

Sure assembly will unpack properites in conf dir. But in my assembly, i would like to define a dependency to this module So finally, i will have my jar artifact with my properties files embded (for eg in a lib dir) and my properties files in conf dir (double) Wayne Fay wrote: Use

Re: Properties files exclude from jar artifact

So if i package properties file into my jars, how can I create finally an assembly which create a deploy/conf dir with all properties from jar. We put all properties into this dir because it is easiest to patch it. Wayne Fay wrote: No such all classifier exists. You must specify each

Re: Properties files exclude from jar artifact

Use dependencies plugin to unpack the properties files into your current module so they will be packaged by assembly into the conf dir you require. Wayne On 11/9/07, Saloucious [EMAIL PROTECTED] wrote: So if i package properties file into my jars, how can I create finally an assembly which

Re: Properties files exclude from jar artifact

No such all classifier exists. You must specify each dependency. Wayne On 11/6/07, Saloucious [EMAIL PROTECTED] wrote: Ok, but is it possible to get jar artifact and properties artifact in one dependency decalaration: For example, I deploy module1 with jar artifact and properties artifact

Re: Properties files exclude from jar artifact

Ok, but is it possible to get jar artifact and properties artifact in one dependency decalaration: For example, I deploy module1 with jar artifact and properties artifact and in a module2, i declare a dependency with module1 Is Maven able to retrieve 2 artifacts (for example with a

Re: Properties files exclude from jar artifact

You could make another artifact (jar) that consists only of properties files that are jar'ed together and deploy it into your repo. Wayne On 10/26/07, Saloucious [EMAIL PROTECTED] wrote: Hi, Acutally, i'm working on a migration from Ant to Maven. The old Ant script creates for each project

Re: properties in settings.xml

Huang, Yan [EMAIL PROTECTED] writes: Hi, I noticed that the install phase does not resolve the properties that are defined in settings.xml. For example, I use a property in my settings.xml to define the release version: profile idDefaultProfile/id activation

Re: properties in settings.xml

why would you specify your version outside of source control... you will no consistency acros difference machines/developers? On Wednesday 12 September 2007 19:04, Huang, Yan wrote: Hi, I noticed that the install phase does not resolve the properties that are defined in settings.xml. For

RE: Re: properties in settings.xml

Will the deploy phase actually resolve this version property? Or I have to go through maven release plug-in? -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Insitu Sent: Wednesday, September 12, 2007 12:13 AM To: users@maven.apache.org Subject: Re: properties

Re: properties

On 8/10/07, John Coleman [EMAIL PROTECTED] wrote: Hi, How do I return the value of the active profiles id as a property in my pom.xml. Add a property to each profile with a specific property name (eg: Profile 'dev': properties active.profiledev/active.profile /properties Profile

Re: properties injection issue

h, I run mvn using the '-Pprofilename' method for activating my profiles. This way I can build several version of the same code base on the same set of pom files. I only need to specify a different profile. When I do 'mvn -Pprofilename help:effective-pom' I get a successful build and all

Re: properties injection issue

Stupid question but is the profile activated? What is the result of: 'mvn help:active-profiles' and 'mvn help:effective-pom'? In the output of 'mvn help:effective-pom' your properties should be replaced with the version number. Cheers, michael Aaron Morand schrieb: Good day all, I am

Re: Properties files in a WAR artifact...

OK... First off, thank you Alexander for the suggestions. Secondly, I realized what I was trying to do... I am trying to pass in run-time configuration, and just like any consumer of my artifact, I need to send in configuration. So, I created a /src/test/config directory. In that directory I

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: profiles profile idprofile-db-postgresql/id properties jdbc.driverClassNameorg.postgresql.Driver/jdbc.driverClassName

  1   2   >