Hello,
I try to port an existing ANT based build system to Maven.
I set in my root POM (A) the org.codehaus.mojo:properties-maven-plugin
to read all required properties from an existing property file.
That works fine. But when I create a new Maven module (B) where I set
its parent to be A, it
. But when I create a new Maven module (B) where I set
its parent to be A, and this is a module of A, it complains that does
not find the property file.
Does exist the property inheritance in Maven?
Thoughts?
Graf László
Property inheritance works for properties you put into the properties
section of a parent pom.
The m-build-helper-p creates properties dynamically *after* maven already
executed pom parsing and property inheritance. I. e.: inheriting dynamic
properties does not work.
HTH
Ansgar
Am 07.02.2013 21
Am 07.02.2013 21:49 schrieb Ansgar Konermann
ansgar.konerm...@googlemail.com:
Property inheritance works for properties you put into the properties
section of a parent pom.
The m-build-helper-p
s/build-helper/properties/
creates properties dynamically *after* maven already executed pom
Please take a couple of minutes to read my answer to a very similar
question on stack overflow
http://stackoverflow.com/questions/14725197/reading-properties-file-from-pom-file-in-maven/14727072#14727072
It should hopefully make things a little clearer
-Stephen
On Thursday, 7 February 2013,
Hi all
I have a problem with the property inheritance in the maven site project.
I have a multi-module project. The base pom looks like this:
project
modelVersion4.0.0/modelVersion
groupIdmy.project/groupId
artifactIdall/artifactId
packagingpom/packaging
version${project.version
Hi,
${project.version} is an internal maven property, so it is absolutely
not a good idea to use it. So the first try should be to rename that one.
Stefan
Christian Kölle wrote:
Hi all
I have a problem with the property inheritance in the maven site project.
I have a multi-module project
VUB Stefan Seidel wrote:
${project.version} is an internal maven property, so it is absolutely
not a good idea to use it. So the first try should be to rename that one.
Hi
Obviously this was a bad example. In my real poms the variable has
another name. I changed that in the mail because i
] on 05/26/2004 05:08:56 PM
Please respond to Maven Users List [EMAIL PROTECTED]
To: 'Maven Users List' [EMAIL PROTECTED]
cc:(bcc: Winston Rast/Jeppesen/TMC)
Subject: RE: RC3 Property Inheritance Problem
Attachement is not there.
Can you post the contents of your message to JIRA and attach
Users List [EMAIL PROTECTED]
To: 'Maven Users List' [EMAIL PROTECTED]
cc:(bcc: Winston Rast/Jeppesen/TMC)
Subject: RE: RC3 Property Inheritance Problem
Do any of the plugins you use (eg the xdoclet one) override the values?
- Brett
-Original Message-
From: [EMAIL PROTECTED
I've been doing a lot of trial and error with this problem and I've narrowed it
down to what I think is a problem in multiproject environments with inherited
properties. It is *not* an issue strictly with the maven.compile.* properties as
I've previously mentioned. I'm attaching a jar file of my
Attachement is not there.
Can you post the contents of your message to JIRA and attach the example?
Thanks,
Brett
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, 27 May 2004 7:36 AM
To: [EMAIL PROTECTED]
Subject: Re: RC3 Property Inheritance
I'm trying to generate 1.4 friendly compiled classes. I'm getting failures on
the assert keyword. Here's a rundown of my multiproject structure:
root/
project.xml (extends root/service/project.xml)
project.ent
common/
maven/
project.properties
multiproject:install:
multiproject:projects-init:
[echo] Gathering project list
Starting the reactor...
snip
xdoclet:ejbdoclet:
java:prepare-filesystem:
java:compile:
[echo] maven.compile.source=1.3
[echo] maven.compile.target=1.1
So is the problem in the property inheritance, the java plugin
Do any of the plugins you use (eg the xdoclet one) override the values?
- Brett
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 26 May 2004 3:56 AM
To: Maven Users List
Subject: Re: RC3 Property Inheritance Problem
Just to follow up
Thanks - I wasn't aware of MAVEN_HOME_LOCAL.
-Original Message-
From: khote [mailto:[EMAIL PROTECTED]
Sent: 15 October 2003 13:04
To: Maven Users List
Subject: Re: Property inheritance
set a global
export MAVEN_HOME_LOCAL=/mavenrepository
or some such place. Put
-
From: Alastair Rodgers [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 3:46 AM
Subject: Property inheritance
Hello,
I've just started using Maven over the last couple of days, and I must
say, my first impressions are very positive (I'm used to dealing with lots
I know that property inheritance is a hot discussion, and I've been
following it intently over the months. I just had an idea though, that I'd
like to see what people think.
Since the multiproject plugin is the replacement for the reactor, couldn't
it be modified to load the inherited properties
On Tue, 2003-09-30 at 14:32, Sonnek, Ryan wrote:
I know that property inheritance is a hot discussion, and I've been
following it intently over the months. I just had an idea though, that I'd
like to see what people think.
Since the multiproject plugin is the replacement for the reactor
19 matches
Mail list logo