Maven Shared Components

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: maven-filtering-1.0-beta-1
• Fix Version/s: maven-filtering-1.0-beta-2
• Component/s: maven-filtering
• Labels:

  None
• Environment:

  linux, windows

<targetPath> is always relative to target/classes, even if you pass it an absolute path. This happens if the path is from a variable, like this:

<targetPath>${basedir}/scripts</targetPath>

It also happens if you write the path directly:

<targetPath>/home/pjungwir/src/encc/scripts</targetPath>

or on windows:

<targetPath>C:/home/pjungwir/src/encc/scripts</targetPath>

Your resources wind up in directories like this:

/home/pjungwir/src/encc/target/classes/home/pjungwir/src/encc/scripts

1. 

   absolute-resource-outputs.patch

   25/Oct/06 4:58 PM

   0.7 kB

   Paul Jungwirth

• Assignee:

  Olivier Lamy

  Reporter:

  Paul Jungwirth

• Created:

  25/Oct/06 4:44 PM

  Updated:

  12/Sep/08 4:24 PM

  Resolved:

  12/Sep/08 4:24 PM