![Repository client
● Maven brought remote repository idea to mainstream
● Elements are identified by:
○ group id
○ artifact id
○ version
○ classifier
○ type (packaging)
Location: ${group id}/${artifact id}/${version}/${artifact id}-${version}[-${classifier}].${type}
● One project may have multiple repositories
● The central.maven.org is enabled by default
● You are free to define own repositories
○ in project descriptor
○ local or global maven settings](https://image.slidesharecdn.com/improveddeveloperproductivitythankstomavenandosgi-lukaszdywickicode-house-181116172822/85/Improved-developer-productivity-thanks-to-Maven-and-OSGi-Lukasz-Dywicki-Code-House-23-320.jpg)
![Pax URL
● By default Java runtime supports following URI schemes:
○ http[s]:
○ file:
● Java / OSGi framework allows to provide new schemes (ie. bundle:)
● Pax URL provides:
○ wrap:
○ classpath:
○ mvn:
○ and few more (exploded dir and similar)](https://image.slidesharecdn.com/improveddeveloperproductivitythankstomavenandosgi-lukaszdywickicode-house-181116172822/85/Improved-developer-productivity-thanks-to-Maven-and-OSGi-Lukasz-Dywicki-Code-House-45-320.jpg)
![Example test
@RunWith(PaxExam.class)
@ExamReactorStrategy(PerMethod.class)
public class ExampleIntegrationTest {
@Configuration public Option[] config() {
return options(junitBundles());
}
@Test …
}](https://image.slidesharecdn.com/improveddeveloperproductivitythankstomavenandosgi-lukaszdywickicode-house-181116172822/85/Improved-developer-productivity-thanks-to-Maven-and-OSGi-Lukasz-Dywicki-Code-House-56-320.jpg)
Improved developer productivity thanks to Maven and OSGi - Lukasz Dywicki (Code-House)
- 1. OSGi with Maven Improved developer productivity thanks to standard tools
- 2. Thank you! To correct me: luke | code-house.org twitter: @ldywicki code: https://github.com/Code-House/eclipsecon (under ASL 2.0)
- 3. Is it a perfect marriage?
- 4. Is it a perfect marriage?
- 5. Let's face the truth Source: https://twitter.com/vorburger/status/1044203455055892481
- 7. About me Self employed consultant since 2008, a middleware specialist. ● Open Source enthusiast since forever ● Apache Karaf ○ committer since 2010 ○ project management committee since 2012 ● I worked for Red Hat, FUSE Source, been involved in projects for Alcatel-Lucent, Nokia Siemens Networks, Polish Post Bank, Royal Bank of Scotland etc. ● Eclipse user since 2003 ● Maven user since 2006
- 8. Few words about world How does it look a like outhere
- 14. OSGi is not classified in runtimes ● Some of server runtimes can run OSGi ● OSGi can be run inside a WAR ● There are a lot of people who knows Maven, Tomcat, IntellIJ and Eclipse and development model promoted by these tools
- 15. Communication troubles Pay attention to what you say
- 16. There is a problem finding people knowing OSGi.
- 17. Closer look on Maven
- 18. Maven is ... ● build tool ○ compiler ○ test runner ○ packager ○ site generator But it is also ● Tool promoting convention over configuration ● Repository client ● A dependency manager ● A pluggable machina
- 19. a word about configuration ● Global $M2_HOME/conf/settings.xml ● Local, user settings ~/.m2/settings.xml ● Project pom.xml
- 20. a bit about inheritance ● Projects can be organised into a tree: ○ super pom (implicit) ■ organisation POM ● project A ○ child project 1 ○ child project 2 ● project B ○ first child ○ second child
- 21. what is inherited ● dependency management ● dependencies ● plugins ○ executions ○ configurations ● resources configuration
- 22. Convention over configuration ● You palce sources in src/ ○ code in main/java, resources in main/resources ○ tests in test/java ● Results end up in target/ ● There are standard build phases (pre-test, test, package etc.) ● Plugins are hooked into phases ● Depending on plugin developer, there are various defaults
- 23. Repository client ● Maven brought remote repository idea to mainstream ● Elements are identified by: ○ group id ○ artifact id ○ version ○ classifier ○ type (packaging) Location: ${group id}/${artifact id}/${version}/${artifact id}-${version}[-${classifier}].${type} ● One project may have multiple repositories ● The central.maven.org is enabled by default ● You are free to define own repositories ○ in project descriptor ○ local or global maven settings
- 24. Dependency manager ● Maven recognizes basic dependency scopes ○ compile ○ runtime ○ test (not transitive) ○ provided (not transitive) ● system / import scopes are special kind ● Dependencies can be managed / forced by parent and also overridden
- 26. What dependency management do
- 28. Pluggable machina ● Maven internally uses simple IoC based on classpath scanning ● Classpath can be extended via plugin dependencies & extensions ● There is whole new extension mechanism in 3.x (enabling polyglot maven) ● Almost all, if not all, components are injected via IoC ● … did I mention that maven supports version ranges?
- 29. Versions and ranges under Maven ● 2 becomes 2.0.0 when comparing ● Special values in qualifier: ○ "alpha" < "beta" < "milestone" < "cr" / "rc" < "snapshot" < "final" / "ga" < "sp" ● 2.0-Snapshot matches [1,2.0) boundary (excludes 2.0 release) ● Customisable via SPI: ○ Version Scheme ○ Version Range Resolver ○ OSGi compatible version: https://github.com/Code-House/maven-osgi-resolver
- 30. Commonalities
- 31. Comparison Element OSGi Maven Build unit Bundle Project / Module Dependency unit Package, req /cap Dependency Platform definition Target Platform (PDE) Dependency management Version ranges Yes Yes Repositories OBR, P2 Maven repos
- 33. Systems are like onions Source: http://www.downvids.net/shrek-moments-quot-ogres-are-like-onions-quot--317773.html, Shrek movie was made by DreamWorks
- 34. Each bigger system have ● Domain model ● Persistence ● Communication interface ● Many provider/consumer relationship between these parts
- 35. Properly structured project is easier to run and maintain.
- 36. Most of OSGi projects is properly structured.
- 37. Some Maven based projects have good structure.
- 38. Basic project structure ● root ○ model ○ api ○ core ○ dao ■ api ■ core ○ web ■ api ■ core ○ features
- 39. Manifest is just another resource
- 40. How to generate manifest <packaging>bundle</packaging> <!-- … --> <plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <configuration> <instructions> <Export-Package>org.code_house.eclipsecon.mvnosgi.api</Export-Package> <Private-Package>org.code_house.eclipsecon.mvnosgi.core</Private-Package> <Bundle-Activator>org.code_house.eclipsecon.mvnosgi.core.Activator</Bundle-Activator> </instructions> </configuration> </plugin>
- 41. bndlib ✔
- 42. Manifest defaults Bundle-SymbolicName: ${project.groupId}.${project.artifactId} Bundle-Version: ${project.version} Bundle-Name: ${project.name} Bundle-Description: ${project.description} Bundle-Vendor: ${project.organization.name} Bundle-License: ${project.license*.url} Import-Package: * Export-Package: * Private-Package: *.impl.*, *.internal.*
- 43. Deployment How to bring bundles to runtime
- 44. Quick look on Karaf
- 45. Pax URL ● By default Java runtime supports following URI schemes: ○ http[s]: ○ file: ● Java / OSGi framework allows to provide new schemes (ie. bundle:) ● Pax URL provides: ○ wrap: ○ classpath: ○ mvn: ○ and few more (exploded dir and similar)
- 46. Deploying bundles ● install mvn:org.code-house.eclipsecon.mvnosgi/api/RELEASE ● install mvn:org.code-house.eclipsecon.mvnosgi/core/RELEASE ● install mvn:org.code-house.eclipsecon.mvnosgi.dao/api/RELEASE ● install mvn:org.code-house.eclipsecon.mvnosgi.dao/core/RELEASE/jar ● install mvn:org.code-house.eclipsecon.mvnosgi.web/api/LATEST/x86_64/jar
- 47. Karaf feature <feature name="book-service" version="${project.version}"> <feature>scr</feature> <feature>cxf-jaxrs</feature> <feature>aries-blueprint</feature> <bundle>mvn:org.code-house.eclipsecon.mvnosgi/core/1.0.0-SNAPSHOT</bundle> <bundle>mvn:org.code-house.eclipsecon.mvnosgi/api/1.0.0-SNAPSHOT</bundle> <bundle>mvn:org.code-house.eclipsecon.mvnosgi/model/1.0.0-SNAPSHOT</bundle> <bundle>mvn:org.code-house.eclipsecon.mvnosgi.dao/api/1.0.0-SNAPSHOT</bundle> <bundle>mvn:org.code-house.eclipsecon.mvnosgi.dao/core/1.0.0-SNAPSHOT</bundle> <bundle>mvn:org.code-house.eclipsecon.mvnosgi.web/core/1.0.0-SNAPSHOT</bundle> <bundle>mvn:org.code-house.eclipsecon.mvnosgi.web/api/1.0.0-SNAPSHOT</bundle> <bundle>mvn:org.code-house.eclipsecon.mvnosgi/dto/1.0.0-SNAPSHOT</bundle> <!-- … rest of stuff ... --> </feature>
- 48. Testing How to bring bundles to runtime
- 49. OSGi -> junit -> test
- 50. junit -> OSGi -> test
- 51. Demo time
- 52. Arquillian
- 53. Pax Exam
- 54. Pax Tinybundles InputStream inp = bundle() .activator(TestActivator.class) .add(BookService.class) .add(TestBookService.class) .symbolicName("test-bundle") .set(Constants.EXPORT_PACKAGE, "demo") .set(Constants.IMPORT_PACKAGE, "demo") .build();
- 55. Exam containers ● OSGi ● Karaf ● Tomcat ● Weld ● JBoss / Wildfly 8 / Wildfly 9
- 56. Example test @RunWith(PaxExam.class) @ExamReactorStrategy(PerMethod.class) public class ExampleIntegrationTest { @Configuration public Option[] config() { return options(junitBundles()); } @Test … }
- 57. Unit testing - Felix Connect ● Emulates OSGi framework ○ Activators ○ Service lookups ○ Bundles and classloaders ● Perfect candidate for unit testing based on plain maven classpath
- 58. Felix Connect String bundleFilter = "(&(Bundle-SymbolicName=*)(!(Bundle-SymbolicName=org.osgi.*)))"; List<BundleDescriptor> descriptors = new ClasspathScanner().scanForBundles(bundleFilter, loader); // setup felix-connect to use our bundles Map<String, Object> config = new HashMap<>(); config.put(PojoServiceRegistryFactory.BUNDLE_DESCRIPTORS, bundles); PojoServiceRegistry reg = new PojoServiceRegistryFactoryImpl().newPojoServiceRegistry(config); BundleContext bundleContext = reg.getBundleContext();
- 59. JUnit 5
- 60. AssertJ // entry point for all assertThat methods and utility methods (e.g. entry) import static org.assertj.core.api.Assertions.*; // basic assertions assertThat(frodo.getName()).isEqualTo("Frodo"); assertThat(frodo).isNotEqualTo(sauron);
- 61. Questions
- 62. Thank you! To correct me: luke | code-house.org twitter: @ldywicki code: https://github.com/Code-House/eclipsecon (under ASL 2.0)