Add manifest entries in jar to make it a valid OSGi bundle about prettytime HOT 5 CLOSED

Hey! Thanks for this idea. Would you like to help set this up? I haven't done any work in OSGi, so I probably wouldn't be able to test it very well. Your help would be very appreciated!

from prettytime.

(A pull request adding this configuration to the POM would be awesome!)

from prettytime.

To you POM, add something like:

<plugins>
  <plugin>
    <groupId>org.apache.felix</groupId>
    <artifactId>maven-bundle-plugin</artifactId>
    <extensions>true</extensions>
    <configuration>
      <instructions>
        <Export-Package>org.foo.myproject.api</Export-Package>
        <Private-Package>org.foo.myproject.*</Private-Package>
      </instructions>
    </configuration>
  </plugin>
</plugins>

Where the export should contain all packages that your users will actually use (ie. import).
Private should contain all packages which are only for the lib's internal use.
Not sure if you need a version here, but if so, try 2.3.7 or the latest (2.5.3)

from prettytime.

I would also be interested to use prettytime in osgi environment.
I have created a pull request (#100) adding configuration to the POM in order to build prettytime with OSGI manifest

from prettytime.

(Merged PR)

from prettytime.