Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 7 of 7 for Kata (0.26 sec)

  1. apache-maven/src/main/appended-resources/licenses/unrecognized-asm-9.6.txt

    LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
    CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
    SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
    INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
    CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Mon Nov 13 12:16:58 GMT 2023
    - 1.5K bytes
    - Viewed (0)
  2. apache-maven/src/main/appended-resources/META-INF/NOTICE.vm

    LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
    CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
    SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
    INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
    CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Sat Sep 10 19:27:25 GMT 2022
    - 5.5K bytes
    - Viewed (0)
  3. apache-maven/src/main/appended-resources/licenses/EPL-1.0.txt

    exercise of rights under this Agreement, including but not limited to the
    risks and costs of program errors, compliance with applicable laws, damage
    to or loss of data, programs or equipment, and unavailability or interruption
    of operations.
    
       6. DISCLAIMER OF LIABILITY
    
    EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Mon Sep 17 05:50:12 GMT 2018
    - 11.1K bytes
    - Viewed (0)
  4. apache-maven/src/main/appended-resources/licenses/unrecognized-jline-3.26.1.txt

    EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE
    FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
    OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
    AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
    LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Thu Apr 25 09:13:56 GMT 2024
    - 1.5K bytes
    - Viewed (0)
  5. apache-maven/src/main/appended-resources/licenses/unrecognized-javax.annotation-api-1.3.2.txt

    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.
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Tue May 11 18:59:18 GMT 2021
    - 38.5K bytes
    - Viewed (0)
  6. apache-maven/src/main/appended-resources/licenses/unrecognized-jline-3.25.1.txt

    EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE
    FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
    OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
    AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
    LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
    Plain Text
    - Registered: Sun Apr 21 03:35:09 GMT 2024
    - Last Modified: Mon Jan 29 15:51:24 GMT 2024
    - 1.5K bytes
    - Viewed (0)
  7. maven-core/plugin-manager.txt

     * classloading capability - remote resolution of dependencies - do we want a model for sharing
     * information among plugins, is this more like an extension point - do we need a sort of bus for
     * application data - do we need a dictionary for our applications like Apple does. We could easily
     * hook into this and this is the model we need to follow - how many of our REST services do not map
     * directory to a method in the application interface?
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Mon Jul 18 22:45:13 GMT 2022
    - 12.9K bytes
    - Viewed (0)
Back to top