<commit_before><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">
   <modelVersion>4.0.0</modelVersion>
   <groupId>OWASP</groupId>
   <artifactId>ESAPI</artifactId>
   <packaging>jar</packaging>
   <version>2.0</version>
   <name>ESAPI</name>
   <description>The Enterprise Security API (ESAPI) project is an OWASP project
      to create simple strong security controls for every web platform.
      Security controls are not simple to build. You can read about the
      hundreds of pitfalls for unwary developers on the OWASP website. By
      providing developers with a set of strong controls, we aim to
      eliminate some of the complexity of creating secure web applications.
      This can result in significant cost savings across the SDLC.
   </description>
   <scm>
      <connection>scm:svn:http://owasp-esapi-java.googlecode.com/svn/trunk</connection>
      <developerConnection>scm:svn:https://owasp-esapi-java.googlecode.com/svn/trunk</developerConnection>
      <!-- <url>http://owasp-esapi-java.googlecode.com/svn/trunk</url> -->
      <url>http://code.google.com/p/owasp-esapi-java/source/checkout</url>
   </scm>
   <issueManagement>
      <system>Google Code Issue Tracking</system>
      <url>http://code.google.com/p/owasp-esapi-java/issues/list</url>
   </issueManagement>
    <mailingLists>
        <mailingList>
            <name>OWASP-ESAPI</name>
            <subscribe>https://lists.owasp.org/mailman/listinfo/esapi-dev/</subscribe>
            <unsubscribe>https://lists.owasp.org/mailman/listinfo/esapi-dev/</unsubscribe>
            <post>mailto:<EMAIL>.org</post>
            <archive>https://lists.owasp.org/pipermail/esapi-dev/</archive>
        </mailingList>
    </mailingLists>

   <organization>
      <name>The Open Web Application Security Project (OWASP)</name>
      <url>http://www.owasp.org/index.php</url>
   </organization>
   <url>http://www.esapi.org/</url>

   <properties>
      <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
   </properties>
   <repositories>
      <repository>
         <id>ibiblio</id>
         <name>ibiblio</name>
         <url>http://www.ibiblio.com/maven</url>
      </repository>
      <repository>
         <id>googlecode-snapshots.oss.sonatype.com</id>
         <name></name>
         <url>http://oss.sonatype.org/content/repositories/googlecode-snapshots</url>
      </repository>
   </repositories>
   <dependencies>
      <dependency>
         <groupId>commons-configuration</groupId>
         <artifactId>commons-configuration</artifactId>
         <version>1.5</version>
      </dependency>
      <dependency><commit_msg>Changed mailing list section. Changed name of 'OWASP-ESAPI' to 'ESAPI-Developers' (which was what it was referring to), added entry for 'ESAPI-Users' list. And left entry for old 'OWASP-ESAPI' archives, but indicated that list was inactive and for archival purposes only.<commit_after><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">
   <modelVersion>4.0.0</modelVersion>
   <groupId>OWASP</groupId>
   <artifactId>ESAPI</artifactId>
   <packaging>jar</packaging>
   <version>2.0</version>
   <name>ESAPI</name>
   <description>The Enterprise Security API (ESAPI) project is an OWASP project
      to create simple strong security controls for every web platform.
      Security controls are not simple to build. You can read about the
      hundreds of pitfalls for unwary developers on the OWASP website. By
      providing developers with a set of strong controls, we aim to
      eliminate some of the complexity of creating secure web applications.
      This can result in significant cost savings across the SDLC.
   </description>
   <scm>
      <connection>scm:svn:http://owasp-esapi-java.googlecode.com/svn/trunk</connection>
      <developerConnection>scm:svn:https://owasp-esapi-java.googlecode.com/svn/trunk</developerConnection>
      <!-- <url>http://owasp-esapi-java.googlecode.com/svn/trunk</url> -->
      <url>http://code.google.com/p/owasp-esapi-java/source/checkout</url>
   </scm>
   <issueManagement>
      <system>Google Code Issue Tracking</system>
      <url>http://code.google.com/p/owasp-esapi-java/issues/list</url>
   </issueManagement>
    <mailingLists>
        <mailingList>
            <name>ESAPI-Users</name>
            <subscribe>https://lists.owasp.org/mailman/listinfo/esapi-users/</subscribe>
            <unsubscribe>https://lists.owasp.org/mailman/listinfo/esapi-users/</unsubscribe>
            <post>mailto:<EMAIL></post>
            <archive>https://lists.owasp.org/pipermail/esapi-users/</archive><!--This is the OWASP ESAPI mailing list for ESAPI users, regardless of programming language. For example, ESAPI users with questions about ESAPI for Java or ESAPI for PHP would both post here.-->
        </mailingList>
        <mailingList>
            <name>ESAPI-Developers</name>
            <subscribe>https://lists.owasp.org/mailman/listinfo/esapi-dev/</subscribe>
            <unsubscribe>https://lists.owasp.org/mailman/listinfo/esapi-dev/</unsubscribe>
            <post>mailto:<EMAIL>.org</post>
            <archive>https://lists.owasp.org/pipermail/esapi-dev/</archive><!--This is the OWASP ESAPI mailing list for ESAPI for Java developers. While the list is not closed, the topics of discussion are likely to be less relevant to those only using ESAPI. Note that this is the list for ESAPI for Java. Most other language implementations, such ESAPI for PHP, have their own mailing lists.-->
        </mailingList>
        <mailingList>
            <name>OWASP-ESAPI (Inactive! Archive only!)</name>
            <archive>https://lists.owasp.org/pipermail/owasp-esapi/</archive><!--The name of the obsolete mailing list that previously was a combination of an ESAPI users lists and ESAP development list. While obsolete, it is still sometimes useful for searching through old historical posts. NOTE: NEW POSTS SHOULD NO LONGER BE MADE TO THIS LIST!-->
        </mailingList>
    </mailingLists>

   <organization>
      <name>The Open Web Application Security Project (OWASP)</name>
      <url>http://www.owasp.org/index.php</url>
   </organization>
   <url>http://www.esapi.org/</url>

   <properties>
      <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
   </properties>
   <repositories>
      <repository>
         <id>ibiblio</id>
         <name>ibiblio</name>
         <url>http://www.ibiblio.com/maven</url>
      </repository>
      <repository>
         <id>googlecode-snapshots.oss.sonatype.com</id>
         <name></name>
         <url>http://oss.sonatype.org/content/repositories/googlecode-snapshots</url>
      </repository>
   </repositories>
   <dependencies>
      <dependency>
         <groupId>commons-configuration</groupId>
         <artifactId>commons-configuration</artifactId>
         <version>1.5</version>
      </dependency>
      <dependency>
{'fraction_non_alphanumeric': 0.1334630891144168, 'fraction_numerical': 0.0061170582510774365, 'mean_word_length': 3.055242390078918, 'pattern_counts': {'":': 0, '<': 199, '<?xml version=': 0, '>': 199, 'https://': 12, 'lorem ipsum': 0, 'www.': 8, 'xml': 4}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6447253', 'n_tokens_mistral': 2313, 'n_tokens_neox': 2193, 'n_words': 464}