tetra 0.40.0

data/.gitignore

@@ -0,0 +1,27 @@
+*.gem
+*.rbc
+.bundle
+.config
+coverage
+InstalledFiles
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+
+# SPEC generated files
+spec/data/nailgun/com.martiansoftware\:nailgun-all\:0.9.1
+spec/data/struts-apps/org.apache.struts\:struts2-apps\:
+spec/data/test-project
+
+# YARD artifacts
+.yardoc
+_yardoc
+doc/
+
+# integration test files
+integration-tests/galaxy
+

data/.rubocop.yml

@@ -0,0 +1,14 @@
+ClassLength:
+  Max: 200
+
+LineLength:
+  Max: 120
+
+MethodLength:
+  Max: 35
+
+StringLiterals:
+  EnforcedStyle: double_quotes
+
+MultilineBlockChain:
+  Enabled: false

data/Gemfile

@@ -0,0 +1,4 @@
+source "http://rubygems.org"
+
+# See tetra.gemspec
+gemspec

data/LICENSE

@@ -0,0 +1,28 @@
+Copyright (c) 2013 SUSE
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are
+met:
+
+   * Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+   * Redistributions in binary form must reproduce the above
+copyright notice, this list of conditions and the following disclaimer
+in the documentation and/or other materials provided with the
+distribution.
+   * Neither the name of Google Inc. nor the names of its
+contributors may be used to endorse or promote products derived from
+this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

data/MOTIVATION.md

@@ -0,0 +1,27 @@
+# Motivation
+
+The Java developer world has packages (jars, wars, ears...), tools ([ant](http://ant.apache.org/), [Maven](http://maven.apache.org/), [Ivy](http://ant.apache.org/ivy/), [Gradle](http://www.gradle.org/)...) and established workflows to handle software distribution while Linux distros have their own ([zypper](http://en.opensuse.org/Portal:Zypper), [yum](http://en.wikipedia.org/wiki/Yellowdog_Updater,_Modified), [apt](http://en.wikipedia.org/wiki/Advanced_Packaging_Tool)...). Since the two communities have different goals and requirements, Linux distros typically want to repackage Java software with their own format, tools and workflows. Reasons range from ease of installation, predictable rebuildability, support to (security) patching, management tools, legal issues, etc.
+
+Unfortunately those two "schemes" became very different over time, so automatic translation/repackaging is not possible except in very simple cases. This leads to a lot of tedious, error-prone manual work that Linux packagers have to do in order to fit the "alien" Java model into distro packaging rules that were thought and optimized with a different ecosystem in mind.
+
+A typical example is packaging any software built by Maven on SUSE distros. A number of pain points arise:
+
+* Maven requires Internet access and downloads precompiled code as part of the build. RPMs have to be built on a standalone machine in [OBS](http://en.opensuse.org/openSUSE:Build_Service), and they should build code from sources they are provided beforehands exclusively;
+* [Maven is basically a plugin container](http://maven.apache.org/plugins/), so hundreds of different plugins have to be installed to build real-life projects (the exact plugin set and their dependencies is determined at build time). While this is no big deal for Java developers, since they get the corresponding jars prebuilt from public Intenet Maven repositories, it is a nightmare for distros, because all shipping code is supposed to be built from scratch and packaged!
+* Maven often uses multiple versions of a same library or plugin during the same build. Usually distros do not accept more than one version of any given library to reduce maintenance work;
+* Maven requires itself in order to build. To be more exact, Maven needs Nexus, which in turn needs Maven and Nexus. To be more exact, its build dependency graph is a very complicated mess with lots of cycles that have to be broken manually.
+
+The current solution in openSUSE is having the packager handle those differences, but this limits the amount of software the community is able to package due to the high effort required to overcome them.
+
+The Fedora community is experimenting with another set of tools, [XMvn](http://mizdebsk.fedorapeople.org/xmvn/site/), which goals are similar to `tetra`'s. 
+
+## Kit rationale
+
+`tetra` simplifies the packaging process mostly because of its use of a binary blob package that contains all build time dependencies for a set of packages called a **kit**.
+
+Building software from a binary blob is unusual for Linux distros, and it surely has some drawbacks. It is anyway believed that benefits outweigh them, in fact using prebuilt software:
+
+* drastically reduces packaging efforts. A very basic and relatively simple package like [commons-collections](http://commons.apache.org/proper/commons-collections/) needs about [150 jars](https://build.opensuse.org/package/show/home:SilvioMoioli/myproject-kit) just to be compiled and tested. Those should be packaged, roughly, one-by-one!
+* is just the way all Java developers out there build, test and use their software — this is how they expect it to work. Any different approach is necessarily error-prone and could result in unexpected bugs;
+* does not affect the ability of providing patches to Java projects, as only build time requirements are in the kit. In virtually all cases patching a piece of software does not require to patch its build toolchain;
+* does not affect the ability of complying to software licenses like the GPL. In fact those licenses only require to redistribute a project's source code - not the whole toolchain needed to build it. Sources can be added and shipped together with binaries when licenses require it.

data/README.md

@@ -0,0 +1,106 @@
+# tetra – builds RPMs for Java software
+
+`tetra` is a set of tools to help you build RPM packages for Java projects.
+
+Packaging of Java projects is sometimes hard because build tools like Maven partially overlap with distro tools like RPM in functionality.
+
+This tool's goal is to drastically simplifies packaging.
+
+## Installation
+
+You need:
+
+* [Ruby 1.9](https://www.ruby-lang.org/en/);
+* [git](http://git-scm.com/);
+* a JDK that can compile whatever software you need to package;
+
+Install `tetra` via RubyGems:
+
+     gem install tetra
+
+## Workflow
+
+Building a package with `tetra` is quite unusual — this is a deliberate choice, so don't worry. Basic steps are:
+
+* `tetra init` a new project;
+* add sources to `src/<package name>` and anything else needed for the build in `kit/` in binary form (typically a copy of Maven and maybe some other dependency jars);
+* execute `tetra dry-run`, then any command needed to compile your software, then `tetra finish`;
+* execute `tetra generate-all`: tetra will look at changed files and Bash history to scaffold spec files and tarballs.
+
+Done!
+
+### How can that possibly work?
+
+With `tetra` you are not building all dependencies from source, just your package. Everything else is shipped already compiled with attached source files, which is much easier to implement and automate. Yet, it is sufficient to fulfill open source licenses and to have a repeatable, networkless build. See [MOTIVATION.md](MOTIVATION.md) for further information.
+
+## A commons-collections walkthrough
+
+First, ceate a new `tetra` project, in this example named "myproject":
+
+    mkdir myproject
+    cd myproject
+    tetra init
+
+Second, place commons-collections source files in the `src/` folder. Specifically, every `src/` subfolder will become a separate package named after the folder itself, so you can use the following:
+
+    cd src
+    mkdir commons-collections
+    cd commons-collections
+    wget http://archive.apache.org/dist/commons/collections/source/commons-collections-3.2.1-src.zip
+    unzip commons-collections-3.2.1-src.zip
+    rm commons-collections-3.2.1-src.zip
+
+Third, put all non-source files needed for the build in `kit/`. This means all build dependencies and tools excluding the JDK: in this case it is just Maven:
+
+    cd ../../kit
+    wget http://www.eu.apache.org/dist/maven/binaries/apache-maven-3.1.1-bin.zip
+    unzip apache-maven-3.1.1-bin.zip
+    rm apache-maven-3.1.1-bin.zip
+
+Fourth, you need to show `tetra` how to build your package by running appropriate commands between `tetra dry-run` and `tetra finish`. Bash history will be recorded to generate a "starting-point" build script (that will be sufficient in simple cases like this):
+
+    cd ../src/commons-collections/commons-collections-3.2.1-src/
+    tetra dry-run
+    tetra mvn package
+    tetra finish
+
+Note that we used `tetra mvn package` instead of `mvn package`: this will use of the Maven copy we put in `kit/` and the repository in `kit/m2`.
+Also note that this being a dry-run build, sources will be brought back to their original state after `tetra finish`, as this ensures build repeatability.
+
+Finally, generate build scripts, spec files and tarballs in the `output/` directory:
+
+    tetra generate-all
+
+Note that `tetra` will generate files for the commons-collections package and for the binary-only myproject-kit package, which is a special container of all build-time dependencies (basically, the `kit/` folder). This will be shared among all packages you might add to your `tetra` project.
+
+## In-depth information
+
+In more complex cases building a package will require some special tweaks. We are trying to cover the most common in the [SPECIAL_CASES.md](SPECIAL_CASES.md) file.
+
+An in-depth discussion of this project's motivation is available in the [MOTIVATION.md](MOTIVATION.md) file.
+
+## Status
+
+`tetra` is a research project currently in beta state. If you are a packager you can try to use it, any feedback would be **very** welcome!
+
+At the moment `tetra` is tested on openSUSE.
+
+## Sources
+
+`tetra`'s Git repo is available on GitHub, which can be browsed at:
+
+    https://github.com/SilvioMoioli/tetra
+
+and cloned with:
+
+    git clone git@github.com:SilvioMoioli/tetra.git
+
+## Contact
+
+Are you using `tetra` or even just reading this? Let's get in touch!
+
+    smoioli at suse dot de
+
+## License
+
+MIT license.

data/Rakefile

@@ -0,0 +1,9 @@
+# encoding: UTF-8
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new
+
+task default: :test
+task test: :spec

data/SPECIAL_CASES.md

@@ -0,0 +1,130 @@
+# Special cases
+
+## Failing builds
+
+If your build fails for whatever reason, abort it with `tetra finish --abort`. `tetra` will restore all project files as they were before build.
+
+## Manual changes to generated files
+
+You can do any manual changes to spec and build.sh files and regenerate them later, `tetra` will reconcile changes with a [three-way merge](http://en.wikipedia.org/wiki/Three-way_merge#Three-way_merge) and alert about any conflicts. You can generate single files with the following commands:
+
+* `tetra generate-kit-archive`: (re)generates the kit tarball;
+* `tetra generate-kit-spec`: (re)generates the kit spec;
+* `tetra generate-package-script`: (re)generates the `build.sh` file from the latest bash history (assumes `tetra dry-run` and `tetra finish`have been used). Assumes your current working directory is in a package folder (that is, a subdirectory of `src/<package name>/`);
+* `tetra generate-package-archive`: (re)generates a package tarball;
+* `tetra generate-package-spec`: (re)generates a package spec;
+
+Note that, by default, `generate-kit-archive` will generate additional "diff" tar.xz files instead of rewriting the whole archive - this will result in faster uploads if you use OBS (see below). You can use the `--whole` option to regenerate a single complete archive.
+
+## Kit sources
+
+Your kit is basically a binary blob. If its sources are needed for proper packaging, for example to comply with the GPL, some extra steps are needed.
+
+If you use Maven, most (~90%) sources can be automatically downloaded:
+
+    tetra download-maven-source-jars
+
+The remaining (mostly very outdated) jars will be listed by `tetra` when the download ends. You need to manually find corresponding sources for them, you can use:
+
+    tetra get-source /path/to/<jar name>.pom
+
+to get pointers to relevant sites if available in the pom itself.
+
+A list of commonly used jars can be found [below](#frequently-used-sources).
+
+You can also use:
+
+    tetra list-kit-missing-sources
+
+To get a list of jars that have one or more `.class` file which does not have a corresponding `.java` file in `kit/` (or zip files in `kit/`).
+
+## Ant builds
+
+`tetra` is currently optimized for Maven as it is the most common build tool, but it can work with any other. In particular, support for Ant has already been implemented and `tetra ant` works like `tetra mvn`.
+
+Sometimes you will have jar files distributed along with the source archive that will end up in `src/`: you don't want that! Run
+
+    tetra move-jars-to-kit
+
+to have them moved to `kit/jars`. The command will generate a symlink back to the original, so builds will work as expected.
+
+When generating spec files, be sure to have a `pom.xml` in your package directory even if you are not using Maven: `tetra` will automatically take advantage of information from it to compile many fields.
+
+You can also ask `tetra` to find one via `tetra get-pom <filename>.jar` (be sure to have Maven in your kit).
+
+## Other build tools
+
+Other build tools are currently unsupported but will be added in the future. You can nevertheless use them - the only rule is that you have to keep all of their files in `kit`.
+
+## [OBS](build.opensuse.org) integration
+
+If you want to submit packages to OBS, you can do so by replacing the `output/` directory in your `tetra` project with a symlink to your OBS project directory.
+
+Packages will rebuild cleanly in OBS because no Internet access is needed - all files were already downloaded during dry-run and are included in the kit.
+
+Note that the kit package is needed at build time only by OBS, no end user should ever install it.
+
+
+## Gotchas
+
+* `tetra` internally uses `git` to keep track of files, any tetra project is actually also a `git` repo. Feel free to navigate it, you can commit, push and pull as long as the `tetra` tags are preserved. You can also delete commits and tags, effectively rewinding tetra history (just make sure to delete all tags pointing to a certain commit when you discard it);
+* some Maven plugins like the Eclipse Project ones ([Tycho](https://www.eclipse.org/tycho/)) will save data in `/tmp` downloaded from the Internet and will produce errors if this data is not there during offline builds. One way to work around that is to force Java to use a kit subdirectory as `/tmp`. Add the following option to `tetra mvn` during your build:
+
+    -DskipTests=true -Djava.io.tmpdir=<full path to project>/kit/tmp
+
+Use the following option in `mvn` in your build.sh file to make it reproducible:
+
+    -DskipTests=true -Djava.io.tmpdir=$PROJECT_PREFIX/kit/tmp
+
+* Tycho builds may also require NSS, so if you get NSS errors be sure to add `mozilla-nss` or an equivalent package in a BuildRequires: line;
+
+* if you want to be 100% sure your package builds without network access, you can use scripts in the `utils/` folder to create a special `nonet` user that cannot use the Internet and retry the build from that user.
+
+## Frequently used sources
+
+* ant-1.8.1: `wget http://archive.apache.org/dist/ant/source/apache-ant-1.8.1-src.tar.gz -O kit/m2/org/apache/ant/ant/1.8.1/ant-1.8.1-sources.tar.gz`;
+* ant-1.8.2: `wget http://archive.apache.org/dist/ant/source/apache-ant-1.8.2-src.tar.gz -O kit/m2/org/apache/ant/ant/1.8.2/ant-1.8.2-sources.tar.gz`;
+* ant-launcher-<version>: sources included in ant-<version>;
+* ant-nodeps-<version>: sources included in ant-<version>;
+* antlr-2.7.7: `wget http://www.antlr2.org/download/antlr-2.7.7.tar.gz -O kit/m2/antlr/antlr/2.7.7/antlr-2.7.7-sources.tar.gz`;
+* asm-3.3.1, asm-commons-3.3.1, asm-tree-3.3.1: `wget http://download.forge.ow2.org/asm/asm-3.3.1.tar.gz -O kit/m2/asm/asm/3.3.1/asm-3.3.1-sources.tar.gz`;
+* aspectjrt-1.5.3: `wget http://git.eclipse.org/c/aspectj/org.aspectj.git/snapshot/org.aspectj-1_5_3_final.tar.gz -O kit/m2/aspectj/aspectjrt/1.5.3/aspectjrt-1.5.3-sources.tar.gz` (you can remove tests, lib, docs and org.eclipse.jdt.core);
+* avalon-framework-4.1.5: `wget http://archive.apache.org/dist/avalon/avalon-framework/v4.1.5/avalon-framework-4.1.5.src.tar.gz -O kit/m2/avalon-framework/avalon-framework/4.1.5//4.1.5--sources.tar.gz`;
+* batik-<subartifact>-1.7: `mkdir kit/m2/org/apache/xmlgraphics/batik/; wget http://archive.apache.org/dist/xmlgraphics/batik/batik-src-1.7.zip -O kit/m2/org/apache/xmlgraphics/batik/batik-sources.zip`
+* bndlib-0.0.238, bndlib-0.0.255: these are used by apache-felix-1.4.x, which is in turn used by commons-parent < 22 to provide JDK 1.4 compatibility. Unfortunately no source before 1.1 is available, if possible update your dependencies to commons-parent >= 22;
+* bsh-2.0b4: `wget http://beanshell2.googlecode.com/files/bsh-2.0b4-src.jar -O kit/m2/org/beanshell/bsh/2.0b4/bsh-2.0b4-sources.zip`;
+* commons-beanutils-core-1.8.0: `wget http://archive.apache.org/dist/commons/beanutils/source/commons-beanutils-1.8.0-src.tar.gz -O kit/m2/commons-beanutils/commons-beanutils-core/1.8.0/commons-beanutils-core-1.8.0-sources.tar.gz`;
+* commons-beanutils-core-1.8.3: `wget http://archive.apache.org/dist/commons/beanutils/source/commons-beanutils-1.8.3-src.tar.gz -O kit/m2/commons-beanutils/commons-beanutils-core/1.8.3/commons-beanutils-core-1.8.3-sources.tar.gz`;
+* commons-codec-1.2: `wget http://archive.apache.org/dist/commons/codec/source/commons-codec-1.2-src.tar.gz -O kit/m2/commons-codec/commons-codec/1.2/commons-codec-1.2-sources.tar.gz`;
+* commons-collections-testframework-3.2.1: included in commons-collections-3.2.1;
+* commons-collections-2.0: `wget http://archive.apache.org/dist/commons/collections/source/collections-2.0-src.tar.gz -O kit/m2/commons-collections/commons-collections/2.0/commons-collections-2.0-sources.tar.gz`;
+* commons-jexl-1.1: `wget http://archive.apache.org/dist/commons/jexl/source/commons-jexl-1.1-src.tar.gz -O kit/m2/commons-jexl/commons-jexl/1.1/commons-jexl-1.1-sources.tar.gz`;
+* commons-lang-1.0: `wget http://archive.apache.org/dist/commons/lang/source/lang-1.0-src.tar.gz -O kit/m2/commons-lang/commons-lang/1.0/commons-lang-1.0-sources.tar.gz`;
+* commons-logging-api-1.1: `wget http://archive.apache.org/dist/commons/logging/source/commons-logging-1.1-src.tar.gz -O kit/m2/commons-logging/commons-logging/1.1/commons-logging-1.1-sources.tar.gz` (included in commons-logging-1.1);
+* commons-logging-1.0: `wget http://archive.apache.org/dist/commons/logging/source/logging-1.0-src.tar.gz -O kit/m2/commons-logging/commons-logging/1.0/commons-logging-1.0-sources.tar.gz`;
+* derby-10.9.1.0: `wget http://archive.apache.org/dist/db/derby/db-derby-10.9.1.0/db-derby-10.9.1.0-src.tar.gz -O kit/m2/org/apache/derby/derby/10.9.1.0/derby-10.9.1.0-sources.tar.gz`;
+* dom4j-1.1: `wget http://dom4j.cvs.sourceforge.net/viewvc/dom4j/dom4j/?view=tar\&pathrev=dom4j-1-1 -O kit/m2/dom4j/dom4j/1.1/dom4j-1.1-sources.tar.gz`;
+* doxia-sink-api-1.0-alpha-4: use `svn export http://svn.apache.org/repos/asf/maven/doxia/doxia/tags/doxia-sink-api-1.0-alpha-4/ kit/m2/doxia/doxia-sink-api/1.0-alpha-4/doxia-sink-api-1.0-alpha-4-sources`;
+* fop-0.95: `wget http://archive.apache.org/dist/xmlgraphics/fop/source/fop-0.95-src.tar.gz -O kit/m2/org/apache/xmlgraphics/fop/0.95/fop-0.95-sources.tar.gz`;
+* hc-stylecheck-1: contains only metadata, no sources to be compiled in this artifact;
+* jsr305-1.3.9, jsr305-2.0.1: sources included in jar;
+* jsch-0.1.38: `wget http://sourceforge.net/projects/jsch/files/jsch/0.1.38/jsch-0.1.38.zip/download -O kit/m2/com/jcraft/jsch/0.1.38/jsch-0.1.38-sources.zip`;
+* kxml2-2.2.2: use `wget http://sourceforge.net/projects/kxml/files/kxml2/2.2.2/kxml2-src-2.2.2.zip/download -O kit/m2/net/sf/kxml/kxml2/2.2.2/kxml2-2.2.2-sources.zip`;
+* log4j-1.2.12: `wget http://archive.apache.org/dist/logging/log4j/1.2.12/logging-log4j-1.2.12.tar.gz -O kit/m2/log4j/log4j/1.2.12/log4j-1.2.12-sources.tar.gz`;
+* naming-common-5.0.28, naming-java-5.0.28: `mkdir -p kit/m2/tomcat/tomcat/5.0.28/; wget http://archive.apache.org/dist/tomcat/tomcat-5/v5.0.28/src/jakarta-tomcat-5.0.28-src.tar.gz -O kit/m2/tomcat/tomcat/5.0.28/tomcat-5.0.28-sources.tar.gz` (part of tomcat);
+* org.osgi.core-1.0.0: `wget http://archive.apache.org/dist/felix/org.osgi.core-1.0.0.tar.gz -O kit/m2/org/apache/felix/org.osgi.core/1.0.0/org.osgi.core-1.0.0-sources.tar.gz`;
+* org.osgi.core-4.1.0: sources included in jar;
+* org.osgi.service.obr-1.0.1: `wget http://archive.apache.org/dist/felix/org.osgi.service.obr-1.0.1-project.tar.gz -O kit/m2/org/apache/felix/org.osgi.service.obr/1.0.1/org.osgi.service.obr-1.0.1-sources.tar.gz`;
+* plexus-utils-1.4.9: `wget https://github.com/sonatype/plexus-utils/archive/plexus-utils-1.4.9.tar.gz -O kit/m2/org/codehaus/plexus/plexus-utils/1.4.9/plexus-utils-1.4.9-sources.tar.gz`;
+* spymemcached-2.6: `wget http://spymemcached.googlecode.com/files/memcached-2.4.2-sources.zip -O kit/m2/spy/spymemcached/2.6/spymemcached-2.6-sources.zip`;
+* stringtemplate-3.2: `wget http://www.stringtemplate.org/download/stringtemplate-3.2.tar.gz -O kit/m2/org/antlr/stringtemplate/3.2/stringtemplate-3.2-sources.tar.gz`;
+* velocity-tools-2.0: `wget http://archive.apache.org/dist/velocity/tools/2.0/velocity-tools-2.0-src.tar.gz -O kit/m2/org/apache/velocity/velocity-tools/2.0/velocity-tools-2.0-sources.tar.gz`;
+* velocity-1.5: `wget http://archive.apache.org/dist/velocity/engine/1.5/velocity-1.5.tar.gz -O kit/m2/org/apache/velocity/velocity/1.5/velocity-1.5-sources.tar.gz`;
+* trilead-ssh2-build213-svnkit-1.3: `svn export http://svn.svnkit.com/repos/svnkit/tags/1.3.5/ kit/m2/org/tmatesoft/svnkit/svnkit/1.3.5/svnkit-1.3.5-sources` (included in svnkit 1.3.5 full sources because of custom patch);
+* xercesImpl-2.9.1: `wget http://archive.apache.org/dist/xerces/j/source/Xerces-J-src.2.9.1.tar.gz -O kit/m2/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1-sources.tar.gz`;
+* xercesMinimal-1.9.6.2: included in any xercesImpl >= 2 source package;
+* xml-apis-ext-1.3.04: `wget http://archive.apache.org/dist/xml/commons/xml-commons-external-1.3.04-src.tar.gz -O kit/m2/xml-apis/xml-apis-ext/1.3.04/xml-apis-ext-1.3.04-sources.tar.gz`;
+* xmlgraphics-commons-1.3.1: `wget http://archive.apache.org/dist/xmlgraphics/commons/source/xmlgraphics-commons-1.3.1-src.tar.gz -O kit/m2/org/apache/xmlgraphics/xmlgraphics-commons/1.3.1/xmlgraphics-commons-1.3.1-sources.tar.gz`;
+* xmlpull-1.1.3.1: `wget http://www.extreme.indiana.edu/xmlpull-website/v1/download/xmlpull_1_1_3_4c_src.tgz -O kit/m2/xmlpull/xmlpull/1.1.3.1/xmlpull-1.1.3.1-sources.tar.gz`;
+* xpp3-1.1.3.3: `wget http://www.extreme.indiana.edu/dist/java-repository/xpp3/distributions/xpp3-1.1.3.4.C_src.tgz -O kit/m2/xpp3/xpp3/1.1.3.3/xpp3-1.1.3.3-sources.tar.gz`;
+* xmlunit-1.3: `wget http://sourceforge.net/projects/xmlunit/files/xmlunit%20for%20Java/XMLUnit%20for%20Java%201.3/xmlunit-1.3-src.zip/download -O kit/m2/xmlunit/xmlunit/1.3/xmlunit-1.3-sources.zip`;

data/bin/tetra

@@ -0,0 +1,29 @@
+#!/usr/bin/env ruby
+# encoding: UTF-8
+#
+# The (open)?SUSE ((Linux Enterprise) (Server|Desktop))?'s
+# packager Swiss Army Knife.
+#
+# Copyright 2013 Silvio Moioli <smoioli@suse.de>
+#
+# Inspired mainly by pom2spec by:
+#  Pascal Bleser <pascal.bleser@opensuse.org>
+#  Duncan Mac-Vicar Prett <dmacvicar@suse.de>
+#
+# This file is licensed under the
+# GNU Lesser General Public License version 2.1 or later:
+# http://www.gnu.org/licenses/lgpl-2.1.html
+#
+
+if File.exist?(File.join(File.dirname(__FILE__), "..", ".git"))
+  $LOAD_PATH << File.join(File.dirname(__FILE__), "..", "lib")
+end
+
+begin
+  require "tetra"
+rescue LoadError
+  require "rubygems"
+  require "tetra"
+end
+
+Tetra::MainCommand.run

data/integration-tests/commons.sh

@@ -0,0 +1,55 @@
+#!/bin/bash
+
+# A crude integration test that builds commons-collections
+
+set -e
+
+rm -Rf galaxy
+mkdir galaxy
+cd galaxy
+tetra init
+
+cd src
+mkdir commons-collections
+cd commons-collections
+wget http://archive.apache.org/dist/commons/collections/source/commons-collections-3.2.1-src.zip
+unzip commons-collections-3.2.1-src.zip
+rm commons-collections-3.2.1-src.zip
+
+cd ../../kit
+wget http://apache.fastbull.org/maven/maven-3/3.1.1/binaries/apache-maven-3.1.1-bin.zip
+unzip apache-maven-*.zip
+rm apache-maven-*.zip
+cd ..
+
+tetra dry-run --very-very-verbose
+cd src/commons-collections/commons-collections-3.2.1-src/
+tetra mvn package -DskipTests
+tetra finish
+
+tetra generate-all
+cd ../../..
+
+cd src
+mkdir commons-fileupload
+cd commons-fileupload
+wget http://archive.apache.org/dist/commons/fileupload/source/commons-fileupload-1.3-src.zip
+unzip commons-fileupload-1.3-src.zip
+rm commons-fileupload-1.3-src.zip
+
+tetra dry-run
+cd commons-fileupload-1.3-src/
+tetra mvn package -DskipTests
+tetra finish
+
+tetra generate-kit-archive
+tetra generate-kit-spec
+tetra generate-package-script
+tetra generate-package-archive
+tetra generate-package-spec
+cd ../../..
+
+
+echo "**************** All Done ****************"
+
+ls -lah output/*

data/lib/template/gitignore

@@ -0,0 +1,2 @@
+*.tetra_user_edited
+output/

data/lib/template/kit.spec

@@ -0,0 +1,64 @@
+#
+# spec file for tetra kit for project "<%= name %>"
+#
+# Copyright (c) <%= Time.now.year %> <%= Etc.getlogin %>
+#
+# All modifications and additions to the file contributed by third parties
+# remain the property of their copyright owners, unless otherwise agreed
+# upon. The license for this file, and modifications and additions to the
+# file, is the same license as for the pristine package itself (unless the
+# license for the pristine package is not an Open Source License, in which
+# case the license is the MIT License). An "Open Source License" is a
+# license that conforms to the Open Source Definition (Version 1.9)
+# published by the Open Source Initiative.
+
+# Please submit bugfixes or comments via http://bugs.opensuse.org/
+#
+
+Name:           <%= name %>-kit
+Version:        <%= version %>
+Release:        1
+License:        Apache-2.0
+Summary:        Build-time dependencies for tetra project <%= name %>
+Url:            https://github.com/SilvioMoioli/tetra
+Group:          Development/Libraries/Java
+<% archives.each_with_index do |archive, i| %>
+Source<%= i %>:        <%= archive %>
+<% end %>
+BuildRoot:      %{_tmppath}/%{name}-%{version}-build
+BuildArch:      noarch
+BuildRequires:  xz
+BuildRequires:  fdupes
+Provides:       tetra(kit)
+# no two kits should ever be installed at any given time
+Conflicts:      otherproviders(tetra(kit))
+
+%description
+This package has been automatically created by tetra in order to
+satisfy build time dependencies of some Java packages. It should
+not be used except for rebuilding those packages and it should never
+be installed on end users' systems.
+
+%prep
+<% (0..(archives.length-1)).each do |i| %>
+<% if i > 0 %>
+%setup -q -c -T -D -b <%= i %>
+<% else %>
+%setup -q -c -T -b <%= i %>
+<% end %>
+<% end %>
+
+%build
+# nothing to do, tetra kits are precompiled by design
+
+%install
+export NO_BRP_CHECK_BYTECODE_VERSION=true
+install -d -m 0755 %{buildroot}%{_datadir}/tetra/%{name}/
+cp -a * %{buildroot}%{_datadir}/tetra/%{name}/
+%fdupes -s %{buildroot}%{_datadir}/tetra/%{name}/
+
+%files
+%defattr(-,root,root)
+%{_datadir}/tetra/
+
+%changelog