[#MAVEN-1501] maven seems not to evaluate .properties of parent pom

Maven 1

maven seems not to evaluate .properties of parent pom

Created: 12/Nov/04 10:49 AM Updated: 08/Mar/06 10:45 PM

Component/s:

core

Affects Version/s:

1.0.1

Fix Version/s:

1.0.2

Time Tracking:

Not Specified

Environment:

[][9.2.0](10)> maven -i
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.1

#---- BEGIN: Which report
Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
java.version=1.4.1_06
file.encoding=ISO646-US
java.ext.dirs=/usr/j2se/jre/lib/ext
java.class.path=/home/tminor/maven-1.0.1/lib/forehead-1.0-beta-5.jar
os.name=SunOS
java.vendor=Sun Microsystems Inc.
sun.boot.class.path=/home/tminor/maven-1.0.1/lib/endorsed/xerces-2.4.0.jar:/home/tminor/maven-1.0.1/lib/endorsed/xml-apis-1.0.b2.jar:/usr/j2se/jre/lib/rt.jar:/usr/j2se/jre/lib/i18n.jar:/usr/j2se/jre/lib/sunrsasign.jar:/usr/j2se/jre/lib/jsse.jar:/usr/j2se/jre/lib/jce.jar:/usr/j2se/jre/lib/charsets.jar:/usr/j2se/jre/classes
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
#---- END: Which report

Installed plugins:
  maven-abbot-plugin-1.1
  maven-announcement-plugin-1.3
  maven-ant-plugin-1.8.1
  maven-antlr-plugin-1.2.1
  maven-appserver-plugin-2.0
  maven-artifact-plugin-1.4.1
  maven-ashkelon-plugin-1.2
  maven-aspectj-plugin-3.2
  maven-aspectwerkz-plugin-1.2
  maven-caller-plugin-1.1
  maven-castor-plugin-1.2
  maven-changelog-plugin-1.7.1
  maven-changes-plugin-1.5.1
  maven-checkstyle-plugin-2.5
  maven-clean-plugin-1.3
  maven-clover-plugin-1.6
  maven-console-plugin-1.1
  maven-cruisecontrol-plugin-1.5
  maven-dashboard-plugin-1.5
  maven-developer-activity-plugin-1.5.1
  maven-dist-plugin-1.6.1
  maven-docbook-plugin-1.2
  maven-ear-plugin-1.5
  maven-eclipse-plugin-1.9
  maven-ejb-plugin-1.5
  maven-faq-plugin-1.4
  maven-file-activity-plugin-1.5.1
  maven-genapp-plugin-2.2
  maven-gump-plugin-1.4
  maven-hibernate-plugin-1.2
  maven-html2xdoc-plugin-1.3.1
  maven-idea-plugin-1.5
  maven-j2ee-plugin-1.5.1
  maven-jalopy-plugin-1.3.1
  maven-jar-plugin-1.6.1
  maven-java-plugin-1.4
  maven-javacc-plugin-1.1
  maven-javadoc-plugin-1.7
  maven-jboss-plugin-1.5
  maven-jbuilder-plugin-1.5
  maven-jcoverage-plugin-1.0.9
  maven-jdee-plugin-1.1
  maven-jdepend-plugin-1.5
  maven-jdeveloper-plugin-1.4
  maven-jdiff-plugin-1.4
  maven-jellydoc-plugin-1.3.1
  maven-jetty-plugin-1.1
  maven-jira-plugin-1.1.2
  maven-jnlp-plugin-1.4.1
  maven-junit-doclet-plugin-1.2
  maven-junit-report-plugin-1.5
  maven-jxr-plugin-1.4.2
  maven-latex-plugin-1.4.1
  maven-latka-plugin-1.4.1
  maven-license-plugin-1.2
  maven-linkcheck-plugin-1.3.3
  maven-multichanges-plugin-1.1
  maven-multiproject-plugin-1.3.1
  maven-native-plugin-1.1
  maven-nsis-plugin-1.1
  maven-pdf-plugin-2.2.1
  maven-plugin-plugin-1.5.2
  maven-pmd-plugin-1.6
  maven-pom-plugin-1.4.1
  maven-rar-plugin-1.0
  maven-release-plugin-1.4.1
  maven-repository-plugin-1.2
  maven-scm-plugin-1.4.1
  maven-shell-plugin-1.1
  maven-simian-plugin-1.4
  maven-site-plugin-1.5.2
  maven-struts-plugin-1.3
  maven-tasklist-plugin-2.3
  maven-test-plugin-1.6.2
  maven-tjdo-plugin-1.0.0
  maven-uberjar-plugin-1.2
  maven-vdoclet-plugin-1.2
  maven-war-plugin-1.6.1
  maven-webserver-plugin-2.0
  maven-wizard-plugin-1.1
  maven-xdoc-plugin-1.8
Home Build properties: {maven.build.dir=/home/tminor/maven/build/${pom.groupID}/${pom.artifactId}, build.view.path=/mms, maven.home.local=/home/tminor/maven/localhome}

Issue Links:

Duplicate

This issue is duplicated by:

~~MAVEN-1513~~ maven.username is not inherited properly

~~MAVEN-1509~~ Property "maven.home.local" doesn't get overriden

~~MAVEN-1519~~ Property maven.build.dir is no longer overridable in parent project

~~MAVEN-1523~~ NoSuchFieldError

Description

« Hide

My pop extends an other pom.
<extend>../../project-defaults.xml</extend>
In that directory, there exists a project.properties.

This property file defines a company local, remote repository.

maven.repo.remote= http://maven.<company-domain>/repo

Using maven 1.0, this repository is used.
When using 1.0.1, it is not used.

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Brett Porter added a comment - 12/Nov/04 05:28 PM

this is a regression resulting from fixing >1 level of inheritence. It only fails for build in properties (most importantly, maven.repo.remote).

[ Permalink | « Hide ]

Boris Boehlen added a comment - 16/Nov/04 11:06 AM

My project layout is as follows:

common-build
project.properties
project.xml
kernel-module
project.xml
extension-1
project.xml
extension-2
project.xml

The extensions of the kernel are developed independently and can thus not be stored under kernel-module. Each module has a project.xml which says:
<extend>${basedir}/../common-build/project.xml</extend>
The output of "maven -X" tells me that the project.properties are read but the values (like maven.username and maven.repo.remote) are not set.

For me this is not a minor bug, but a show stopper.

[ Permalink | « Hide ]

Boris Boehlen added a comment - 22/Nov/04 03:57 AM

Bug's priority should be set to critical as it is in the duplicated bug #1513.

[ Permalink | « Hide ]

Brett Porter added a comment - 22/Nov/04 05:20 AM

major is fairer.

We tend to drive priority by "fix for" version.

[ Permalink | « Hide ]

Carlos Sanchez added a comment - 27/Nov/04 06:19 PM

A workaround is passing the property in the command line, e.g.
maven -Dmaven.repo.remote=http://www.ibiblio.org/maven/,http://dist.codehaus.org/

This way it's available to subprojects

[ Permalink | « Hide ]

Brett Porter added a comment - 29/Nov/04 09:19 PM

From Dr Wes Munsil:
For me, adding this to my top-level project.properties file seemed to make everything happy again:

maven.property.inheritance=true

[ Permalink | « Hide ]

Boris Boehlen added a comment - 30/Nov/04 05:13 AM

The workaround suggested by Wes Munsil does not work for me. I tried to set "maven.property.inheritance=true" at the following places

Inherited "project.properties"
Project specific "project.properties"
Command line
None of them solved the issue.

[ Permalink | « Hide ]

Brett Porter added a comment - 02/Dec/04 09:24 PM

looking at the code made this fairly obvious what was going wrong. I have it fixed, and will commit this evening.