jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 1
  • MAVEN-37

Not honoring parents project.properties when inheriting projects.

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor 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.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Kevin Hagel added a comment - 06/Oct/03 8:56 AM

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.

Show
Kevin Hagel added a comment - 06/Oct/03 8:56 AM 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.
Hide
Permalink
Brent Hale added a comment - 07/Nov/03 11:29 AM

The suggestion for using the "<util:properties file="../project.properties" trim="true" />" above is helpful for the maven.xml file.

Is there a similar way to get around it for the project.xml file?

Show
Brent Hale added a comment - 07/Nov/03 11:29 AM The suggestion for using the "<util:properties file="../project.properties" trim="true" />" above is helpful for the maven.xml file. Is there a similar way to get around it for the project.xml file?
Hide
Permalink
Brett Porter added a comment - 24/Apr/04 7:16 PM

second oldest open bug
Fixed.

Show
Brett Porter added a comment - 24/Apr/04 7:16 PM second oldest open bug Fixed.

People

  • Assignee:
    Brett Porter
    Reporter:
    Jeff Brekke
Vote (11)
Watch (5)

Dates

  • Created:
    04/Aug/02 9:15 PM
    Updated:
    08/Mar/06 10:45 PM
    Resolved:
    24/Apr/04 7:16 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.