[ 
https://issues.apache.org/jira/browse/SLING-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309689#comment-16309689
 ] 

Oliver Lietz commented on SLING-7351:
-------------------------------------

[~kwin], patch looks good to me, but I suggest an even less invasive change:

{noformat}
                <plugin>
                    <groupId>org.apache.servicemix.tooling</groupId>
                    <artifactId>depends-maven-plugin</artifactId>
                    <version>1.4.0</version>
                    <configuration>
                        
<outputFile>${project.build.directory}/test-classes/META-INF/maven/dependencies.properties</outputFile>
                    </configuration>
                </plugin>
{noformat}

> Include the "dependencies.properties" file in the final JAR
> -----------------------------------------------------------
>
>                 Key: SLING-7351
>                 URL: https://issues.apache.org/jira/browse/SLING-7351
>             Project: Sling
>          Issue Type: Improvement
>          Components: General
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Parent 33
>
>
> With the upgrade of the maven-failsafe-plugin in SLING-7347 pax-exam based 
> tests do no longer work. The reason is 
> https://issues.apache.org/jira/browse/SUREFIRE-855 that makes 
> surefire/failsafe now use the generated JAR as classpath (instead of the 
> classes directory). By default the generated bundle does not include the 
> referenced {{META-INF/maven/dependencies.properties}} file though (although 
> it exists below {{target/classes}}).
> To make it easier to upgrade to the new sling-parent for modules leveraging 
> pax-exam without adding additional configuration the file 
> {{META-INF/maven/dependencies.properties}} should automatically included by 
> the {{maven-bundle-plugin}} in case that file exists.
> This has been discussed in 
> https://www.mail-archive.com/[email protected]/msg73340.html.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to