Maven 2.x Resources Plugin

Property substitution of ${project.build.directory} on Windows FAILS

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.3
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    Windows XP 32 bits
  • Number of attachments :
    1

Description

For a project target directory on C:\project\target, the maven build substitutes the project property $

{project.build.directory}

with c\:\\project
target. The c\:
should be c:

Issue Links

duplicates

Bug - A problem which impairs or prevents the functions of the product. MRESOURCES-81 2.3 escapes characters when filtering properties

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Benjamin Bentmann added a comment -

In which file exactly does this substitution happen? In the POM or in some resource file? Could you provide an example project to demonstrate this?

Show
Benjamin Bentmann added a comment - In which file exactly does this substitution happen? In the POM or in some resource file? Could you provide an example project to demonstrate this?
Hide
Permalink
Rodolfo Rothganger added a comment -

Also reproduced with 2.0.10. Works OK on 2.0.9.

Show
Rodolfo Rothganger added a comment - Also reproduced with 2.0.10. Works OK on 2.0.9.
Hide
Permalink
Rodolfo Rothganger added a comment - - edited

Benjamin,

The substitution occurs on a .xml resource file.

I´ve attached a sample project with a .xml resource file and a .xml test resource file on it.

regards,

Rodolfo

Show
Rodolfo Rothganger added a comment - - edited Benjamin, The substitution occurs on a .xml resource file. I´ve attached a sample project with a .xml resource file and a .xml test resource file on it. regards, Rodolfo
Hide
Permalink
Benjamin Bentmann added a comment -

This is a known issue in the maven-resources-plugin:2.3, downgrading to version 2.2 will get you back to a working build.

On this occasion, I strongly recommend to lock down the versions of all plugins employed in your build for the sake of reproducibility. A build like yours that exhibits different output depending on the Maven version is surely suboptimal.

Show
Benjamin Bentmann added a comment - This is a known issue in the maven-resources-plugin:2.3, downgrading to version 2.2 will get you back to a working build. On this occasion, I strongly recommend to lock down the versions of all plugins employed in your build for the sake of reproducibility. A build like yours that exhibits different output depending on the Maven version is surely suboptimal.
Hide
Permalink
Rodolfo Rothganger added a comment -

Benjamin,

Thanks on the feed back.

Regards,

Rodolfo

Show
Rodolfo Rothganger added a comment - Benjamin, Thanks on the feed back. Regards, Rodolfo

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Rodolfo Rothganger
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: