Veritas Data Insight Third-Party Attributions Guide
- Third Party software license agreements
- About Third-party Legal Notices
- Apache License
- Apache Software License 1.1
- Apache Software License 2.0
- Artistic License
- ANTLR License
- BSD License
- Classpath exception
- Common Development and Distribution License
- Common Public License
- Creative Commons Attribution
- Creative Commons Zero v1.0 Universal
- Do What The F*ck You Want To Public License
- Eclipse Distribution License v 1.0
- Eclipse Public License 1.0
- Eclipse Public License 2.0
- GNU General Public License v1.0 only
- GNU General Public License v1.0 or later
- GNU General Public License v2.0 or later
- GNU Lesser General Public License
- Google Web Toolkit Terms License
- ISC License
- Jdom License
- JSON License
- Microsoft Public License
- Microsoft Reciprocal License
- MIT License
- Mozilla Public License 2.0
- NetCDF license
- Open Geospatial Consortium Software License
- OpenSSL License
- Oracle Binary Code License Agreement for the Java SE Platform Products and JavaFX
- Oracle Binary Code License for Java EE Technologies
- Public Domain
- Python Software Foundation License 2.0
- Restricted Property
- Sun GPL With Classpath Exception v2.0
- TeamDev Product License Agreement Version 3.7
- unRAR License
- Veritas Proprietary Inbound License
ANTLR License
ANTLR 2.7.7
ANTLR License ============= SOFTWARE RIGHTS ANTLR 1989-2004 Developed by Terence Parr Partially supported by University of San Francisco & jGuru.com We reserve no legal rights to the ANTLR--it is fully in the public domain. An individual or company may do whatever they wish with source code distributed with ANTLR or the code generated by ANTLR, including the incorporation of ANTLR, or its output, into commerical software. We encourage users to develop software with ANTLR. However, we do ask that credit is given to us for developing ANTLR. By "credit", we mean that if you use ANTLR or incorporate any source code into one of your programs (commercial product, research project, or otherwise) that you acknowledge this fact somewhere in the documentation, research report, etc... If you like ANTLR and have developed a nice tool with the output, please mention that you developed it using ANTLR. In addition, we ask that the headers remain intact in our source code. As long as these guidelines are kept, we expect to continue enhancing this system and expect to make other tools available as they are completed. The primary ANTLR guy: Terence Parr parrt@cs.usfca.edu parrt@antlr.org
Modified libraries for Apache Portable Runtime 1.7.0