Maven 2 & 3

Use expression ${project.build.directory} instead of hard-coding "target" in super POM

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Trivial Trivial
  • Resolution: Fixed
  • Affects Version/s: 2.0.8
  • Fix Version/s: 2.1.0-M1
  • Component/s: POM
  • Labels:
    None
  • Patch Submitted:
    Yes
  • Number of attachments :
    1

Description

The super POM hard-codes several paths to "target/...". Re-using project.build.directory for those paths would ease customization.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brian Fox added a comment -

I thought exactly the same when I was working with the super-pom. It doesn't get interpolated correctly and breaks everything. I forget the exact error, but it failed horribly when I tried to use that version.

Show
Brian Fox added a comment - I thought exactly the same when I was working with the super-pom. It doesn't get interpolated correctly and breaks everything. I forget the exact error, but it failed horribly when I tried to use that version.
Hide
Permalink
John Casey added a comment -

I've just added this functionality, and all ITs and unit tests pass with it in place since the interpolation refactor.

Show
John Casey added a comment - I've just added this functionality, and all ITs and unit tests pass with it in place since the interpolation refactor.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.