diff --git a/.munge-maven-plugin.metadata b/.munge-maven-plugin.metadata
new file mode 100644
index 0000000..273ecd6
--- /dev/null
+++ b/.munge-maven-plugin.metadata
@@ -0,0 +1 @@
+fa2f7ba99156f241fa44cf756ed53725093242a1 SOURCES/munge-maven-plugin-1.0.tar.gz
diff --git a/README.md b/README.md
deleted file mode 100644
index 0e7897f..0000000
--- a/README.md
+++ /dev/null
@@ -1,5 +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/SPECS/munge-maven-plugin.spec b/SPECS/munge-maven-plugin.spec
new file mode 100644
index 0000000..3295740
--- /dev/null
+++ b/SPECS/munge-maven-plugin.spec
@@ -0,0 +1,58 @@
+Name:           munge-maven-plugin
+Version:        1.0
+Release:        1%{?dist}
+Summary:        Munge Maven Plugin
+License:        CDDL
+URL:            http://github.com/sonatype/munge-maven-plugin
+BuildArch:      noarch
+
+Source0:        https://github.com/sonatype/munge-maven-plugin/archive/munge-maven-plugin-1.0.tar.gz
+
+BuildRequires:  maven-local
+BuildRequires:  sonatype-plugins-parent
+
+%description
+Munge is a purposely-simple Java preprocessor. It only supports
+conditional inclusion of source based on defined strings of the
+form "if[tag]", "if_not[tag]", "else[tag]", and "end[tag]".
+Unlike traditional preprocessors, comments, and formatting are all
+preserved for the included lines. This is on purpose, as the output
+of Munge will be distributed as human-readable source code.
+
+To avoid creating a separate Java dialect, the conditional tags are
+contained in Java comments. This allows one build to compile the
+source files without pre-processing, to facilitate faster incremental
+development. Other builds from the same source have their code contained
+within that comment. The format of the tags is a little verbose, so
+that the tags won't accidentally be used by other comment readers
+such as javadoc. Munge tags must be in C-style comments;
+C++-style comments may be used to comment code within a comment.
+
+Like any preprocessor, developers must be careful not to abuse its
+capabilities so that their code becomes unreadable. Please use it
+as little as possible.
+
+%package javadoc
+Summary:        API documentation for %{name}
+
+%description javadoc
+This package provides %{summary}.
+
+%prep
+%setup -q -n %{name}-%{name}-%{version}
+
+%build
+%mvn_build
+
+%install
+%mvn_install
+
+%files -f .mfiles
+%doc LICENSE README
+
+%files javadoc -f .mfiles-javadoc
+%doc LICENSE
+
+%changelog
+* Tue Sep 10 2013 Mikolaj Izdebski <mizdebsk@redhat.com> - 1.0-1
+- Initial packaging