Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.0-beta-7
-
Fix Version/s: 1.0-rc3
-
Component/s: inheritance
-
Labels:None
-
Environment:java version "1.4.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)
Redhat 7.3 + errata
Description
When a project is inheiriting from a parent project, the parent's project project.properties file is not being read. Example:
Parent project.properties defines maven.repo.remote. When the child is built it will default to maven's default remote repo at jakarta.
My current favorite kludge around this to put the following right at the top of my maven.xml:
<util:properties file="../project.properties" trim="true" />
<util:properties file="../build.properties" trim="true" />
this is immediately after the opening <project ..> tag, before any goals are encountered. Yes, outside of any <goal>
Using jelly:util preserves the mavenesque last-set feature, while using the <ant:loadproperties srcFile="file.properties"/> sticks you with ant's first-set policy.