[
https://issues.apache.org/jira/browse/FELIX-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-1735.
--------------------------------------
Resolution: Fixed
Implemented this change in Rev. 824244:
* the bundle jar file name is provided as the value of the
"project.bundle.file" system property
* if the system property is not set, the fixed name "target/scr.jar" is tried
* If the file is not present, an exception is thrown before trying to run the
tests
To run the integration tests in the console nothing special must be done. The
tests run in the integration-test phase which is automatically passed when
targetting the install phase.
To run the integration tests in your favourite IDE, build the bundle jar file
targetting the "package" phase and enabling the "ide" profile as in:
$ mvn -Pide clean package
Then run the integration tests from the IDE.
> Use system property to provide bundle jar file to integration tests
> -------------------------------------------------------------------
>
> Key: FELIX-1735
> URL: https://issues.apache.org/jira/browse/FELIX-1735
> Project: Felix
> Issue Type: Improvement
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.2.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.2.0
>
>
> Currently the integration tests depend on a hard coded file name for the
> bundle JAR file to tests. This file is created in the pre-integration-test by
> copying the actual bundle file to the file with the fixed name. It would
> probably be better to use a system property to set the name of the bundle jar
> file and interpret that in the integration tests.
> For ease of use in IDEs the fixed file name can be left as a fallback if the
> system property is not set. And the maven project provides a profile which
> copies the bundle file after creating it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
