Merge branch 'develop'

Author: tobiasstamann

.github/workflows/default.yml

@@ -12,8 +12,8 @@ jobs:
     runs-on: ${{ matrix.os }}
     strategy:
       matrix:
-        os: [ubuntu-latest,macos-latest]
-        java: [ 7, 7.0.181, 8, 8.0.192, 9.0.x, 10, 11.0.x, 11.0.3, 12 ]
+        os: [ ubuntu-latest,macos-latest ]
+        java: [ 8.0.x, 9.0.x, 11.0.x, 12.0.x, 13.0.x, 14.0.x, 15.0.x, 16.0.x, 17.0.x, 18.0.x ]
 
     steps:
       - uses: actions/checkout@v1

.github/workflows/jacoco.yml

@@ -35,7 +35,7 @@ jobs:
         run: ./mvnw verify jacoco:report-aggregate -B -q
 
       - name: Upload coverage to Codecov
-        uses: codecov/codecov-action@v1.0.2
+        uses: codecov/codecov-action@v2
         with:
           token: ${{secrets.CODECOV_TOKEN}}
-          file: target/site/jacoco-aggregate/jacoco.xml
+          files: target/site/jacoco-aggregate/jacoco.xml

README.md

@@ -7,15 +7,19 @@
 # Why you should use this project?
 
 If you want to use a service provider interface (_SPI_) you need to register your service implementation in the _/META-INF/services/<Full qualified spi interface name>_ file.
-Additionally you usually need to write a service locator to be able to use the service implementation.
+Additionally, you usually need to write a service locator to be able to use the service implementation.
 
 The annotation processor offered by this project provides exactly this. It allows you to create the service locator file just by adding an annotation to you spi implementation.
-Additionally it will generate a service locator for you.  
+Additionally, it will generate a service locator for you.
+
+# Prerequisites
+- The generated ServiceLocator code requires at least JDK 8.
 
 # Features
 Annotation processor that
 - provides support for generating service locator file in _/META-INF/services/<Full qualified spi interface name>_
 - provides support for generating service locator class for accessing the SPI implementations
+- compatible with Java >= 8 (Java 7 support up to version 0.8.2)
 
 # How does it work?
 
@@ -75,12 +79,13 @@ To create multiple service locators in the same package use @SpiServiceLocators:
 
     @SpiServiceLocators({
         @SpiServiceLocator(FirstExampleSpiInterface.class),
-        @SpiServiceLocator(SecondExampleSpiInterface.class),
+        @SpiServiceLocator(SecondExampleSpiInterface.class)
     })
     package your.target.package;
 
     import io.toolisticon.spiap.api.SpiServiceLocator;
-    import your.spi.package.ExampleSpiInterface;
+    import your.spi.package.FirstExampleSpiInterface;
+    import your.spi.package.SecondExampleSpiInterface;
 
 ## How to register a service implementation
 Just add a Service annotation to your service implementation:
@@ -96,7 +101,7 @@ Just add a Service annotation to your service implementation:
 Service annotations mandatory value must declare the SPI you want the service class to be registered to.
 All other annotation attributes are optional. 
 
-- id defines a custom id which can be used to locate a specific servics implementation via the generated service locator class. Defaults to fully qualified service class name in generated service locator.
+- id defines a custom id which can be used to locate a specific services implementation via the generated service locator class. Defaults to fully qualified service class name in generated service locator.
 - description declares a short description about the implementation
 - priority is used to define a specific order in which the services are located
 

api/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>io.toolisticon.spiap</groupId>
         <artifactId>spiap-parent</artifactId>
-        <version>0.8.2</version>
+        <version>0.9.0</version>
     </parent>
 
     <name>spiap-api</name>

example/api/pom.xml

@@ -8,7 +8,7 @@
     <parent>
         <groupId>io.toolisticon.spiap</groupId>
         <artifactId>example-parent</artifactId>
-        <version>0.8.2</version>
+        <version>0.9.0</version>
     </parent>
 
     <name>example-api</name>

example/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>io.toolisticon.spiap</groupId>
         <artifactId>spiap-parent</artifactId>
-        <version>0.8.2</version>
+        <version>0.9.0</version>
     </parent>
 
     <name>example-parent</name>

example/service/pom.xml

@@ -8,7 +8,7 @@
     <parent>
         <groupId>io.toolisticon.spiap</groupId>
         <artifactId>example-parent</artifactId>
-        <version>0.8.2</version>
+        <version>0.9.0</version>
     </parent>
 
     <name>example-service</name>

example/usage/pom.xml

@@ -8,7 +8,7 @@
     <parent>
         <groupId>io.toolisticon.spiap</groupId>
         <artifactId>example-parent</artifactId>
-        <version>0.8.2</version>
+        <version>0.9.0</version>
     </parent>
 
     <name>example-usage</name>

integrationTest/baseCode/pom.xml

@@ -8,7 +8,7 @@
     <parent>
         <groupId>io.toolisticon.spiap</groupId>
         <artifactId>integrationTest-parent</artifactId>
-        <version>0.8.2</version>
+        <version>0.9.0</version>
     </parent>
 
     <name>integrationTest-baseCode</name>

integrationTest/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>io.toolisticon.spiap</groupId>
         <artifactId>spiap-parent</artifactId>
-        <version>0.8.2</version>
+        <version>0.9.0</version>
     </parent>
 
     <name>integrationTest</name>