pepijnve-ivy4r 0.12.11

data/.autotest

@@ -0,0 +1,14 @@
+require 'rubygems'
+Bundler.require(:default, :development)
+
+# see https://github.com/rspec/rspec/wiki/autotest
+
+Autotest.add_hook(:initialize) {|at|
+  at.add_exception %r{^\.git}  # ignore Version Control System
+  at.add_exception %r{^./tmp}  # ignore temp files, lest autotest will run again, and again...
+  at.clear_mappings            # take out the default (test/test*rb)
+  at.add_mapping(%r{^lib/.*\.rb$}) {|f, _|
+    Dir['spec*/**/*.rb']
+  }
+  nil
+}

data/.gitignore

@@ -0,0 +1,7 @@
+.bundle
+doc
+*~
+nbproject
+pkg
+Gemfile.lock
+ivy4r-*.gem

data/.project

@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>ivy4r</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+		<buildCommand>
+			<name>org.rubypeople.rdt.core.rubybuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+	</buildSpec>
+	<natures>
+		<nature>org.rubypeople.rdt.core.rubynature</nature>
+	</natures>
+</projectDescription>

data/.rspec

@@ -0,0 +1,2 @@
+--format nested
+--color

data/CHANGELOG

@@ -0,0 +1,280 @@
+=== 0.12.11 / 2014-11-21
+  * Fix compatibility with MRI Ruby 2.x+
+  * Buildr: Use doc instead of javadoc to silence deprecation warnings
+
+=== 0.12.10 / 2011-01-21
+  * Default folder for settings file changed to '@extension_dir/iyvsettings.xml'
+  * Default ivy.home property is left empty to use default '${user.home}/.ivy2'
+
+=== 0.12.9 / 2011-01-17
+  * Added missing 'install' target, use it as defined in Ivy documentation
+
+=== 0.12.8 / 2011-01-14
+  * Converted all tests to RSpec2 specs and grouped them according to functional and normal spec
+  * Started adding more specs to get a descent test coverage
+  * Fixed regression error on Ivy status for buildr, now the proc is used if given
+
+=== 0.12.7 / 2011-01-06
+  * Fixed error in manifest: module was organisation name.
+  * info task uses the same ivy config as the other ivy tasks
+
+=== 0.12.6 / 2010-10-20
+  * Fixed copy & paste error
+
+=== 0.12.5 / 2010-10-20
+  * Fixed typo preventing compile to work properly
+
+=== 0.12.4 / 2010-10-19
+  * Fixed next problem regarding removal of "facets/blank": must be able to handle Regexps and Strings so needed to check both for beeing blank
+
+=== 0.12.3 / 2010-10-19
+  * Missed to fix the rake extension: Removed use of "facets/blank" using now "empty?" did not find the use when removing the require
+
+=== 0.12.2 / 2010-10-19
+  * Removed use of "facets/blank" using now "empty?" did not find the use when removing the require
+  * Add fix for error while merging additional infos into manifest files. Some jars, ears or wars do not have a manifest no just do nothing.
+
+=== 0.12.1 / 2010-10-13
+  * Use [project target dir]/pom.xml as default name for generated POM files.
+  * Works with MRI and JRuby
+  * remove unused and old import of 'facets/blank' that does not exists in new facets gem anymore
+
+=== 0.12.0 / 2010-10-12
+  * Use new version of ivy4r-jars. The new version is based on the last release of Ivy 2.2.0 with better support for POMs and a few bugfixes.
+  * Added global and per project Buildr task ivy:makepom. It generates a simple Maven POM file in target folder of project with the same name as project and pom file extension. Right now no additional features of the makepom target are supported by using this task. If you need to use the nested elements use the the makepom target directly. I.e.: ivy.ivy4r.makepom :ivyfile => 'pathtofile' [, ...] [, :nested => [:mapping => [:conf => 'conf', :scope => 'scope']], [...] ] I am planning to provide a makepom task with descent support for the makepom target after figuring out a nice syntax for it.
+
+=== 0.11.1 / 2010-06-09
+  * Fixed a bug reported by Rhett Sutphin that prevented the use of MRI.
+  * Added mapping from java to ruby via RJB and source example from
+    Stanford Parser Ruby Wrapper by William Patrick McNeill.
+  
+=== 0.11.0 / 2010-05-31
+  * Fixed a few bugs and issues reported by Rhett Sutphin. See issues on github 3-6.
+  * Ivy4r should work with MRI and JRuby, previously only JRuby was supported.
+  * The multi ivy.xml file support should work now. 
+
+=== 0.10.5 / 2010-04-26
+  * Fix a bug where artifacts for sub-projects have not been copied correctly to the publish directory
+    defined for ivy.
+
+=== 0.10.4 / 2010-04-22
+  * Changes to from version 0.9.14 working preventing a circular dependency error. Buildr.projects
+    is not used anymore but the ivy.publish task works as expected. See 0.9.14 for more details.
+
+=== 0.10.3 / 2010-03-30
+  * gem yank did not work so needed a new version :(
+
+=== 0.10.2 / 2010-03-30
+  * Fixed nil access exception for undefined user settings of type 'ivy'
+
+=== 0.10.1 / 2010-03-30
+  * Some fixes for the rake ivy result caching.
+  * Renamed the targets from ivy:enableresultcache, ivy:disableresultcache and ivy:cleanresultcache
+    into ivy:enable_result_cache, ivy:disable_result_cache and ivy:clean_result_cache for better
+    readability
+
+=== 0.10.0 / 2010-03-30
+
+* Add caching support to ivy4r. Ivy4r has now an optional parameter to a caching directory where it
+  stores results from calls to the tasks for each parameter set. If caching is enabled and a call
+  with the same parameters is done the cached result is used instead of executing the task again. This
+  should speed up local development because long running tasks like "ivy:resolve" are cached.
+  Caching can be enabled in buildr with:
+  * add this to your build.yaml or the [home]/.buildr/settings.yaml:
+  	ivy:
+  		caching.enabled: true
+  * add a marker file to your project under the path project.path_to('use_ivy_caching') Note that this is
+    a marker file only the existence of the file is checked not the content!! If the file exists caching
+    will be used!
+
+=== 0.9.15 / 2010-03-20
+
+* Revert changes from 0.9.14 because the fix does not work in all environments. Use the old code again
+  till a fix is found that circumvents the circular dependency issue and keeps the functionality of the tasks.
+
+=== 0.9.14 / 2010-03-14
+
+* Do not use Buildr.projects because of a circular dependency issue with the new buildr thanks to
+  Pepijn Van Eeckhoudt: He has bumped into an issue in the ivy4r buildr extension that triggers
+  circular dependency exceptions. The culprit is the call to Buildr.projects in add_copy_tasks_for_publish.
+  This can cause a call to project.invoke on the project being defined itself. He has checked with the
+  buildr devs and they told me that Buildr.projects should probably not be called from before/after
+  define callbacks.
+
+=== 0.9.13 / 2010-02-16
+
+* Fix problems with Facets and ActiveSupport. We now only include the required core extensions,
+  not all of them.
+
+=== 0.9.12 / 2010-01-21
+
+* Fix the problem with creation of packages where the additional ivy information has not been added
+  if "package :file 'x.type'" was used instead of "package :type".
+
+=== 0.9.11 / 2009-12-22
+
+* Fix of the ivy:clean target to clean the ivy cache via the cleancache task.
+
+=== 0.9.10 / 2009-12-21
+
+* Better support for Rake targets using the deps mechanism from buildr support.
+
+=== 0.9.9 / 2009-12-10
+
+* Fixed setting of ant properties, properties are really sets and cannot be overwritten afterwards.
+
+=== 0.9.7 / 2009-12-10
+
+* Fixed missing files in gem.
+
+=== 0.9.6 / 2009-12-09
+
+* Support for JRuby access to underlying java objects of ivy. Require 'ivy4r_java_extensions'
+  instead of 'ivy4r'. The Ivy4r#ivy_instance returns a new ivy instance configured with the same
+  settings file as used in the underlying ant process. Note that configuration via URL is not
+  supported.
+
+=== 0.9.5 / 2009-12-01
+
+* Bugfix for manifest handling in packages. The custom set manifest informations are not lost,
+  ivy informations for manifest are merged into the configured manifest.
+
+=== 0.9.4 / 2009-12-01
+
+* ivy.deps for buildr supports three argument types:
+    1. if an Hash is given :conf is used for confs and :type is used for types
+    2. if exactly two arrays are given args[0] is used for confs and args[1] is used for types
+    3. if not exactly two arrays all args are used as confs
+
+=== 0.9.3 / 2009-11-18
+
+* Sorting of compile and test dependencies to prevent problems with old jars that are added by
+  buildr automatically, i.e. log4j-1.2.9 for cobertura or JUnit 4.4 if tests are using a newer version.
+  The sort order:
+  1. all project dependencies as classes, resources and this like in the order the are contained in path
+  2. all ivy dependencies
+  3. all dependencies added by buildr to the targets
+* Deleted 'to_ivy_file' functionality because it was not working as expected. The function used the
+  wrong ivy context and was not able to resolve all variables within the file from the correct ivy context.
+
+=== 0.9.2 / 2009-11-16
+
+* Added new method to generate an ivy file from a resolved module descriptor, via the java
+  method ModuleDescriptor.toIvyFile(java.io.File). This is only working in jruby, because
+  the method is not called via Antwrap!
+* Added support for buildr configuration to call 'to_ivy_file' to generate ivy file from resolved
+  module descriptor, i.e. using 'ivy.to_ivy_file :file => 'output.file', :overwrite => true'
+
+=== 0.9.1 / 2009-11-16
+
+* Fixed bug that 'type' was not working for EAR
+
+=== 0.9.0 / 2009-11-16
+
+* Add a new configuration option for compile, test and package with name 'type'. The type can
+  be used as defined in ivy to only get artifacts of given type(s). One or more types can be
+  set as an array to this option. If no type is given all artifacts are retrieved.
+
+=== 0.8.1 / 2009-11-12
+
+* the project version is NOT set anymore by the the 'before_define' of the extension. The reason
+  for this are problems with ivy files that contain external references (i.e. include within the conf
+  block). The info task used for this needs more configuration information to work properly so this
+  feature is removed and the user must do it herself.
+   * In our projects we just moved the defintion to a different extension that configures more stuff
+     before setting the version and group:
+     before_define do |project|
+          if project.parent.nil? && project.ivy.enabled?
+            # do more configuration here prior setting the versions
+            info = project.ivy.info
+            project.version = info['ivy.revision']
+            project.group = "#{info['ivy.organisation']}.#{info['ivy.module']}"
+          end
+        end
+    * As an alternative you can set the group and version manually in the build file as it is usally done
+      in buildr.
+
+=== 0.8.0 / 2009-10-19
+
+* Moved to gemcutter for hosting of gems 'gem install gemcutter' add it as primary location and you
+  can install gems as before
+
+=== 0.7.3 / 2009-09-15
+
+* Renamed +ant+ to +ivy4r+ in buildr extension to make more clear what this object does. It is accesible
+  via call to +project.ivy.ivy4r+, use it in post_resolve or other places where the low level
+  ivy functions are needed in any way.
+* Added access to buildr_extension to get the configured mappings for artifacts to ivy publish names.
+  I.e. configured +ivy.publish package(:jar) => 'name.jar'
+  access this hash via +ivy.publish_mappings+
+
+=== 0.7.2 / 2009-09-08
+
+* Fix bug for creating EARs. The package dependencies are added into the root directory
+  of the EAR.
+
+=== 0.7.1 / 2009-08-24
+
+* Fix bug that manual added dependencies are overwritten for package task
+  issue 1: http://github.com/klaas1979/ivy4r/issues#issue/1
+* possible to add manual dependencies for compile and test as for package
+
+=== 0.7.0 / 2009-07-20
+
+* It is possible to register +post_resolve+ actions via blocks:
+  ivy.post_resolve {...}
+* support for generic configuration syntax via +method_missing+:
+  Any method combination of TARGETS [:compile, :test, :package] and TYPES [:conf, :include, :exclude] is valid.
+  It is possible to set all confs at once:
+  +ivy.conf :compile => 'conf', :package => 'other', :test => ['still', 'other']
+  Or to set the complete package options:
+  +ivy.package :conf => 'prod', :include => /includepattern/, :exclude => /excludepattern/+
+  Or to set a specific value via a complete call like:
+  +ivy.compile_conf [...] or ivy.conf_test [...] or ivy.package.include [...]
+* more include/exclude possibilities, support to include and exclude for compile and test targets using
+  +ivy.include :compile => [pattern list]+ or +ivy.exclude+
+* small refactorings
+
+=== 0.6.0 / 2009-07-08
+
+* added support for the +ide+ targets +eclipse+, +idea+ and +idea7x+
+* gem needs +facets+
+
+=== 0.5.3 / 2009-06-24
+
+* bugfixes
+
+=== 0.5.2 / 2009-06-24
+
+* bugfixes
+
+=== 0.5.1 / 2009-06-24
+
+* small improvements in rakefile (execute test for some targets)
+* publish to rubyforge "hamburg.rb"
+
+=== 0.5.0 / 2009-06-23
+
+* use ivy4r-jars to get needed jars from to separate the ruby source from the dependencies
+  and make the gem smaller.
+
+=== 0.4.0 / 2009-06-23
+
+* added rake/ivy_extension similar to buildr/ivy_extension to help use ivy4r in rake
+
+=== 0.3.0 / 2009-06-20
+
+* added ant*.jar to gem so that user does not need to have a local ant installation
+
+=== 0.2.0 / 2009-06-18
+
+* added the Buildr ivy_extension to include ivy in buildr for dependency managment
+* small improvements in documentation
+
+
+=== 0.1.0 / 2009-06-17
+
+* initial release
+  * support for nearly all basic IVY Ant targets
+  * basic validation of parameters
+

data/Gemfile

@@ -0,0 +1,5 @@
+source 'https://rubygems.org'
+
+# All in gemspec
+gemspec
+

data/README.txt

@@ -0,0 +1,124 @@
+= ivy4r
+
+* http://github.com/pepijnve/ivy4r/tree/master
+
+== DESCRIPTION:
+
+Apache Ivy dependency manager wrapper for ruby (see {Apache Ivy}[http://ant.apache.org/ivy/index.html] for more information).
+Use {Apache Ivy}[http://ant.apache.org/ivy/index.html] via a ruby wrapper without the need to use Apache Ant.
+The wrapper uses Antwrap[http://antwrap.rubyforge.org/] to interface with Ivy.
+
+Includes a Extension for Buildr[http://buildr.apache.org/] and Rake[http://rake.rubyforge.org] to use
+{Apache Ivy}[http://ant.apache.org/ivy/index.html] for dependency management.
+
+== FEATURES/PROBLEMS:
+
+Supports most standard Ivy Ant targets via Antwrap. Provides a caching feature so that long running ivy tasks
+like resolve can be cached and are not rerun for local builds. For more information about caching see the History.txt
+and checkout the source of buildr/ivy_extension.rb and rake/ivy_extension.rb.
+
+=== Supported Ivy targets:
+* info
+* settings
+* configure
+* cleancache
+* buildnumber
+* findrevision
+* cachepath
+* artifactreport
+* resolve
+* makepom
+* retrieve
+* publish
+* artifactproperty
+* report
+* buildlist
+* deliver
+* install
+* repreport
+
+=== Currently not working Ivy targets:
+* listmodules
+
+=== Ivy targets that need to be implemented:
+* deliver
+* install
+* repreport
+
+=== Unsupported Ivy Targets (they make no sense for the wrapper):
+* cachefileset
+* var
+
+=== Caching of Ivy results:
+For Buildr the targets ivy:enable_result_cache, ivy:disable_result_cache and ivy:clean_result_cache have been added.
+Additionally the result cache can be enabled via the build.yaml or the global buildr settings.yaml by setting
+the variable "ivy: caching.enabled: true".
+
+For Rake the targets ivy:enable_result_cache, ivy:disable_result_cache and ivy:clean_result_cache have been added as
+well. For Rake there is no other way to enable the caching beside this targets.
+
+== Notes about usage and testing:
+A few information how this project is used and what parts are well tested and what parts are nearly never used.
+
+=== Buildr extension:
+The buildr extension is tested only on projects with a single ivy.xml, the multi ivy.xml file support was added
+but was never tested extensively!
+
+=== Rake extension:
+Note that the rake extension is only test in JRuby Rails projects to publish a java WAR file into the repository.
+It does not offer as many features as the buildr extension.
+
+== SYNOPSIS:
+
+ivy4r plain:
+  To init a new Ivy4r instance set the ANT_HOME and the Ivy lib dir
+    ivy4r = Ivy4r.new
+    ivy4r.ant_home = 'PATH TO YOUR ANTHOME'
+    ivy4r.lib_dir = 'PATH TO IVY LIB DIR'
+  as an alternative to setting the ANT_HOME you can set an +Antwrap+ instance directly:
+    ivy4r.ant = Buildr.ant('ivy')
+    
+buildr:
+  TODO add buildr example
+
+rake:
+  TODO add rake example
+
+== REQUIREMENTS:
+
+Plain ivy4r:
+* Installed Apache Ant, to call Ivy via Antwrap
+* Ivy and dependencies in a single directory. Dependencies depends on used features, see the ivy homepage for more information.
+* JRuby is well tested, MRI support has been added with version 0.11.0 so use it at your own risk.
+* Rake to use the rake extension
+* Buildr to use the buildr extension
+
+== INSTALL:
+
+You can use gemcutter to install
+  sudo gem install ivy4r
+
+== LICENSE:
+
+(The MIT License)
+
+Copyright (c) 2009 blau Mobilfunk GmbH
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+'Software'), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.