[SLING-876] maven-sling-plugin ignores targetPath on resource path checking

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Maven Sling Plugin 2.0.2, Maven Sling Plugin 2.0.4
• Fix Version/s: Maven Sling Plugin 2.0.4
• Component/s: Maven Plugins and Archetypes
• Assignee: Unassigned
• Reporter: Stefan Seifert
• Created: 28/Feb/09 18:57
• Updated: 11/May/09 23:44
• Resolved: 28/Mar/09 14:26

Description

the sling plugins configures and checks initial content path mappings in method AbstractBundleInstallMojo.configure.
this does work fine with maven default mapping.

but if the project pom defines a special resource mapping with target path like this:
<resources>
<!-- copy webapp resources to SLING-INF/content/apps/${project.name} -->
<resource>
<directory>src/main/webapp</directory>
<targetPath>SLING-INF/content/apps/${project.name}</targetPath>
<filtering>false</filtering>
</resource>
</resources>
this does not work any longer, because the target path is ignored and the wrong path is checked.

the patch attached solves the problem.

Issue Links

• is related to: SLING-963 maven-sling-plugin fix for targetPath without trailing slash