Permalink
Browse files

convert prototype plugin to use .pluginspec

  • Loading branch information...
cowboyd committed Sep 16, 2011
1 parent 594cc2a commit 577d7877571529df89e6f71000eb5a459be2f6d5
Showing with 10 additions and 12 deletions.
  1. +2 −2 Gemfile
  2. +0 −10 Rakefile
  3. +8 −0 ruby-prototype.pluginspec
View
@@ -2,11 +2,11 @@ source :rubygems
# Use this line instead if you want to bundle from a local copy.
# gem "jenkins-plugin-runtime", :path => "#{File.dirname(__FILE__)}/../jenkins-plugin-runtime"
-gem "jenkins-plugin-runtime", "~> 0.1.3"
+gem "jenkins-plugin-runtime", "~> 0.1.5"
gem "sinatra"
group :development do
# we need this patched version of bundler in order to generate valide .hpi file
- gem "jenkins-plugin", "~> 0.1.3"
+ gem "jenkins-plugin", "~> 0.1.5"
end
View
@@ -1,16 +1,6 @@
load "#{File.dirname(__FILE__)}/.rake" if File.exists? '.rake'
-# First, let's declare some metadata about the plugin that might be needed. These are properties
-# I just pulled out of the air. The point is, let's put everything as constants here, and then maybe we can
-# move all the metadata eventually into a `Pluginfile` or a `ruby-prototype.pluginspec` that can be eval'd
-# separately
-
-PluginName = 'ruby-prototype'
-PluginVersion = '0.1.0'
-PluginJenkinsVersion = ">= 1.410"
-PluginDeps = {"ruby-runtime" => "0.3"} # change this to -SNAPSHOT to co-develop this with ruby-runtime plugin
-
require 'jenkins/rake'
Jenkins::Rake.install_tasks
@@ -0,0 +1,8 @@
+
+Jenkins::Plugin::Specification.new do |plugin|
+ plugin.name = 'ruby-prototype'
+ plugin.version = '0.1.0'
+ plugin.description = 'a pure ruby playground for Jenkins plugins'
+
+ plugin.depends_on 'ruby-runtime', '0.3'
+end

0 comments on commit 577d787

Please sign in to comment.