diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/.gitignore
diff --git a/.rh-maven33.metadata b/.rh-maven33.metadata
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/.rh-maven33.metadata
diff --git a/README.md b/README.md
deleted file mode 100644
index 98f42b4..0000000
--- a/README.md
+++ /dev/null
@@ -1,4 +0,0 @@
-The master branch has no content
-
-Look at the c7 branch if you are working with CentOS-7, or the c4/c5/c6 branch for CentOS-4, 5 or 6
-If you find this file in a distro specific branch, it means that no content has been checked in yet
diff --git a/SOURCES/LICENSE b/SOURCES/LICENSE
new file mode 100644
index 0000000..d159169
--- /dev/null
+++ b/SOURCES/LICENSE
@@ -0,0 +1,339 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+                            NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License along
+    with this program; if not, write to the Free Software Foundation, Inc.,
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.
diff --git a/SOURCES/README b/SOURCES/README
new file mode 100644
index 0000000..e2c6e7f
--- /dev/null
+++ b/SOURCES/README
@@ -0,0 +1,40 @@
+The %{scl_name} package provides Apache Maven 3.3.9 with a set of Maven
+plugins delivered as a Software Collection. For more information
+about Software Collections, see the scl(1) man page.
+
+Installing the %{scl_name} Software Collection gets you Maven 3.3.9
+with all required dependencies, including the Java Development Kit.
+
+Usage: scl enable %{scl} 'mvn'
+
+Software Collections allow you to build and execute applications which
+are not located in the file system root hierarchy but instead are stored in
+an alternative location. The location is %{_scl_root} in
+case of the %{scl_name} Software Collection.
+
+Maven is a software project management and comprehension tool. Based
+on the concept of a project object model (POM), Maven can manage a
+project's build, reporting and documentation from a central piece of
+information.
+
+When you want to start working with the %{scl_name} Software Collection, use the
+scl utility to enable the scl environment. See the scl(1) man page for
+usage.
+
+Examples:
+scl enable %{scl_name} 'command --arg'
+  Run a specific command with the argument --arg from within the
+  %{scl_name} Software Collection environment.
+
+scl enable %{scl_name} 'mvn'
+  Run mvn from the %{scl_name} Software Collection.
+
+scl enable %{scl_name} bash
+  Run an interactive shell with the %{scl_name} Software Collection
+  enabled.
+
+scl enable %{scl_name} 'man mvn'
+  Show man pages for the mvn command, which is a part of the
+  %{scl_name} Software Collection.
+
+Report any bugs to <http://bugzilla.redhat.com>.
diff --git a/SOURCES/javapackages-config.json b/SOURCES/javapackages-config.json
new file mode 100644
index 0000000..a7a4d8e
--- /dev/null
+++ b/SOURCES/javapackages-config.json
@@ -0,0 +1,22 @@
+{
+    "maven.req": {
+        "always_generate": [
+            "rh-maven33-runtime"
+        ],
+        "java_requires": {
+            "package_name": "java",
+            "always_generate": true,
+            "skip": false
+        },
+        "java_devel_requires": {
+            "package_name": "java-devel",
+            "always_generate": false,
+            "skip": false
+        }
+    },
+    "javadoc.req": {
+        "always_generate": [
+            "rh-maven33-runtime"
+        ]
+    }
+}
diff --git a/SOURCES/macros.rh-maven33 b/SOURCES/macros.rh-maven33
new file mode 100644
index 0000000..6c061a0
--- /dev/null
+++ b/SOURCES/macros.rh-maven33
@@ -0,0 +1,5 @@
+%scl_maven rh-maven33
+%scl_prefix_maven rh-maven33-
+
+# macro to invoke the javapackages provides and requires generators on el6
+%maven_find_provides_and_requires %{java_common_find_provides_and_requires}
diff --git a/SOURCES/xmvn-configuration.xml b/SOURCES/xmvn-configuration.xml
new file mode 100644
index 0000000..c0d1d03
--- /dev/null
+++ b/SOURCES/xmvn-configuration.xml
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="US-ASCII"?>
+<configuration xmlns="http://fedorahosted.org/xmvn/CONFIG/2.0.0">
+  <resolverSettings>
+    <metadataRepositories>
+      <repository>/opt/rh/rh-maven33/root/usr/share/maven-metadata</repository>
+    </metadataRepositories>
+    <prefixes>
+      <prefix>/opt/rh/rh-maven33/root</prefix>
+    </prefixes>
+  </resolverSettings>
+  <installerSettings>
+    <metadataDir>opt/rh/rh-maven33/root/usr/share/maven-metadata</metadataDir>
+  </installerSettings>
+  <repositories>
+    <repository>
+      <id>install</id>
+      <type>compound</type>
+      <properties>
+        <prefix>opt/rh/rh-maven33/root</prefix>
+        <namespace>rh-maven33</namespace>
+      </properties>
+      <configuration>
+        <repositories>
+          <repository>base-install</repository>
+        </repositories>
+      </configuration>
+    </repository>
+  </repositories>
+</configuration>
diff --git a/SPECS/rh-maven33.spec b/SPECS/rh-maven33.spec
new file mode 100644
index 0000000..e4c3e82
--- /dev/null
+++ b/SPECS/rh-maven33.spec
@@ -0,0 +1,497 @@
+%{!?scl_name_base:%global scl_name_base rh-maven}
+%{!?scl_name_version:%global scl_name_version 33}
+%{!?scl:%global scl %{scl_name_base}%{scl_name_version}}
+%scl_package %scl
+
+%global debug_package %{nil}
+
+Name:       %scl_name
+Version:    1
+Release:    17%{?dist}
+Summary:    Package that installs %scl
+
+License:    GPLv2+
+#URL:
+Source1:    macros.%{scl_name}
+Source2:    javapackages-config.json
+Source3:    xmvn-configuration.xml
+Source4:    README
+Source5:    LICENSE
+
+BuildRequires:  help2man
+BuildRequires:  scl-utils-build
+
+Requires:         %{name}-runtime = %{version}-%{release}
+Requires:         %{scl_name}-maven
+
+%description
+This is the main package for the %scl Software Collection.
+
+%package runtime
+Summary:    Package that handles %scl Software Collection.
+Requires:   scl-utils
+Requires:   java-1.7.0-openjdk-devel
+
+%description runtime
+Package shipping essential scripts to work with the %scl Software Collection.
+
+%package build
+Summary:    Build support tools for the %scl Software Collection.
+Requires:   scl-utils-build
+Requires:   %{name}-scldevel = %{version}-%{release}
+
+%description build
+Package shipping essential configuration marcros/files in order to be able
+to build %scl Software Collection.
+
+%package scldevel
+Summary:    Package shipping development files for %scl
+Requires:   %{name}-maven-local = %{version}-%{release}
+Requires:   %{name}-runtime = %{version}-%{release}
+Requires:   %{?scl_prefix_java_common}scldevel-common
+
+%description scldevel
+Package shipping development files, especially useful for development of
+packages depending on %scl Software Collection.
+
+# javapackages-tools counterparts for rh-maven33 collection
+%package maven-local
+Summary:        Support for Maven packaging
+Requires:       %{?scl_prefix_java_common}javapackages-tools
+Requires:       %{name}-javapackages-local = %{version}-%{release}
+Requires:       %{?scl_prefix}maven
+Requires:       %{?scl_prefix}xmvn >= 2
+Requires:       %{?scl_prefix}xmvn-mojo >= 2
+Requires:       %{?scl_prefix}xmvn-connector-aether >= 2
+# POM files needed by maven itself
+Requires:       %{?scl_prefix}apache-commons-parent
+Requires:       %{?scl_prefix}apache-parent
+Requires:       %{?scl_prefix}geronimo-parent-poms
+Requires:       %{?scl_prefix}httpcomponents-project
+Requires:       %{?scl_prefix}jboss-parent
+Requires:       %{?scl_prefix}jvnet-parent
+Requires:       %{?scl_prefix}maven-parent
+Requires:       %{?scl_prefix}maven-plugins-pom
+Requires:       %{?scl_prefix}mojo-parent
+Requires:       %{?scl_prefix}plexus-components-pom
+Requires:       %{?scl_prefix}plexus-pom
+Requires:       %{?scl_prefix}plexus-tools-pom
+Requires:       %{?scl_prefix}sonatype-oss-parent
+Requires:       %{?scl_prefix}weld-parent
+# Common Maven plugins required by almost every build. It wouldn't make
+# sense to explicitly require them in every package built with Maven.
+Requires:       %{?scl_prefix}maven-assembly-plugin
+Requires:       %{?scl_prefix}maven-compiler-plugin
+Requires:       %{?scl_prefix}maven-enforcer-plugin
+Requires:       %{?scl_prefix}maven-jar-plugin
+Requires:       %{?scl_prefix}maven-javadoc-plugin
+Requires:       %{?scl_prefix}maven-resources-plugin
+Requires:       %{?scl_prefix}maven-surefire-plugin
+# Tests based on JUnit are very common and JUnit itself is small.
+# Include JUnit provider for Surefire just for convenience.
+Requires:       %{?scl_prefix}maven-surefire-provider-junit
+# testng is quite common as well
+Requires:       %{?scl_prefix}maven-surefire-provider-testng
+Requires:       %{?scl_prefix_java_common}maven-local-support
+
+%description maven-local
+This package provides tools to support packaging Maven artifacts.
+
+%package ivy-local
+Summary:        Support for Apache Ivy packaging
+Requires:       %{?scl_prefix_java_common}javapackages-tools
+Requires:       %{name}-javapackages-local = %{version}-%{release}
+Requires:       %{?scl_prefix}apache-ivy
+Requires:       %{?scl_prefix}xmvn-connector-ivy >= 2
+Requires:       %{?scl_prefix_java_common}ivy-local-support
+
+%description ivy-local
+This package provides tools to support Apache Ivy packaging.
+
+%package javapackages-local
+Summary:        Non-essential tools for Java packaging
+Requires:       %{?scl_prefix_java_common}javapackages-tools
+Requires:       %{?scl_prefix}xmvn-install >= 2
+Requires:       %{?scl_prefix}xmvn-subst >= 2
+Requires:       %{?scl_prefix}xmvn-resolve >= 2
+Requires:       %{?scl_prefix_java_common}javapackages-local-support
+
+%description javapackages-local
+This package provides non-essential tools for Java packaging.
+
+%prep
+%setup -c -T
+#===================#
+# SCL enable script #
+#===================#
+cat <<EOF >enable
+. /opt/rh/%{scl_java_common}/enable
+
+# Generic variables
+export PATH="%{_bindir}:\${PATH:-/bin:/usr/bin}"
+export MANPATH="%{_mandir}\${MANPATH:+:}\${MANPATH:-}"
+export PYTHONPATH="%{_scl_root}%{python_sitelib}\${PYTHONPATH:+:}\${PYTHONPATH:-}"
+
+export JAVACONFDIRS="%{_sysconfdir}/java\${JAVACONFDIRS:+:}\${JAVACONFDIRS:-}"
+export XDG_CONFIG_DIRS="%{_sysconfdir}/xdg:\${XDG_CONFIG_DIRS:-/etc/xdg}"
+export XDG_DATA_DIRS="%{_datadir}:\${XDG_DATA_DIRS:-/usr/local/share:/usr/share}"
+EOF
+
+# Generate Eclipse configuration file
+cat <<EOF >eclipse.conf
+eclipse.bundles=%{_javadir},%{_jnidir}
+scl.namespace=%{?scl}
+scl.root=%{?_scl_root}
+EOF
+
+# Generate java.conf
+cat <<EOF >java.conf
+JAVA_LIBDIR=/opt/rh/%{scl_name}/root/usr/share/java
+JNI_LIBDIR=/opt/rh/%{scl_name}/root/usr/lib/java
+JVM_ROOT=/opt/rh/%{scl_name}/root/usr/lib/jvm
+EOF
+
+# This section generates README file from a template and creates man page
+# from that file, expanding RPM macros in the template file.
+cat >README <<'EOF'
+%{expand:%(cat %{SOURCE4})}
+EOF
+
+# copy the license file so %%files section sees it
+cp %{SOURCE5} .
+
+cp %{SOURCE1} macros.%{scl_name}
+cat >> macros.%{scl_name} << EOF
+%%_sysconfdir_maven %_sysconfdir
+%%_prefix_maven %_prefix
+%%_exec_prefix_maven %_exec_prefix
+%%_bindir_maven %_bindir
+%%_libdir_maven %_libdir
+%%_libexecdir_maven %_libexecdir
+%%_sbindir_maven %_sbindir
+%%_sharedstatedir_maven %_sharedstatedir
+%%_datarootdir_maven %_datarootdir
+%%_datadir_maven %_datadir
+%%_includedir_maven %_includedir
+%%_infodir_maven %_infodir
+%%_mandir_maven %_mandir
+%%_localstatedir_maven %_localstatedir
+%%_initddir_maven %_initddir
+%%_javadir_maven %_javadir
+%%_jnidir_maven %_jnidir
+%%_javadocdir_maven %_javadocdir
+%%_mavenpomdir_maven %_mavenpomdir
+%%_jvmdir_maven %_jvmdir
+%%_jvmsysconfdir_maven %_jvmsysconfdir
+%%_jvmcommonsysconfdir_maven %_jvmcommonsysconfdir
+%%_jvmjardir_maven %_jvmjardir
+%%_jvmprivdir_maven %_jvmprivdir
+%%_jvmlibdir_maven %_jvmlibdir
+%%_jvmdatadir_maven %_jvmdatadir
+%%_jvmcommonlibdir_maven %_jvmcommonlibdir
+%%_jvmcommondatadir_maven %_jvmcommondatadir
+%%_javaconfdir_maven %_javaconfdir
+EOF
+
+%build
+# generate a helper script that will be used by help2man
+cat >h2m_helper <<'EOF'
+#!/bin/bash
+[ "$1" == "--version" ] && echo "%{scl_name} %{version} Software Collection" || cat README
+EOF
+chmod a+x h2m_helper
+
+# generate the man page
+help2man -N --section 7 ./h2m_helper -o %{scl_name}.7
+# Fix single quotes in man page.
+sed -i "s/'/\\\\(aq/g" %{scl_name}.7
+
+%install
+# Parentheses are needed here as workaround for rhbz#1017085
+(%scl_install)
+
+install -d -m 755 %{buildroot}%{_scl_scripts}
+install -p -m 755 enable %{buildroot}%{_scl_scripts}/
+
+# install rpm magic
+install -Dpm0644 macros.%{scl_name} %{buildroot}%{_root_sysconfdir}/rpm/macros.%{scl_name_base}-scldevel
+
+# install dirs used by some deps
+install -dm0755 %{buildroot}%{_prefix}/lib/rpm
+install -dm0755 %{buildroot}%{_scl_root}%{python_sitelib}
+
+# install generated man page
+mkdir -p %{buildroot}%{_mandir}/man7/
+install -m 644 %{scl_name}.7 %{buildroot}%{_mandir}/man7/%{scl_name}.7
+
+# eclipse.conf, java.conf, javapackages-config.json and XMvn config
+install -m 755 -d %{buildroot}%{_javaconfdir}
+install -m 644 -p eclipse.conf %{buildroot}%{_javaconfdir}/
+install -m 644 -p %{SOURCE2} %{buildroot}%{_javaconfdir}/
+install -m 644 -p java.conf %{buildroot}%{_javaconfdir}/
+install -m 755 -d %{buildroot}%{_sysconfdir}/xdg/xmvn
+install -m 644 -p %{SOURCE3} %{buildroot}%{_sysconfdir}/xdg/xmvn/configuration.xml
+
+install -m 755 -d %{buildroot}%{_jnidir}
+install -m 755 -d %{buildroot}%{_javadir}
+install -m 755 -d %{buildroot}%{_javadocdir}
+install -m 755 -d %{buildroot}%{_mandir}/man1
+install -m 755 -d %{buildroot}%{_mandir}/man7
+install -m 755 -d %{buildroot}%{_datadir}/maven-metadata
+install -m 755 -d %{buildroot}%{_mavenpomdir}
+install -m 755 -d %{buildroot}%{_datadir}/xmvn
+install -m 755 -d %{buildroot}%{_datadir}/licenses
+
+# Empty package (no file content).  The sole purpose of this package
+# is collecting its dependencies so that the whole SCL can be
+# installed by installing %{name}.
+%files
+
+%files runtime
+%doc README LICENSE
+%{scl_files}
+%{_prefix}/lib/python2.*
+%{_prefix}/lib/rpm
+%{_mandir}/man7/%{scl_name}.*
+%{_javaconfdir}/
+%dir %{_jnidir}
+%dir %{_javadir}
+%dir %{_javadocdir}
+%dir %{_mandir}/man1
+%dir %{_mandir}/man7
+%dir %{_datadir}/maven-metadata
+%dir %{_mavenpomdir}
+%dir %{_datadir}/xmvn
+%dir %{_datadir}/licenses
+
+%files build
+%{_root_sysconfdir}/rpm/macros.%{scl}-config
+
+%files scldevel
+%{_root_sysconfdir}/rpm/macros.%{scl_name_base}-scldevel
+
+%files maven-local
+%files ivy-local
+%files javapackages-local
+
+%changelog
+* Thu Apr 14 2016 Michal Srb <msrb@redhat.com> - 1-17
+- Fix directory ownership (Resolves: rhbz#1325866)
+
+* Thu Feb 11 2016 Michal Srb <msrb@redhat.com> - 1-16
+- Remove temporary requires
+
+* Mon Feb 08 2016 Michal Srb <msrb@redhat.com> - 1-15
+- Fix macros.rh-maven33
+- Revert temporary changes in xmvn config
+
+* Mon Feb 08 2016 Michal Srb <msrb@redhat.com> - 1-14
+- Resolve from local repository first
+
+* Fri Feb 05 2016 Michal Srb <msrb@redhat.com> - 1-13
+- Temporarily resolve from rh-java-common first
+
+* Fri Jan 29 2016 Michal Srb <msrb@redhat.com> - 1-12
+- Correctly handle XDG env. variables in enable script (Resolves: rhbz#1300623)
+
+* Fri Jan 29 2016 Michal Srb <msrb@redhat.com> - 1-11
+- Rebuild
+
+* Wed Jan 27 2016 Michal Srb <msrb@redhat.com> - 1-10
+- Get rid of transitive maven30 dependency
+
+* Tue Jan 26 2016 Michal Srb <msrb@redhat.com> - 1-9
+- Fix R on javapackages-tools
+
+* Tue Jan 19 2016 Michal Srb <msrb@redhat.com> - 1-8
+- Introduce maven33-specific "local" subpackages
+- Drop temp requires
+
+* Mon Jan 18 2016 Michal Srb <msrb@redhat.com> - 1-7
+- Remove fake sonatype provides
+- Partially remove maven-wagon requires
+
+* Mon Jan 18 2016 Michal Srb <msrb@redhat.com> - 1-6
+- Fix R on rh-java-common packages
+
+* Mon Jan 18 2016 Michal Srb <msrb@redhat.com> - 1-5
+- Remove maven30 from PATH
+
+* Thu Jan 14 2016 Michal Srb <msrb@redhat.com> - 1-4
+- Reduce number of fake provides
+
+* Tue Jan 12 2016 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-3
+- Temporarly add maven30 to PATH
+
+* Sat Jan 09 2016 Michal Srb <msrb@redhat.com> - 1-2
+- Temporarily require all maven33 packages
+
+* Fri Jan 08 2016 Michal Srb <msrb@redhat.com> 1-1
+- Alter for rh-maven33
+
+* Tue Jul 21 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-27
+- Fix syntax errors in manpage
+
+* Wed Jun 10 2015 Michal Srb <msrb@redhat.com> - 1.1-26
+- Convert back to arch
+
+* Tue Jun  9 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-25
+- Convert to noarch
+
+* Mon Feb  2 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-24
+- Be more careful when setting env variables in enable script
+
+* Fri Jan 16 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-23
+- Obsolete xml-commons-apis
+
+* Thu Jan 15 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-22
+- Remove temp provides
+
+* Thu Jan 15 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-21
+- Add temp provides to fix Thermostat bulid
+
+* Thu Jan 15 2015 Michal Srb <msrb@redhat.com> - 1.1-20
+- Own %%{_javaconfdir}
+
+* Wed Jan 14 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-19
+- Revert adding directory ownership
+
+* Wed Jan 14 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-18
+- Add explicit directory attributes
+
+* Wed Jan 14 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-17
+- Own directories created by other packages
+
+* Wed Jan 14 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-16
+- Obsolete packages removed in RHSCL 2.0
+
+* Tue Jan 13 2015 Michael Simacek <msimacek@redhat.com> - 1.1-15
+- Mass rebuild 2015-01-13
+
+* Tue Jan 13 2015 Michael Simacek <msimacek@redhat.com>
+- Generates macros for directories
+
+* Wed Jan  7 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-13
+- Fix XMvn config location
+
+* Wed Jan  7 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-12
+- Install XMvn configuration
+
+* Wed Jan  7 2015 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-11
+- Don't use scl_source to enable %{scl_java_common}
+
+* Tue Jan 06 2015 Michal Srb <msrb@redhat.com> - 1.1-10
+- Add java.conf for maven30
+
+* Tue Jan 06 2015 Michael Simacek <msimacek@redhat.com> - 1.1-9
+- Mass rebuild 2015-01-06
+
+* Wed Dec 24 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-8
+- Avoid generating requires on java-headless
+
+* Thu Dec 18 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-7
+- Add eclipse.conf file
+- Add javapackages-config.json
+
+* Wed Dec 17 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-6
+- Switch to dependency generator from rh-java-common
+
+* Wed Dec 17 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-5
+- Add dependency on rh-java-common
+
+* Thu Jul 31 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-4
+- Add %%scl_maven and %%scl_prefix_maven macros to scldevel package
+- Resolves: rhbz#1125274
+
+* Mon Jun  2 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-3
+- Update README file
+
+* Mon Jun  2 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-2
+- Disable debuginfo
+
+* Thu May 29 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.1-1
+- Set metapackage version to 1.1
+
+* Tue May 27 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 3.0.5-5
+- Use python_sitelib marco
+
+* Tue May 27 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 3.0.5-4
+- Re-enable Python auto-requires
+
+* Mon May 26 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 3.0.5-3
+- Temporarly disable Python auto-requires
+
+* Mon May 26 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 3.0.5-2
+- Mass rebuild 2014-05-26
+
+* Wed Feb 19 2014 Stanislav Ochotnicky <sochotnicky@redhat.com> - 3.0.5-1
+- Remove common subpackage
+- Fix up requires in subpackages on various parts of SCL and deps
+- Own a few unowned directories
+
+* Wed Feb 19 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-22
+- Ultimately remove provides for java and java-devel
+
+* Wed Feb 19 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-21
+- Restore provides for java and java-devel
+
+* Tue Feb 18 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-20
+- Remove bogus provides
+
+* Mon Feb 17 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-19
+- Don't install java.conf for base RHEL
+
+* Thu Feb 13 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-18
+- Add requires on maven30-maven-local to maven30-runtime
+
+* Thu Feb 13 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-17
+- Install java.conf for base RHEL
+
+* Thu Feb 13 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-16
+- Add jpackage-utils provides
+
+* Wed Feb 12 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-15
+- Provide java-devel in addition to java
+
+* Wed Feb 12 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-14
+- Temporally add base RHEL to javapackages search path
+
+* Wed Feb 12 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-13
+- Set PYTHONPATH in requires/provides wrapper scripts
+
+* Wed Feb 12 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-12
+- Fix requires/provides wrapper scripts
+
+* Wed Feb 12 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-11
+- Temporarly add XMvn config variables to enable script
+
+* Tue Feb 11 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-10
+- Provide and obsolete javapackages-tools
+
+* Tue Feb 11 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-9
+- Don't install XMvn configuration files
+
+* Tue Feb 11 2014 Mikolaj Izdebski <mizdebsk@redhat.com> - 1-8
+- Avoid trailing colon in PYTHONPATH
+
+* Tue Feb 11 2014 Stanislav Ochotnicky <sochotnicky@redhat.com> - 1-7
+- Prefix PYTHONPATH with _scl_root
+
+* Tue Feb 11 2014 Stanislav Ochotnicky <sochotnicky@redhat.com> - 1-6
+- Fix PYTHONPATH to root of python_sitelib instead of subdir
+
+* Fri Feb 07 2014 Stanislav Ochotnicky <sochotnicky@redhat.com> - 1-5
+- Extend PYTHONPATH in enable scriptlet
+
+* Fri Feb 07 2014 Stanislav Ochotnicky <sochotnicky@redhat.com> - 1-4
+- Add epoch to provides to match original
+
+* Fri Feb 07 2014 Stanislav Ochotnicky <sochotnicky@redhat.com> - 1-3
+- Build-provide java 1.7.0
+
+* Wed Feb 05 2014 Stanislav Ochotnicky <sochotnicky@redhat.com> - 1-2
+- Make scl-utils requires unversioned
+
+* Wed Feb 05 2014 Stanislav Ochotnicky <sochotnicky@redhat.com> - 1-1
+- Initial maven30 scl metapackage
+