OSGi support

[failsafe-lib]

OSGi support

[jhalterman]

I'm not an OSGi user, but I'd be happy to take a pull request for this so I don't mess it up :)

[jhalterman]

@eurotrip11 Have a look at the commit I just pushed and let me know how that looks. Here's the branch

https://github.com/jhalterman/failsafe/tree/osgi

[eurotrip11]

Sorry for delay :)
I show the commit, is ok, but the better solution is add this configuration on maven plugin

<plugin>
    <groupId>org.apache.felix</groupId>
    <artifactId>maven-bundle-plugin</artifactId>
    <version>3.0.1</version>
    <extensions>true</extensions>
    <executions>
        <execution>
            <id>bundle-manifest</id>
            <phase>process-classes</phase>
            <goals>
                <goal>manifest</goal>
            </goals>
        </execution>
    </executions>
    <configuration>
        <supportedProjectTypes>
            <supportedProjectType>jar</supportedProjectType>
            <supportedProjectType>bundle</supportedProjectType>
        </supportedProjectTypes>
        <instructions>
            <Implementation-Title>${project.description}</Implementation-Title>
            <Implementation-Version>${project.version}</Implementation-Version>
            <Bundle-Name>Failsafe</Bundle-Name>
            <Bundle-SymbolicName>net.jodah.failsafe</Bundle-SymbolicName>
            <Export-Package>net.jodah.failsafe*;version=1.0</Export-Package>
            <Import-Package>*</Import-Package>
        </instructions>
    </configuration>
</plugin>

and remove this tag on pom.xml <packaging>bundle</packaging> so no need to manage ad hoc branch for osgi.
Thanks Giuseppe

[jhalterman]

@eurotrip11 So I noticed that when removing the <packaging>bundle</packaging> and doing a mvn build, the generated MANIFEST.MF inside my jar does not contain any package export information. It simply contains:

Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Built-By: jonathan
Created-By: Apache Maven 3.1.1
Build-Jdk: 1.8.0_60

Does that seem right?

[eurotrip11]

@jhalterman Sorry :( i forgot this configuration :)

           <plugin>
                <artifactId>maven-jar-plugin</artifactId>
                <configuration>
                    <archive>
                        <manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
                    </archive>
                </configuration>
            </plugin> 

[jhalterman]

No worries. What's the benefit of this approach over <packaging>bundle</packaging>, which has been suggested in other projects?

[eurotrip11]

Greater support for the solutions not OSGi and not having to handle more than one branch for development. The solutions are identical to OSGi level does not change anything .

[jhalterman]

Thanks for the help on this @eurotrip11.