[ https://issues.apache.org/jira/browse/SLING-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert updated SLING-876: --------------------------------- Attachment: targetpath-patch.patch > maven-sling-plugin ignores targetPath on resource path checking > --------------------------------------------------------------- > > Key: SLING-876 > URL: https://issues.apache.org/jira/browse/SLING-876 > Project: Sling > Issue Type: Bug > Components: Maven Plugins > Affects Versions: Maven Sling Plugin 2.0.2, Maven Sling Plugin 2.0.4 > Reporter: Stefan Seifert > Fix For: Maven Sling Plugin 2.0.4 > > Attachments: targetpath-patch.patch > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.