From d089343090d4e3d71d36103b51582133a21bf1a7 Mon Sep 17 00:00:00 2001 From: Michael Jones Date: Thu, 26 Jan 2017 16:36:50 -0500 Subject: [PATCH] readme update --- README.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 823a910..e2e3498 100644 --- a/README.md +++ b/README.md @@ -1,14 +1,16 @@ -# ember-cli-svn --------------------------------------------------- +ember-cli-svn +===================================== [![Build Status](https://travis-ci.org/mdeanjones/ember-cli-svn.svg?branch=master)](https://travis-ci.org/mdeanjones/ember-cli-svn) -Yes it is very old hat, but sometimes you just can't avoid Subversion. There are several tools that allow you to define -SVN dependencies in your package, which is great, but Ember-CLI only inspects `dependencies` and `devDependencies` for -addons that it should include in a build. This plugin aims to get around that by inspecting the parent application's -package, and masquerading any `svnDependencies` as its own `dependencies`. It's not perfect, but - generally speaking - -it seems to get the job done. +> Yes it is very old hat, but sometimes you just can't avoid Subversion. +_- Me, just now_ + +There are several tools that allow you to define SVN dependencies in your package, which is great, but Ember-CLI +only inspects `dependencies` and `devDependencies` for addons that it should include in a build. This plugin aims +to get around that by inspecting the parent application's package, and masquerading any `svnDependencies` as its +own `dependencies`. It's not perfect, but - generally speaking - it seems to get the job done. ## Installation