caterpillar 1.4.0 → 1.4.1

data/ChangeLog

@@ -1,3 +1,6 @@
+= 1.4.1
+	- small warning fix
+
 = 1.4.0
 	- create Liferay XML with REXML
 	- Caterpillar works outside of RAILS_ROOT

data/README.rdoc

@@ -15,20 +15,7 @@ For developers:
 
 
 = Quickstart
-== The new path
-You'll need at least the version 1.3.0.
-
-  $ gem install caterpillar-1.3.0.gem
-
-Start up a new Rails project:
-
-  $ caterpillar rails example
-
-It's all you need =].
-
-
-== The old way
-Rubygems is fixed, but the most recent stable release is 1.2.5.
+Install the Caterpillar gem from rubygems.org:
 
   $ gem install caterpillar
 

data/lib/caterpillar.rb

@@ -8,7 +8,7 @@
 #++
 
 module Caterpillar   
-  VERSION = '1.4.0'
+  VERSION = '1.4.1' unless defined? Caterpillar::VERSION
 end
 
 this_file = File.symlink?(__FILE__) ? File.readlink(__FILE__) : __FILE__

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: caterpillar
 version: !ruby/object:Gem::Version 
-  hash: 7
+  hash: 5
   prerelease: false
   segments: 
   - 1
   - 4
-  - 0
-  version: 1.4.0
+  - 1
+  version: 1.4.1
 platform: ruby
 authors: 
 - Mikael Lammentausta
@@ -78,7 +78,6 @@ files:
 - Rakefile
 - init.rb
 - install.rb
-- portlets-config.rb
 - lib/caterpillar/config.rb
 - lib/caterpillar/helpers/liferay.rb
 - lib/caterpillar/liferay.rb

data/portlets-config.rb

@@ -1,87 +0,0 @@
-# encoding: utf-8
-Caterpillar::Config.new do |portlet|
-
-  # JRUBY_HOME can be set here, unless the environment variable can be used.
-  # portlet.class::JRUBY_HOME = '/usr/local/jruby'
-
-  # The portlet container.
-  # By default only portlet.xml is created.
-  # Currently only Liferay is supported. You may optionally define the version.
-  portlet.container = Liferay
-  # portlet.container.version = '5.2.3'
-
-  # If you want to install the Rails-portlet JAR into the container, the container
-  # WEB-INF will be used.
-  #
-  # Since liferay-display-ext.xml does not exist, all portlets are categorized in
-  # liferay-display.xml. Caterpillar parses this file and appends Rails portlets.
-  #
-  # No changes are made to any of the files in this directory while making XML,
-  # only the deploy and install tasks make any changes.
-  # portlet.container.root = '/usr/local/liferay/tomcat/'
-
-  # The server that the container is running on.
-  # Possible values:
-  #  - 'Tomcat' (default)
-  #  - 'JBoss/Tomcat'
-  # portlet.container.server = 'JBoss/Tomcat'
-
-  # The server dir is only meaningful with JBoss.
-  # This is the name of the directory in server/.
-  # By default the first entry in the directory is chosen.
-  # portlet.container.server_dir = 'default'
-
-  # Allow to defining the deploy_dir - just the WAR file will be deployed under this directory.
-  # Since version 1.3.0
-  # portlet.container.deploy_dir = '/opt/myDeployDir'
-
-  # The hostname and port.
-  # By default the values are taken from the request.
-  portlet.host = 'http://0.0.0.0:3000'
- 
-  # If the Rails is running inside a servlet container such as Tomcat,
-  # you can define the servlet here.
-  # By default the servlet is the name of the Rails app.
-  # Without Warbler this should be an empty string.
-  portlet.servlet = ''
- 
-  # Portlet category. This is only available for Liferay.
-  # By default this is the same as the servlet.
-  # portlet.category = 'Example Rails app'
-
-  # Portlet instances.
-  #
-  # Each named route is mapped to a portlet.
-  #
-  # All keys except for 'name' are obligatory. If the name does not map to a route,
-  # you have to define the route here.
-  # You may override the host, servlet and category here.
-  # Most likely you will want to let ActionController::Routing to set the route.
-  #
-  # Available keys are:
-  #  - :name         -- named route
-  #  - :category     -- portlet category (Liferay only)
-  #  - :title        -- the title in portlet container's category (Liferay only)
-  #  - :edit_mode    -- enables edit mode for the portlet, adds <portlet-mode>edit</portlet-mode> to portlet-ext.xml
-  #                     Default value is false
-  #  - :instanceable -- enables instanceable for the portlet, add <instanceable>true</instanceable> to
-  #                     liferay-portlet-ext.xml. Default value is false
-  #  - :javascripts  -- portlet-specific javascripts that are included at
-  #                     the head of master HTML, such as body onload functions (Liferay only)
-  #  - :host         -- hostname:port of the deployment server
-  #  - :servlet      -- by default, the name of the Rails app (= name of the WAR package)
-  #  - :path         -- unless you're using named routes, you can define the path here
-
-  # Rails-portlet testing application.
-  # NOTE: this needs to be activated by 'map.caterpillar' in RAILS_ROOT/config/routes.rb
-  portlet.instances << {
-    :name     => 'portlet_test_bench',
-    :title    => 'Rails-portlet test bench',
-    :category => 'Caterpillar',
-    :path     => '/caterpillar/test_bench'
-  }
-
-  # this will include all named routes without further configuration
-  portlet.include_all_named_routes = true
-
-end