Download JAR files tagged by maintain with all dependencies

This framework enables users to integrate Transcend's comprehensive consent manager, featuring TCF-UI, consent-manager, and GPP views, into their applications.This WebView seamlessly facilitates the integration of consent forms, privacy policies, and other user data management features, enabling developers to maintain compliance with data privacy regulations and deliver a user-friendly experience.

The pomlint mojo helps enforcing a certain style in Maven projects. This is particular useful in a multi-module project maintained by large teams of developers. Often best practices are ignored when the project becomes busy. This leads to pom structures that are hard to maintain and thus degrade the projects agility. By having a linter enforce the rules upfront many of the simple mistakes can be avoided.

A GWT wrapper for the Vie JavaScript library. This component is used as a part of OpenCms, an enterprise-ready, easy to use website content management system based on Java and XML technology. Offering a complete set of features, OpenCms helps content managers worldwide to create and maintain beautiful websites fast and efficiently.

A GWT wrapper for the Vie JavaScript library. This component is used as a part of OpenCms, an enterprise-ready, easy to use website content management system based on Java and XML technology. Offering a complete set of features, OpenCms helps content managers worldwide to create and maintain beautiful websites fast and efficiently.

The CKIP (Chinese Knowledge and Information Processing) is a online service for separate Chinese sentence. The service maintain by [CKIP group](http://godel.iis.sinica.edu.tw/CKIP/) in [Sinica](http://www.sinica.edu.tw). CKIPClient-Java is a client library that simplify the procedure of TCP scoket communication between client and CKIP server. Developer can use CKIPClient-Java to access CKIP service more easily. The CKIPClient-Java licensed under Apache License Version 2.0. CKIP 是中研院詞庫小組開發的中文斷詞系統，此系統採用線上服務模式，採用 TCP Scoket 傳送文本到 Server 進行斷詞，再接收斷詞結果。 此專案是將上述斷詞流程採用 Java 實作，提供使用者方便地使用 CKIP 服務。本人並非中研院成員或是詞庫小組相關人士，本人只是將之前撰寫的 Client 端程式碼公開，並嘗試以不同的程式語言實做。所有中文斷詞相關技術及問題請洽中研院詞庫小組。 CKIPClient-Java 採用 Apache License Version 2.0 釋出

COBYLA2 is an implementation of Powell's nonlinear derivative free constrained optimization that uses a linear approximation approach. The algorithm is a sequential trust region algorithm that employs linear approximations to the objective and constraint functions, where the approximations are formed by linear interpolation at n + 1 points in the space of the variables and tries to maintain a regular shaped simplex over iterations. It solves nonsmooth NLP with a moderate number of variables (about 100). Inequality constraints only. The initial point X is taken as one vertex of the initial simplex with zero being another, so, X should not be entered as the zero vector.

All Gwt jre emulation code goes in this module, as well as any gwt-compiler overrides. xapi-gwt-api.jar must come before gwt-dev.jar on your compile classpath. A plugin is being built to automatically adjust maven runtime dependencies, but users of ant or IDEs will need to ensure the super jar comes before gwt-dev. We will petition gwt to accept our mods, but, until then, if you want bleeding edge features, you gotta do bleeding edge configuration. Code that ties directly into other modules, like java.lang.reflect for the reflection submodule, have their super-source here, and generators or other implementations in their own modules. This is to maintain consistency in what is or isn't whitelisted in XApi GWT. Some modules, like appengine, provide dependency-specific super-source in their own packages. This module is for jre, junit and core XApi services.

Java Prolog Interface (JPI) is an Application Provider Interface (API) for interaction between Java and Prolog programming languages. Is a bidirectional interface that communicate Java applications with Prolog program or database and Prolog procedures with Java class and methods. JPI is an abstraction layer over concrete prolog drivers over Prolog Engines. This API define all mechanism to interact with any Prolog Engine and maintain the application independent to a specific underlying engine. JPI have several connectors to open source prolog engines like SWI, YAP, XSB native engines and tuProlog, jTrolog, jLog Java based prolog engines. JPI study all related Java-Prolog integration libraries and take the betters features from each solution with the propose to achieve a common integration interface. The last feature allows switch the under laying Prolog Engine driver and the application code still be the same. JPI run over any Java Virtual Machine that support Java SE 5 or above. The project was tested over HotSpot, Open J9 and JRockit Virtual Machines over Operating Systems like Windows (7,8,10), Linux (Debian, Ubuntu) and Mac OS X. Can be deployed on Servlets Containers like Jetty, Tomcat or Glassfish Application Server. JPI can be include in any Java Project using the commonest Java Integration Development Enviroment (IDE) like Eclipse, Netbeans, IntelijIDEA and so on. JPI is developed and maintained by Prolobjectlink Project an open source initiative for build logic based applications using Prolog like fundamental Logic Programming Language in the persistence layer and application programming.

This is the main aggregator for all gwt submodules. All gwt-specific code resides here. Submodules should avoid inheriting from each other unless necessary. This goes for maven structure and gwt.xml structure. The super module is where our jre emulation layer and super-source live; all modules should inherit super, and a minimum of other modules. Some modules, like injection, are fulfilling an api in the core module, and should be accessed only through core service interfaces. Other modules, like reflection, are capable of being standalone inherits, but can benefit from core utilities like injection, so, two (or more) .gwt.xml modules may be provided. As XApi nears 1.0, all submodules will be routinely stitched together into an uber-jar, in order to have a single jar with a single gwt module that can provide all of the services at once. Internal projects will never use the uber jar, to help maintain modularity, but external projects that want to use more than one service will certainly prefer inheriting one artifact, instead of twelve. When distributed in uber-jar format, it will likely be necessary for either the uber jar, or just xapi-gwt-api.jar to appear before gwt-dev on your compile-time classpath. If using gwt-maven-plugin, the gwtFirstOnClasspath option may become problematic. If so, we will provide a forked gwt-plugin to make sure our compiler enhancements are included in the build process. There is also work going on to make a super-source-everything plugin, which will use maven to find source files, and generate synthetic .gwt.xml for you, as part of an effort to create a wholly unified programming environment. In addition to java-to-javascript, we intend to compile java-to-java and possibly other languages, like go; imagine implementing gwt deferred binding to eliminate cross-platform differences between server environments, or operating systems, or versions of a platform, or anywhere else a core api needs to bind to multiple implementations, depending on the runtime environment.