From 74aebb41b0c05220e90b13d46f55809db3ec74e8 Mon Sep 17 00:00:00 2001 From: Decebal Suiu Date: Fri, 5 Jun 2015 16:26:55 +0300 Subject: [PATCH] ready for travis-ci --- .travis.yml | 3 +++ README.md | 6 ++++-- 2 files changed, 7 insertions(+), 2 deletions(-) create mode 100644 .travis.yml diff --git a/.travis.yml b/.travis.yml new file mode 100644 index 0000000..af0e470 --- /dev/null +++ b/.travis.yml @@ -0,0 +1,3 @@ +language: java +jdk: + - oraclejdk7 diff --git a/README.md b/README.md index 2c37c86..044bb6a 100644 --- a/README.md +++ b/README.md @@ -1,12 +1,14 @@ Plugin Framework for Java (PF4J) ===================== + +[![Travis CI Build Status](https://travis-ci.org/decebals/pf4j.png)](https://travis-ci.org/decebals/pf4j) +[![Maven Central](http://img.shields.io/maven-central/v/ro.fortsoft.pf4j/pf4j.svg)](http://search.maven.org/#search|ga|1|pf4j) + A plugin is a way for a third party to extend the functionality of an application. A plugin implements extension points declared by application or other plugins. Also a plugin can define extension points. **NOTE:** Starting with version 0.9 you can define an extension directly in the application jar (you're not obligated to put the extension in a plugin - you can see this extension as a default/system extension). See [WhazzupGreeting](https://github.com/decebals/pf4j/blob/master/demo/app/src/main/java/ro/fortsoft/pf4j/demo/WhazzupGreeting.java) for a real example. -Current build status: [![Build Status](https://buildhive.cloudbees.com/job/decebals/job/pf4j/badge/icon)](https://buildhive.cloudbees.com/job/decebals/job/pf4j/) - Features/Benefits ------------------- With PF4J you can easily transform a monolithic java application in a modular application. -- 2.39.5