Enhance the FeaturesScannerProvisionOption, so that it retrieves artifact
version from project
----------------------------------------------------------------------------------------------
Key: PAXEXAM-193
URL: http://issues.ops4j.org/browse/PAXEXAM-193
Project: Pax Exam
Issue Type: Improvement
Components: Core
Reporter: Bartosz Kowalewski
Assignee: Toni Menzel
It'd be nice not to be forced to specify the version of Maven artifact that
provides the XML feature repo descriptor. This version is now hidden inside the
string "mvn:" URL.
This artifact could be a Maven dependency of the test project, so it would be
possible to introduce a similar mechanism that is now used in Pax Exam for
maven bundles. The option that handles Karaf features could fetch artifact
version from a properties file - the same as the one that is used for maven
bundles.
Instead of doing:
scanFeatures( "mvn:org.apache.servicemix/apache-servicemix/4.0.0/xml/features",
"servicemix-file", "servicemix-http" )
we could call (I don't insist on using the names or signatures proposed below
:-)):
scanMavenFeatures( "org.apache.servicemix",
"apache-servicemix").versionAsInProject().feature("servicemix-file").feature("servicemix-http")
or
scanFeaturesFromMaven(...)
Of course, if one needs to explicitly specify the versions of particular
features to be retrieved from the given features repo XML than this enhancement
will not cause all versions hardcoded in the test class to go away.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
