From b25785d7597531cb214acdd9df99eac67d2e9e49 Mon Sep 17 00:00:00 2001
From: gil <puntogil@libero.it>
Date: Sat, 6 Jan 2024 00:01:56 +0100
Subject: [PATCH] rebuilt with java-openjdk support [release 1.1.1-7mamba;Wed
 Mar 23 2011]

---
 README.md                                     |   3 +
 commons-logging-1.1.1.pom                     | 504 ++++++++++++++++++
 commons-logging-api-1.1.1.pom                 | 165 ++++++
 jakarta-commons-logging-1.1.1-build_xml.patch |  32 ++
 ...mmons-logging-1.1.1-eclipse-manifest.patch |  15 +
 jakarta-commons-logging-1.1.1-javadoc.patch   |  40 ++
 ...s-logging-1.1.1-maven-release-plugin.patch |  25 +
 jakarta-commons-logging-1.1.1-skiptest.patch  |  11 +
 jakarta-commons-logging.spec                  | 204 +++++++
 maven2-2.2.0-settings.xml                     | 245 +++++++++
 10 files changed, 1244 insertions(+)
 create mode 100644 commons-logging-1.1.1.pom
 create mode 100644 commons-logging-api-1.1.1.pom
 create mode 100644 jakarta-commons-logging-1.1.1-build_xml.patch
 create mode 100644 jakarta-commons-logging-1.1.1-eclipse-manifest.patch
 create mode 100644 jakarta-commons-logging-1.1.1-javadoc.patch
 create mode 100644 jakarta-commons-logging-1.1.1-maven-release-plugin.patch
 create mode 100644 jakarta-commons-logging-1.1.1-skiptest.patch
 create mode 100644 jakarta-commons-logging.spec
 create mode 100644 maven2-2.2.0-settings.xml

diff --git a/README.md b/README.md
index fe59e6c..32b2b07 100644
--- a/README.md
+++ b/README.md
@@ -1,2 +1,5 @@
 # jakarta-commons-logging
 
+The commons-logging package provides a simple, component oriented interface (org.apache.commons.logging.Log) together with wrappers for logging systems. The user can choose at runtime which system they want to use. In addition, a small number of basic implementations are provided to allow users to use the package standalone.
+commons-logging was heavily influenced by Avalon's Logkit and Log4J. The commons-logging abstraction is meant to minimize the differences between the two, and to allow a developer to not tie himself to a particular logging implementation.
+
diff --git a/commons-logging-1.1.1.pom b/commons-logging-1.1.1.pom
new file mode 100644
index 0000000..e4b4503
--- /dev/null
+++ b/commons-logging-1.1.1.pom
@@ -0,0 +1,504 @@
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one or more
+   contributor license agreements.  See the NOTICE file distributed with
+   this work for additional information regarding copyright ownership.
+   The ASF licenses this file to You under the Apache License, Version 2.0
+   (the "License"); you may not use this file except in compliance with
+   the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+-->
+
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
+  <!--
+    - Note that due to the special requirements of logging unit-tests, most
+    - tests are executed in the "integration-test" phase rather than the
+    - "test" phase. Please run "mvn integration-test" to run the full suite of
+    - available unit tests.
+    -->
+  <parent>
+    <groupId>org.apache.commons</groupId>
+    <artifactId>commons-parent</artifactId>
+    <version>5</version>
+  </parent>
+  <modelVersion>4.0.0</modelVersion>
+  <groupId>commons-logging</groupId>
+  <artifactId>commons-logging</artifactId>
+  <name>Commons Logging</name>
+  <version>1.1.1</version>
+  <description>Commons Logging is a thin adapter allowing configurable bridging to other,
+    well known logging systems.</description>
+  <url>http://commons.apache.org/logging</url>
+
+  <issueManagement>
+    <system>JIRA</system>
+    <url>http://issues.apache.org/jira/browse/LOGGING</url>
+  </issueManagement>
+
+  <inceptionYear>2001</inceptionYear>
+
+  <developers>
+    <developer>
+      <id>morgand</id>
+      <name>Morgan Delagrange</name>
+      <email>morgand at apache dot org</email>
+      <organization>Apache</organization>
+      <roles>
+        <role>Java Developer</role>
+      </roles>
+    </developer>
+    <developer>
+      <id>rwaldhoff</id>
+      <name>Rodney Waldhoff</name>
+      <email>rwaldhoff at apache org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>craigmcc</id>
+      <name>Craig McClanahan</name>
+      <email>craigmcc at apache org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>sanders</id>
+      <name>Scott Sanders</name>
+      <email>sanders at apache dot org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>rdonkin</id>
+      <name>Robert Burrell Donkin</name>
+      <email>rdonkin at apache dot org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>donaldp</id>
+      <name>Peter Donald</name>
+      <email>donaldp at apache dot org</email>
+    </developer>
+    <developer>
+      <id>costin</id>
+      <name>Costin Manolache</name>
+      <email>costin at apache dot org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>rsitze</id>
+      <name>Richard Sitze</name>
+      <email>rsitze at apache dot org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>baliuka</id>
+      <name>Juozas Baliuka</name>
+      <email>baliuka@apache.org</email>
+      <roles>
+        <role>Java Developer</role>
+      </roles>
+    </developer>
+    <developer>
+      <id>skitching</id>
+      <name>Simon Kitching</name>
+      <email>skitching@apache.org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>dennisl</id>
+      <name>Dennis Lundberg</name>
+      <email>dennisl@apache.org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>bstansberry</id>
+      <name>Brian Stansberry</name>
+    </developer>
+  </developers>
+
+  <scm>
+    <connection>scm:svn:http://svn.apache.org/repos/asf/commons/proper/logging/tags/commons-logging-1.1.1</connection>
+    <developerConnection>scm:svn:https://svn.apache.org/repos/asf/commons/proper/logging/tags/commons-logging-1.1.1</developerConnection>
+    <url>http://svn.apache.org/repos/asf/commons/proper/logging/tags/commons-logging-1.1.1</url>
+  </scm>
+
+  <build>
+    <sourceDirectory>src/java</sourceDirectory>
+    <testSourceDirectory>src/test</testSourceDirectory>
+
+    <testResources>
+      <testResource>
+        <directory>src/test</directory>
+        <filtering>false</filtering>
+        <includes>
+          <include>**/*.properties</include>
+        </includes>
+      </testResource>
+    </testResources>
+
+    <plugins>
+
+      <!--
+        - The custom test framework requires the unit test code to be
+        - in a jarfile so it can control its place in the classpath.
+        -->
+      <plugin>      
+        <groupId>org.apache.maven.plugins</groupId>
+        <artifactId>maven-jar-plugin</artifactId>
+        <configuration>
+          <archive>
+            <manifestFile>src/conf/MANIFEST.MF</manifestFile>
+          </archive>
+        </configuration>
+        <executions>
+          <execution>
+            <id>testjar</id>
+            <phase>package</phase>
+            <goals>
+              <goal>test-jar</goal>
+            </goals>
+            <configuration>
+              <jarName>commons-logging</jarName>
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+
+      <plugin>
+        <!--
+          - We want to create four jarfiles from this project: normal, tests, api
+          - and adapters. The first two are handled by the normal jar:jar target.
+          - Alas, the standard jar plugin doesn't have includes/excludes support
+          - in version 2.0, so antrun is used to create the other ones.
+          -->
+        <groupId>org.apache.maven.plugins</groupId>
+        <artifactId>maven-antrun-plugin</artifactId>
+        <version>1.1</version>
+        <executions>
+          <execution>
+            <id>apijar</id>
+            <phase>package</phase>
+            <configuration>
+              <tasks>
+                <property name="workdir" value="${project.build.directory}/rejar" />
+                <property name="target" value="${project.artifactId}-api-${project.version}" />
+
+                <delete dir="${workdir}" failonerror="false" />
+                <mkdir dir="${workdir}" />
+
+                <unjar src="${project.build.directory}/${project.build.finalName}.jar" dest="${workdir}" />
+                <jar basedir="${workdir}" destfile="${project.build.directory}/${target}.jar" manifest="${basedir}/src/conf/MANIFEST.MF">
+                  <exclude name="org/apache/commons/logging/impl/Log4J*" />
+                  <exclude name="org/apache/commons/logging/impl/Avalon*" />
+                  <exclude name="org/apache/commons/logging/impl/Jdk13*" />
+                  <exclude name="org/apache/commons/logging/impl/LogKit*" />
+                  <exclude name="org/apache/commons/logging/impl/Servlet*" />
+                </jar>
+              </tasks>
+            </configuration>
+            <goals>
+              <goal>run</goal>
+            </goals>
+          </execution>
+          <execution>
+            <id>adaptersjar</id>
+            <phase>package</phase>
+            <configuration>
+              <tasks>
+                <property name="workdir" value="${project.build.directory}/rejar" />
+                <property name="target" value="${project.artifactId}-adapters-${project.version}" />
+
+                <delete dir="${workdir}" failonerror="false" />
+                <mkdir dir="${workdir}" />
+
+                <unjar src="${project.build.directory}/${project.build.finalName}.jar" dest="${workdir}" />
+                <jar basedir="${workdir}" destfile="${project.build.directory}/${target}.jar" manifest="${basedir}/src/conf/MANIFEST.MF">
+                  <exclude name="org/apache/commons/logging/*" />
+                  <exclude name="org/apache/commons/logging/impl/WeakHashtable*" />
+                  <exclude name="org/apache/commons/logging/impl/LogFactoryImpl*" />
+                </jar>
+              </tasks>
+            </configuration>
+            <goals>
+              <goal>run</goal>
+            </goals>
+          </execution>
+          <execution>
+            <id>site.resources</id>
+            <phase>site</phase>
+            <configuration>
+              <tasks>
+                <copy todir="${project.reporting.outputDirectory}">
+                  <fileset dir="${basedir}">
+                    <include name="RELEASE-NOTES.txt" />
+                  </fileset>
+                  <!--
+                    - The logo should be moved to
+                    - ${basedir}/src/site/resources/images
+                    - once we can drop support for the Maven 1 site.
+                    - When that is done this section can be removed.
+                    -->
+                  <fileset dir="${basedir}/xdocs">
+                    <include name="images/logo.png" />
+                  </fileset>
+                </copy>
+              </tasks>
+            </configuration>
+            <goals>
+              <goal>run</goal>
+            </goals>
+          </execution>
+        </executions>
+      </plugin> 
+
+      <plugin>
+        <!--
+          - Attach the adapters and api jars to the normal artifact. This way
+          - they will be deployed when the normal artifact is deployed.
+          -->
+        <groupId>org.codehaus.mojo</groupId>
+        <artifactId>build-helper-maven-plugin</artifactId>
+        <version>1.0</version>
+        <executions>
+          <execution>
+            <id>attach-artifacts</id>
+            <phase>package</phase>
+            <goals>
+              <goal>attach-artifact</goal>
+            </goals>
+            <configuration>
+              <artifacts>
+                <artifact>
+                  <file>${project.build.directory}/${project.artifactId}-adapters-${project.version}.jar</file>
+                  <type>jar</type>
+                  <classifier>adapters</classifier>
+                </artifact>
+                <artifact>
+                  <file>${project.build.directory}/${project.artifactId}-api-${project.version}.jar</file>
+                  <type>jar</type>
+                  <classifier>api</classifier>
+                </artifact>
+              </artifacts>
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+
+      <plugin>
+        <groupId>org.apache.maven.plugins</groupId>
+        <artifactId>maven-release-plugin</artifactId>
+        <version>2.0-beta-6</version>
+        <configuration>
+          <!--
+            - The site needs to be built prior to deploy,
+            - because it is included in the assembly.
+            -->
+          <goals>site deploy</goals>
+          <!-- Pass these arguments to the deploy plugin. -->
+          <arguments>-Prelease</arguments>
+        </configuration>
+      </plugin>
+
+      <plugin>
+        <!--
+          - Many of JCL's tests use tricky techniques to place the generated
+          - JCL jarfiles on the classpath in various configurations. This means
+          - that the tests must be run *after* the "package" build phase. The
+          - normal test phase is therefore disabled here, and the test plugin
+          - rebound to the "integration-test" phase instead.
+          -->
+        <groupId>org.apache.maven.plugins</groupId>
+        <artifactId>maven-surefire-plugin</artifactId>
+        <configuration>
+          <includes>
+            <include>**/AvalonLoggerTestCase.java</include>
+          </includes>
+        </configuration>
+
+        <executions>
+          <execution>
+            <id>integration-test</id>
+            <phase>integration-test</phase>
+            <goals>
+              <goal>test</goal>
+            </goals>
+            <configuration>
+              <includes>
+                <include>**/*TestCase.java</include>
+              </includes>
+              <systemProperties>
+                <!--
+                <property>
+                  <name>org.apache.commons.logging.diagnostics.dest</name>
+                  <value>STDOUT</value>
+                </property>
+                -->
+                <property>
+                  <name>commons-logging</name>
+                  <value>target/${project.build.finalName}.jar</value>
+                </property>
+                <property>
+                  <name>commons-logging-api</name>
+                  <value>target/${project.artifactId}-api-${project.version}.jar</value>
+                </property>
+                <property>
+                  <name>commons-logging-adapters</name>
+                  <value>target/${project.artifactId}-adapters-${project.version}.jar</value>
+                </property>
+                <property>
+                  <name>testclasses</name>
+                  <value>target/commons-logging-tests.jar</value>
+                </property>
+              </systemProperties>
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+
+      <plugin>
+        <groupId>org.apache.maven.plugins</groupId>
+        <artifactId>maven-assembly-plugin</artifactId>
+        <version>2.2-beta-1</version>
+        <configuration>
+          <appendAssemblyId>false</appendAssemblyId>
+          <!-- Do not deploy the assemblies to the repository. -->
+          <attach>false</attach>
+          <descriptors>
+            <descriptor>src/assembly/assembly.xml</descriptor>
+          </descriptors>
+          <tarLongFileMode>gnu</tarLongFileMode>
+        </configuration>
+      </plugin>
+
+      <plugin>
+        <groupId>org.apache.maven.plugins</groupId>
+        <artifactId>maven-site-plugin</artifactId>
+        <version>2.0-beta-5</version>
+      </plugin>
+
+    </plugins>
+  </build>
+  
+  <profiles>
+    <!-- This profile can be removed when we update to commons-parent-5 -->
+    <profile>
+      <id>ci</id>
+      <distributionManagement>
+        <repository>
+          <id>apache.snapshots</id>
+          <name>Apache Development Snapshot Repository</name>
+          <url>${commons.deployment.protocol}://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>
+        </repository>
+        <snapshotRepository>
+          <id>apache.snapshots</id>
+          <name>Apache Development Snapshot Repository</name>
+          <url>${commons.deployment.protocol}://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>
+        </snapshotRepository>
+      </distributionManagement>
+    </profile>
+    <profile>
+      <id>release</id>
+      <build>
+        <plugins>
+          <plugin>
+            <!-- Create the assemblies automatically during release. -->
+            <groupId>org.apache.maven.plugins</groupId>
+            <artifactId>maven-assembly-plugin</artifactId>
+            <executions>
+              <execution>
+                <goals>
+                  <goal>single</goal>
+                </goals>
+                <phase>package</phase>
+              </execution>
+            </executions>
+          </plugin>
+          <plugin>
+            <groupId>org.apache.maven.plugins</groupId>
+            <artifactId>maven-deploy-plugin</artifactId>
+            <version>2.3</version>
+            <configuration>
+              <!-- Pick up this configuration from settings.xml. -->
+              <altDeploymentRepository>${deploy.altRepository}</altDeploymentRepository>
+              <updateReleaseInfo>true</updateReleaseInfo>
+            </configuration>
+          </plugin>
+        </plugins>
+      </build>
+    </profile>
+  </profiles>
+
+  <dependencies>
+    <dependency>
+      <groupId>junit</groupId>
+      <artifactId>junit</artifactId>
+      <version>3.8.1</version>
+      <scope>test</scope>
+    </dependency>
+    <dependency>
+      <groupId>log4j</groupId>
+      <artifactId>log4j</artifactId>
+      <version>1.2.12</version>
+      <optional>true</optional>
+    </dependency>
+    <dependency>
+      <groupId>logkit</groupId>
+      <artifactId>logkit</artifactId>
+      <version>1.0.1</version>
+      <optional>true</optional>
+    </dependency>
+    <dependency>
+      <groupId>avalon-framework</groupId>
+      <artifactId>avalon-framework</artifactId>
+      <version>4.1.3</version>
+      <optional>true</optional>
+    </dependency>
+    <dependency>
+      <groupId>javax.servlet</groupId>
+      <artifactId>servlet-api</artifactId>
+      <version>2.3</version>
+      <scope>provided</scope>
+      <optional>true</optional>
+    </dependency>
+  </dependencies>
+
+  <reporting>
+    <plugins>
+      <!--
+      <plugin>
+        <groupId>org.apache.maven.plugins</groupId>
+        <artifactId>maven-checkstyle-plugin</artifactId>
+        <configuration>
+          <configLocation>checkstyle.xml</configLocation>
+        </configuration>
+      </plugin>
+      -->
+      <plugin>
+        <groupId>org.codehaus.mojo</groupId>
+        <artifactId>clirr-maven-plugin</artifactId>
+        <version>2.1.1</version>
+      </plugin>
+      <plugin>
+        <groupId>org.codehaus.mojo</groupId>
+        <artifactId>jdepend-maven-plugin</artifactId>
+        <version>2.0-beta-1</version>
+      </plugin>
+    </plugins>
+  </reporting>
+
+  <distributionManagement>
+    <site>
+      <id>apache.website</id>
+      <url>${commons.deployment.protocol}://people.apache.org/www/commons.apache.org/logging/</url>
+    </site>
+  </distributionManagement>
+
+  <properties>
+    <maven.compile.source>1.2</maven.compile.source>
+    <maven.compile.target>1.1</maven.compile.target>
+  </properties>
+</project>
diff --git a/commons-logging-api-1.1.1.pom b/commons-logging-api-1.1.1.pom
new file mode 100644
index 0000000..3929b41
--- /dev/null
+++ b/commons-logging-api-1.1.1.pom
@@ -0,0 +1,165 @@
+<?xml version="1.0" encoding="UTF-8"?><project>
+  <modelVersion>4.0.0</modelVersion>
+  <groupId>commons-logging</groupId>
+  <artifactId>commons-logging-api</artifactId>
+  <name>Logging</name>
+  <version>1.1.1</version>
+  <description>Commons Logging is a thin adapter allowing configurable bridging to other,
+    well known logging systems.</description>
+  <url>http://jakarta.apache.org/commons/logging/</url>
+  <issueManagement>
+    <url>http://issues.apache.org/jira/browse/LOGGING</url>
+  </issueManagement>
+  <ciManagement>
+    <notifiers>
+      <notifier>
+        <configuration>
+          <address>commons-dev@jakarta.apache.org</address>
+        </configuration>
+      </notifier>
+    </notifiers>
+  </ciManagement>
+  <inceptionYear>2001</inceptionYear>
+  <mailingLists>
+    <mailingList>
+      <name>Commons Dev List</name>
+      <subscribe>commons-dev-subscribe@jakarta.apache.org</subscribe>
+      <unsubscribe>commons-dev-unsubscribe@jakarta.apache.org</unsubscribe>
+      <archive>http://mail-archives.apache.org/mod_mbox/jakarta-commons-dev/</archive>
+    </mailingList>
+    <mailingList>
+      <name>Commons User List</name>
+      <subscribe>commons-user-subscribe@jakarta.apache.org</subscribe>
+      <unsubscribe>commons-user-unsubscribe@jakarta.apache.org</unsubscribe>
+      <archive>http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/</archive>
+    </mailingList>
+  </mailingLists>
+  <developers>
+    <developer>
+      <id>morgand</id>
+      <name>Morgan Delagrange</name>
+      <email>morgand at apache dot org</email>
+      <organization>Apache</organization>
+      <roles>
+        <role>Java Developer</role>
+      </roles>
+    </developer>
+    <developer>
+      <id>rwaldhoff</id>
+      <name>Rodney Waldhoff</name>
+      <email>rwaldhoff at apache org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>craigmcc</id>
+      <name>Craig McClanahan</name>
+      <email>craigmcc at apache org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>sanders</id>
+      <name>Scott Sanders</name>
+      <email>sanders at apache dot org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>rdonkin</id>
+      <name>Robert Burrell Donkin</name>
+      <email>rdonkin at apache dot org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>donaldp</id>
+      <name>Peter Donald</name>
+      <email>donaldp at apache dot org</email>
+      <organization></organization>
+    </developer>
+    <developer>
+      <id>costin</id>
+      <name>Costin Manolache</name>
+      <email>costin at apache dot org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>rsitze</id>
+      <name>Richard Sitze</name>
+      <email>rsitze at apache dot org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>baliuka</id>
+      <name>Juozas Baliuka</name>
+      <email>baliuka@apache.org</email>
+      <organization></organization>
+      <roles>
+        <role>Java Developer</role>
+      </roles>
+    </developer>
+    <developer>
+      <id>skitching</id>
+      <name>Simon Kitching</name>
+      <email>skitching@apache.org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>dennisl</id>
+      <name>Dennis Lundberg</name>
+      <email>dennisl@apache.org</email>
+      <organization>Apache Software Foundation</organization>
+    </developer>
+    <developer>
+      <id>bstansberry</id>
+      <name>Brian Stansberry</name>
+    </developer>
+  </developers>
+  <licenses>
+    <license>
+      <name>The Apache Software License, Version 2.0</name>
+      <url>/LICENSE.txt</url>
+    </license>
+  </licenses>
+  <scm>
+    <connection>scm:svn:http://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk/</connection>
+    <url>http://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk/</url>
+  </scm>
+  <organization>
+    <name>The Apache Software Foundation</name>
+    <url>http://jakarta.apache.org</url>
+  </organization>
+  <build>
+    <sourceDirectory>src/java</sourceDirectory>
+    <testSourceDirectory>src/test</testSourceDirectory>
+    <plugins>
+      <plugin>
+        <artifactId>maven-xdoc-plugin</artifactId>
+        <version>1.9.2</version>
+        <configuration>
+          <optional>true</optional>
+          <comment>&lt;strong>Site Only&lt;/strong> - v1.9.2 (minimum)</comment>
+        </configuration>
+      </plugin>
+    </plugins>
+  </build>
+  <dependencies>
+    <dependency>
+      <groupId>junit</groupId>
+      <artifactId>junit</artifactId>
+      <version>3.8.1</version>
+      <scope>test</scope>
+      <optional>true</optional>
+    </dependency>
+  </dependencies>
+  <distributionManagement>
+    <repository>
+      <id>default</id>
+      <name>Default Repository</name>
+      <url>file:///www/jakarta.apache.org/builds/jakarta-commons/logging/</url>
+    </repository>
+    <site>
+      <id>default</id>
+      <name>Default Site</name>
+      <url>scp://people.apache.org//www/jakarta.apache.org/commons/logging/</url>
+    </site>
+    <status>converted</status>
+  </distributionManagement>
+</project>
\ No newline at end of file
diff --git a/jakarta-commons-logging-1.1.1-build_xml.patch b/jakarta-commons-logging-1.1.1-build_xml.patch
new file mode 100644
index 0000000..84883d1
--- /dev/null
+++ b/jakarta-commons-logging-1.1.1-build_xml.patch
@@ -0,0 +1,32 @@
+--- commons-logging-1.1.1-src/build.xml	2007-11-22 00:27:52.000000000 +0100
++++ commons-logging-1.1.1-src/build.xml-gil	2009-03-02 10:24:06.000000000 +0100
+@@ -77,7 +77,8 @@
+   <property name="log4j12.jar"             value="log4j-1.2.12.jar"/>
+   <property name="log4j13.jar"             value="log4j-1.3.0.jar"/>
+   <property name="logkit.jar"              value="logkit-1.0.1.jar"/>
+-  <property name="avalon-framework.jar"    value="avalon-framework-4.1.3.jar"/>
++  <property name="avalon-framework-api.jar"    value="avalon-framework-api-4.3.jar"/>
++  <property name="avalon-framework-impl.jar"    value="avalon-framework-impl-4.3.jar"/>
+   <property name="servletapi.jar"          value="servletapi-2.3.jar"/>
+ 
+ 
+@@ -146,7 +147,8 @@
+     <pathelement location="${build.home}/classes"/>
+     <pathelement location="${junit.jar}"/>
+     <pathelement location="${logkit.jar}"/>
+-    <pathelement location="${avalon-framework.jar}"/>
++    <pathelement location="${avalon-framework-api.jar}"/>
++    <pathelement location="${avalon-framework-impl.jar}"/>
+     <pathelement location="${servletapi.jar}"/>
+   </path>
+ 
+@@ -167,7 +169,8 @@
+     <pathelement location="${build.home}/tests"/>
+     <pathelement location="${junit.jar}"/>
+     <pathelement location="${logkit.jar}"/>
+-    <pathelement location="${avalon-framework.jar}"/>
++    <pathelement location="${avalon-framework-api.jar}"/>
++    <pathelement location="${avalon-framework-impl.jar}"/>
+     <pathelement location="${conf.home}"/>
+     <pathelement location="${servletapi.jar}"/>
+   </path>
diff --git a/jakarta-commons-logging-1.1.1-eclipse-manifest.patch b/jakarta-commons-logging-1.1.1-eclipse-manifest.patch
new file mode 100644
index 0000000..26110ea
--- /dev/null
+++ b/jakarta-commons-logging-1.1.1-eclipse-manifest.patch
@@ -0,0 +1,15 @@
+--- src/conf/MANIFEST.MF	2007-11-22 00:27:52.000000000 +0100
++++ src/conf/MANIFEST.MF-gil	2010-07-21 01:30:21.000000000 +0200
+@@ -6,3 +6,12 @@
+ Implementation-Vendor-Id: org.apache
+ Implementation-Vendor: Apache Software Foundation
+ Implementation-Version: 1.1.1
++Bundle-ManifestVersion: 2
++Export-Package: org.apache.commons.logging;version="1.1.1",org.apache.
++ commons.logging.impl;version="1.1.1"
++Bundle-Version: 1.1.1.v20080605-1930
++Bundle-SymbolicName: org.apache.commons.logging
++Bundle-Name: Apache Commons Logging Plug-in
++Bundle-RequiredExecutionEnvironment: CDC-1.0/Foundation-1.0,J2SE-1.3
++Bundle-Localization: plugin
++Bundle-Vendor: Apache Software Foundation
diff --git a/jakarta-commons-logging-1.1.1-javadoc.patch b/jakarta-commons-logging-1.1.1-javadoc.patch
new file mode 100644
index 0000000..9500183
--- /dev/null
+++ b/jakarta-commons-logging-1.1.1-javadoc.patch
@@ -0,0 +1,40 @@
+--- build.xml	2010-10-30 21:21:49.000000000 +0200
++++ build.xml-gil	2010-10-30 21:16:19.000000000 +0200
+@@ -640,6 +640,37 @@
+   </target>
+   
+ 
++  <target name="javadoc" description="Generates the Javadoc of the application">
++          <mkdir dir='${build.home}/docs/apidocs'/>
++	  <tstamp>
++		  <format property="year" pattern="yyyy" />
++	  </tstamp>
++	  <javadoc sourcepath="${source.home}:${test.home}" 
++			  packagenames="*" 
++			  destdir="${build.home}/docs/apidocs" 
++			  access="protected" 
++			  old="false" 
++			  overview="${source.home}/org/apache/commons/logging/package.html"
++			  verbose="false" 
++			  version="true" 
++			  use="true" 
++			  author="true" 
++			  splitindex="false" 
++			  nodeprecated="false" 
++			  nodeprecatedlist="false" 
++			  notree="false" 
++			  noindex="false" 
++			  nohelp="false" 
++			  nonavbar="false" 
++			  serialwarn="false" 
++			  charset="ISO-8859-1" 
++			  linksource="false" 
++			  breakiterator="false">
++		  <doctitle><![CDATA[<h1>Commons Logging ${component.version} API</h1>]]></doctitle>
++		  <bottom><![CDATA[<small>Copyright &#169; 2001-${year} <a href="http://commons.apache.org/">The Apache Software Foundation</a>. All Rights Reserved.</small>]]></bottom>
++	  </javadoc>
++  </target>
++
+   <target name="dist" depends="all,maven-docs-warning"
+      description="Create binary distribution">
+   
diff --git a/jakarta-commons-logging-1.1.1-maven-release-plugin.patch b/jakarta-commons-logging-1.1.1-maven-release-plugin.patch
new file mode 100644
index 0000000..57f980e
--- /dev/null
+++ b/jakarta-commons-logging-1.1.1-maven-release-plugin.patch
@@ -0,0 +1,25 @@
+--- pom.xml	2007-11-22 00:27:52.000000000 +0100
++++ pom.xml-gil	2010-07-21 01:24:52.000000000 +0200
+@@ -307,22 +307,6 @@
+         </executions>
+       </plugin>
+ 
+-      <plugin>
+-        <groupId>org.apache.maven.plugins</groupId>
+-        <artifactId>maven-release-plugin</artifactId>
+-        <version>2.0-beta-6</version>
+-        <configuration>
+-          <!--
+-            - The site needs to be built prior to deploy,
+-            - because it is included in the assembly.
+-            -->
+-          <goals>site deploy</goals>
+-          <!-- Pass these arguments to the deploy plugin. -->
+-          <arguments>-Prelease</arguments>
+-        </configuration>
+-      </plugin>
+-
+-      <plugin>
+         <!--
+           - Many of JCL's tests use tricky techniques to place the generated
+           - JCL jarfiles on the classpath in various configurations. This means
diff --git a/jakarta-commons-logging-1.1.1-skiptest.patch b/jakarta-commons-logging-1.1.1-skiptest.patch
new file mode 100644
index 0000000..eb5479a
--- /dev/null
+++ b/jakarta-commons-logging-1.1.1-skiptest.patch
@@ -0,0 +1,11 @@
+--- build.xml	2011-03-23 10:19:06.000000000 +0100
++++ build.xml-gil	2011-03-23 10:23:17.000000000 +0100
+@@ -628,7 +628,7 @@
+   </target>
+ 
+ 
+-  <target name="all" depends="clean,compile,test"
++  <target name="all" depends="clean,compile"
+    description="Clean and compile all components"/>
+ 
+ 
diff --git a/jakarta-commons-logging.spec b/jakarta-commons-logging.spec
new file mode 100644
index 0000000..f6531ab
--- /dev/null
+++ b/jakarta-commons-logging.spec
@@ -0,0 +1,204 @@
+%define        javahome          %{_jvmdir}/jdk
+
+Name:          jakarta-commons-logging
+Version:       1.1.1
+Release:       7mamba
+Summary:       Jakarta Commons Logging Package
+Group:         Development/Libraries/Java
+Vendor:        openmamba
+Distribution:  openmamba
+Packager:      Silvan Calarco <silvan.calarco@mambasoft.it>
+URL:           http://commons.apache.org/logging/
+Source0:       http://www.apache.org/dist/commons/logging/source/commons-logging-%{version}-src.tar.gz
+Source1:       http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-logging/commons-logging/%{version}/commons-logging-%{version}.pom
+Source2:       commons-logging-api-%{version}.pom
+Source3:       maven2-2.2.0-settings.xml
+Patch0:        jakarta-commons-logging-1.1.1-build_xml.patch
+Patch1:        jakarta-commons-logging-1.1.1-maven-release-plugin.patch
+Patch2:        jakarta-commons-logging-1.1.1-eclipse-manifest.patch
+Patch3:        jakarta-commons-logging-1.1.1-javadoc.patch
+Patch4:        jakarta-commons-logging-1.1.1-skiptest.patch
+License:       Apache License Version 2.0
+## AUTOBUILDREQ-BEGIN
+## AUTOBUILDREQ-END
+BuildRequires: apache-ant
+BuildRequires: apache-ant-junit
+BuildRequires: apache-log4j
+#%if "%{stage1}" != "1"
+#BuildRequires: java-excalibur-avalon-logkit
+#BuildRequires: java-excalibur-avalon-framework
+#BuildRequires: java-excalibur-avalon-framework-api
+#BuildRequires: java-excalibur-avalon-framework-impl
+#%endif
+#BuildRequires: java-servletapi4
+#BuildRequires: java-junit3
+BuildRequires: jpackage-utils
+
+%description
+The commons-logging package provides a simple, component oriented interface (org.apache.commons.logging.Log) together with wrappers for logging systems. The user can choose at runtime which system they want to use. In addition, a small number of basic implementations are provided to allow users to use the package standalone. 
+commons-logging was heavily influenced by Avalon's Logkit and Log4J. The commons-logging abstraction is meant to minimize the differences between the two, and to allow a developer to not tie himself to a particular logging implementation.
+
+%package javadoc
+Group:          Documentation
+Summary:        Javadoc for %{name}
+
+%description javadoc
+Commons Logging is a thin adapter allowing configurable bridging to other, well known logging systems
+
+This package contains javadoc for %{name}.
+
+%prep
+%setup -q -n commons-logging-%{version}-src
+%patch0 -p1
+%patch1
+%patch2
+%patch3
+%patch4 -p0
+
+for j in $(find . -name "*.jar"); do
+  mv $j ${j}.no
+done
+
+%build
+export JAVA_HOME=%{javahome}
+export MAVEN_REPO_LOCAL=$PWD/.m2/repository
+mkdir -p $MAVEN_REPO_LOCAL
+
+cat > build.properties << EOF
+junit.jar=$(build-classpath junit-3.8.2)
+log4j.jar=$(build-classpath log4j)
+log4j12.jar=$(build-classpath log4j)
+servletapi.jar=$(build-classpath servletapi4)
+%if "%{stage1}" != "1"
+logkit.jar=$(build-classpath excalibur/avalon-logkit)
+avalon-framework-api.jar=$(build-classpath excalibur/avalon-framework-api)
+avalon-framework-impl.jar=$(build-classpath excalibur/avalon-framework-impl)
+avalon-framework.jar=$(build-classpath excalibur/avalon-framework)
+%endif
+EOF
+export CLASSPATH=$(build-classpath junit-3.8.2 ant/ant-junit)
+ant all compile.tests
+
+%if "%{stage1}" != "1"
+CLASSPATH=$CLASSPATH:$(build-classpath excalibur/avalon-framework excalibur/avalon-framework-api)
+CLASSPATH=$CLASSPATH:$(build-classpath excalibur/avalon-framework-impl excalibur/avalon-logkit)
+%endif
+CLASSPATH=$CLASSPATH:$(build-classpath log4j servletapi4):target/classes:target/tests
+ant javadoc
+
+%install
+[ "%{buildroot}" != / ] && rm -rf "%{buildroot}"
+
+mkdir -p %{buildroot}%{_javadir}
+
+install -p -m 644 target/commons-logging-%{version}-SNAPSHOT.jar \
+  %{buildroot}%{_javadir}/jakarta-commons-logging-%{version}.jar
+install -p -m 644 target/commons-logging-adapters-%{version}-SNAPSHOT.jar \
+  %{buildroot}%{_javadir}/jakarta-commons-logging-adapters-%{version}.jar
+install -p -m 644 target/commons-logging-api-%{version}-SNAPSHOT.jar \
+  %{buildroot}%{_javadir}/jakarta-commons-logging-api-%{version}.jar
+install -p -m 644 target/commons-logging-appender.jar \
+  %{buildroot}%{_javadir}/jakarta-commons-logging-appender-%{version}.jar
+install -p -m 644 target/commons-logging-tests.jar \
+  %{buildroot}%{_javadir}/jakarta-commons-logging-tests-%{version}.jar
+install -p -m 644 target/commons-logging-wrapper.jar \
+  %{buildroot}%{_javadir}/jakarta-commons-logging-wrapper-%{version}.jar
+
+%add_to_maven_depmap commons-logging commons-logging %{version} JPP commons-logging
+%add_to_maven_depmap commons-logging commons-logging-api %{version} JPP commons-logging-api
+# http://jira.codehaus.org/browse/MEV-591?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
+#_to_maven_depmap commons-logging commons-logging-adapters %{version} JPP commons-logging-adapters
+
+mkdir -p %{buildroot}%{_datadir}/maven2/poms
+install -pm 644 pom.xml %{buildroot}%{_datadir}/maven2/poms/JPP-commons-logging.pom
+install -pm 644 %{SOURCE2} %{buildroot}%{_datadir}/maven2/poms/JPP-commons-logging-api.pom
+
+(
+  cd %{buildroot}%{_javadir}
+  for jar in *-%{version}*; do
+    ln -sf ${jar} `echo $jar| sed "s|jakarta-||g"`
+  done
+)
+
+(
+  cd %{buildroot}%{_javadir}
+  for jar in *-%{version}*; do
+    ln -sf ${jar} `echo $jar| sed "s|-%{version}||g"`
+  done
+)
+
+%if "%{stage1}" != "1"
+mkdir -p %{buildroot}%{_javadocdir}/jakarta-commons-logging-%{version}
+cp -pr target/docs/apidocs/* %{buildroot}%{_javadocdir}/%{name}-%{version}
+ln -sf %{name}-%{version} %{buildroot}%{_javadocdir}/%{name}
+%endif
+
+#%{_bindir}/aot-compile-rpm
+
+%clean
+[ "%{buildroot}" != / ] && rm -rf "%{buildroot}"
+
+%post
+%update_maven_depmap
+
+%postun
+%update_maven_depmap
+
+%files
+%defattr(-,root,root)
+%{_javadir}/commons-logging-%{version}.jar
+%{_javadir}/commons-logging-adapters-%{version}.jar
+%{_javadir}/commons-logging-api-%{version}.jar
+%{_javadir}/jakarta-commons-logging-%{version}.jar
+%{_javadir}/jakarta-commons-logging-adapters-%{version}.jar
+%{_javadir}/jakarta-commons-logging-api-%{version}.jar
+%{_javadir}/commons-logging-adapters.jar
+%{_javadir}/commons-logging-api.jar
+%{_javadir}/commons-logging.jar
+%{_javadir}/jakarta-commons-logging-adapters.jar
+%{_javadir}/jakarta-commons-logging-api.jar
+%{_javadir}/jakarta-commons-logging.jar
+%{_javadir}/commons-logging-appender-%{version}.jar
+%{_javadir}/commons-logging-appender.jar
+%{_javadir}/commons-logging-tests-%{version}.jar
+%{_javadir}/commons-logging-tests.jar
+%{_javadir}/commons-logging-wrapper-%{version}.jar
+%{_javadir}/commons-logging-wrapper.jar
+%{_javadir}/jakarta-commons-logging-appender-%{version}.jar
+%{_javadir}/jakarta-commons-logging-appender.jar
+%{_javadir}/jakarta-commons-logging-tests-%{version}.jar
+%{_javadir}/jakarta-commons-logging-tests.jar
+%{_javadir}/jakarta-commons-logging-wrapper-%{version}.jar
+%{_javadir}/jakarta-commons-logging-wrapper.jar
+%{_datadir}/maven2/poms
+%{_mavendepmapfragdir}
+%doc PROPOSAL.html STATUS.html LICENSE.txt RELEASE-NOTES.txt
+
+%if "%{stage1}" != "1"
+%files javadoc
+%defattr(-,root,root)
+%{_javadocdir}/%{name}-%{version}
+%{_javadocdir}/%{name}
+%endif
+
+%changelog
+* Wed Mar 23 2011 gil <puntogil@libero.it> 1.1.1-7mamba
+- rebuilt with java-openjdk support
+
+* Sat Oct 30 2010 gil <puntogil@libero.it> 1.1.1-6mamba
+- rebuilt devel
+
+* Mon Jan 11 2010 gil <puntogil@libero.it> 1.1.1-5mamba
+- fix OSGi MANIFEST
+
+* Fri Jul 03 2009 gil <puntogil@libero.it> 1.1.1-4mamba
+- added maven poms
+
+* Sat Apr 04 2009 gil <puntogil@libero.it> 1.1.1-3mamba
+- added package javadoc
+
+* Mon Mar 09 2009 gil <puntogil@libero.it> 1.1.1-2mamba
+- rebuilt
+
+* Sat Feb 28 2009 gil <puntogil@libero.it> 1.1.1-1mamba
+- package created by autospec
diff --git a/maven2-2.2.0-settings.xml b/maven2-2.2.0-settings.xml
new file mode 100644
index 0000000..0d6ad48
--- /dev/null
+++ b/maven2-2.2.0-settings.xml
@@ -0,0 +1,245 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+<!--
+ | This is the configuration file for Maven. It can be specified at two levels:
+ |
+ |  1. User Level. This settings.xml file provides configuration for a single user, 
+ |                 and is normally provided in $HOME/.m2/settings.xml.
+ |
+ |                 NOTE: This location can be overridden with the system property:
+ |
+ |                 -Dorg.apache.maven.user-settings=/path/to/user/settings.xml
+ |
+ |  2. Global Level. This settings.xml file provides configuration for all maven
+ |                 users on a machine (assuming they're all using the same maven
+ |                 installation). It's normally provided in 
+ |                 ${maven.home}/conf/settings.xml.
+ |
+ |                 NOTE: This location can be overridden with the system property:
+ |
+ |                 -Dorg.apache.maven.global-settings=/path/to/global/settings.xml
+ |
+ | The sections in this sample file are intended to give you a running start at
+ | getting the most out of your Maven installation. Where appropriate, the default
+ | values (values used when the setting is not specified) are provided.
+ |
+ |-->
+<settings xmlns="http://maven.apache.org/settings/1.0.0" 
+          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
+          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
+  <!-- localRepository
+   | The path to the local repository maven will use to store artifacts.
+   |
+   | Default: ~/.m2/repository-->
+  <localRepository>__INTERNAL_REPO_PLACEHOLDER__</localRepository>
+
+
+
+  <!-- interactiveMode
+   | This will determine whether maven prompts you when it needs input. If set to false,
+   | maven will use a sensible default value, perhaps based on some other setting, for
+   | the parameter in question.
+   |
+   | Default: true
+  <interactiveMode>true</interactiveMode>
+  -->
+
+  <!-- offline
+   | Determines whether maven should attempt to connect to the network when executing a build.
+   | This will have an effect on artifact downloads, artifact deployment, and others.
+   |
+   | Default: false
+  <offline>false</offline>
+  -->
+
+  <!-- proxies
+   | This is a list of proxies which can be used on this machine to connect to the network.
+   | Unless otherwise specified (by system property or command-line switch), the first proxy
+   | specification in this list marked as active will be used.
+   |-->
+  <proxies>
+    <!-- proxy
+     | Specification for one proxy, to be used in connecting to the network.
+     |
+    <proxy>
+      <id>optional</id>
+      <active>true</active>
+      <protocol>http</protocol>
+      <username>proxyuser</username>
+      <password>proxypass</password>
+      <host>proxy.host.net</host>
+      <port>80</port>
+      <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
+    </proxy>
+    -->
+  </proxies>
+
+  <!-- servers
+   | This is a list of authentication profiles, keyed by the server-id used within the system.
+   | Authentication profiles can be used whenever maven must make a connection to a remote server.
+   |-->
+  <servers>
+    <!-- server
+     | Specifies the authentication information to use when connecting to a particular server, identified by
+     | a unique name within the system (referred to by the 'id' attribute below).
+     | 
+     | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are 
+     |       used together.
+     |
+    <server>
+      <id>deploymentRepo</id>
+      <username>repouser</username>
+      <password>repopwd</password>
+    </server>
+    -->
+    
+    <!-- Another sample, using keys to authenticate.
+    <server>
+      <id>siteServer</id>
+      <privateKey>/path/to/private/key</privateKey>
+      <passphrase>optional; leave empty if not used.</passphrase>
+    </server>
+    -->
+  </servers>
+
+  <!-- mirrors
+   | This is a list of mirrors to be used in downloading artifacts from remote repositories.
+   | 
+   | It works like this: a POM may declare a repository to use in resolving certain artifacts.
+   | However, this repository may have problems with heavy traffic at times, so people have mirrored
+   | it to several places.
+   |
+   | That repository definition will have a unique id, so we can create a mirror reference for that
+   | repository, to be used as an alternate download site. The mirror site will be the preferred 
+   | server for that repository.
+   |-->
+  <mirrors>
+    <!-- mirror
+     | Specifies a repository mirror site to use instead of a given repository. The repository that
+     | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
+     | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
+     |
+	 -->
+    <mirror>
+      <id>mirrorId</id>
+      <mirrorOf>repositoryId</mirrorOf>
+      <name>Human Readable Name for this Mirror.</name>
+      <url>__EXTERNAL_REPO_PLACEHOLDER__</url>
+    </mirror>
+     
+  </mirrors>
+  
+  <!-- profiles
+   | This is a list of profiles which can be activated in a variety of ways, and which can modify
+   | the build process. Profiles provided in the settings.xml are intended to provide local machine-
+   | specific paths and repository locations which allow the build to work in the local environment.
+   |
+   | For example, if you have an integration testing plugin - like cactus - that needs to know where
+   | your Tomcat instance is installed, you can provide a variable here such that the variable is 
+   | dereferenced during the build process to configure the cactus plugin.
+   |
+   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
+   | section of this document (settings.xml) - will be discussed later. Another way essentially
+   | relies on the detection of a system property, either matching a particular value for the property,
+   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a 
+   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
+   | Finally, the list of active profiles can be specified directly from the command line.
+   |
+   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
+   |       repositories, plugin repositories, and free-form properties to be used as configuration
+   |       variables for plugins in the POM.
+   |
+   |-->
+  <profiles>
+    <!-- profile
+     | Specifies a set of introductions to the build process, to be activated using one or more of the
+     | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
+     | or the command line, profiles have to have an ID that is unique.
+     |
+     | An encouraged best practice for profile identification is to use a consistent naming convention
+     | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
+     | This will make it more intuitive to understand what the set of introduced profiles is attempting
+     | to accomplish, particularly when you only have a list of profile id's for debug.
+     |
+     | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
+    <profile>
+      <id>jdk-1.4</id>
+
+      <activation>
+        <jdk>1.4</jdk>
+      </activation>
+
+      <repositories>
+        <repository>
+          <id>jdk14</id>
+          <name>Repository for JDK 1.4 builds</name>
+          <url>http://www.myhost.com/maven/jdk14</url>
+          <layout>default</layout>
+          <snapshotPolicy>always</snapshotPolicy>
+        </repository>
+      </repositories>
+    </profile>
+    -->
+
+    <!--
+     | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
+     | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
+     | might hypothetically look like:
+     |
+     | ...
+     | <plugin>
+     |   <groupId>org.myco.myplugins</groupId>
+     |   <artifactId>myplugin</artifactId>
+     |   
+     |   <configuration>
+     |     <tomcatLocation>${tomcatPath}</tomcatLocation>
+     |   </configuration>
+     | </plugin>
+     | ...
+     |
+     | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
+     |       anything, you could just leave off the <value/> inside the activation-property.
+     |
+    <profile>
+      <id>env-dev</id>
+
+      <activation>
+        <property>
+          <name>target-env</name>
+          <value>dev</value>
+        </property>
+      </activation>
+
+      <properties>
+        <tomcatPath>/path/to/tomcat/instance</tomcatPath>
+      </properties>
+    </profile>
+    -->
+  </profiles>
+
+  <!-- activeProfiles
+   | List of profiles that are active for all builds.
+   |
+  <activeProfiles>
+    <activeProfile>alwaysActiveProfile</activeProfile>
+    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
+  </activeProfiles>
+  -->
+</settings>