Download JAR files tagged by path with all dependencies

ExecutorService's type parameters changed between JDK5 and JDK6 in a way that makes it impossible for our invokeAll/invokeAny methods to match both at compile time. This project builds a JDK6-like copy of ExecutorService (but with JDK5 compiler settings to ensure that it will work with JRE5 at runtime). This project's is then used in the bootstrap class path of Guava proper.

ExecutorService's type parameters changed between JDK5 and JDK6 in a way that makes it impossible for our invokeAll/invokeAny methods to match both at compile time. This project builds a JDK6-like copy of ExecutorService (but with JDK5 compiler settings to ensure that it will work with JRE5 at runtime). This project's is then used in the bootstrap class path of Guava proper.

To run all integration tests, you need to set up all the databases: 1) Derby: $ export DERBY_HOME=/path/to/db-derby-10.14.2.0-bin $ cd $DERBY_HOME $ mkdir databases; cd databases $ java -jar $DERBY_HOME/lib/derbyrun.jar server start 2) MS SQL Server (for official and jtds drivers): $ podman run -itd --name pax.jdbc.sqlserver -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=PaxJdbc!(*67' -e 'MSSQL_PID=Express' \ -p 1433:1433 -d mcr.microsoft.com/mssql/server:2022-latest 3) MariaDB: $ podman run --name pax.jdbc.mariadb -p 3306:3306 -e MYSQL_ROOT_PASSWORD=paxjdbc -d mariadb 4) MySQL: $ podman run --name pax.jdbc.mysql -p 3307:3306 -e MYSQL_ROOT_PASSWORD=paxjdbc -d mysql 5) PostgreSQL: $ podman run --name pax.jdbc.postgresql -e POSTGRES_USER=paxjdbc -e POSTGRES_PASSWORD=paxjdbc -p 5432:5432 -d postgres:latest 6) Oracle (a bit unofficial): $ podman run -itd --name pax.jdbc.oracle -p 1521:1521 --privileged=true oracleinanutshell/oracle-xe-11g

<p>Sometimes while programming in NetBeans you want to explore a particular file that you are editing on the file system browser, or maybe launch a command in a terminal to do something with it.</p> <p>This plugins brings to your NetBeans six action, three of them always available and three of them available when the selected node has a file assiociated with it.<br/> In particular:<p><p><em>When the selection has a valid file</em></p> <ul> <li><strong>Open the default OS shell</strong> on the location of the file (or its folder) selected.</li> <li><strong>Open the file system browser</strong> on the location of the file (or its folder) selected.</li> <li><strong>Copy to the clipboard</strong> the path of the file selected.</li> </ul> <p><em>Always enabled:</em></p> <ul> <li><strong>Launch a shell command</strong> (with parameters, customizable on preferences)</li> <li><strong>FileSystem browser on any location</strong> (favorites, customizable on preferences)</li> <li><strong>Open a shell on any location</strong> (favorites, customizable on preferences)</li> </ul>

This ApplicationProperties Java package provides a fast and easily configurable application.properties loader that mimics some key features of the Spring Boot application.properties loader. This package allows for multi-level overloading of properties based on a basename and optional suffix by searching the classpath, optional configurable file paths along with the JNDI server container context. The class [ApplicationPropertiesConfig](src/main/java/com/lyders/application-properties/ApplicationPropertiesConfig.java) controls the features of the overloading of properties such as the base name of the properties file, an optional suffix that allows for the loading of environment-specific or scenario-specific property files as needed. The following features are supported: * Names of properties files can be customized * Locations of properties files can be customized. The following path types are supported: * class path * file system paths * JNDI environment naming context (e.g., Servlet/JSP running under Tomcat) * Environment-specific property files can override the values in default properties files via a "suffix"

Tool used to analyze a set of classes and determine on what other classes they directly or indirectly depend. Typically this tool is used to compute the necessary and sufficient set of classes to include in a JAR file, for use in the class path of a client or service, or for use in the codebase of a client or service. The tool starts with a set of "root" classes and recursively computes a dependency graph, finding all of the classes referenced directly by the root classes, finding all of the classes referenced in turn by those classes, and so on, until no new classes are found or until classes that are not of interest are found. The normal output of the tool is a list of all of the classes in the dependency graph. The output from this command can be used as input to the jar tool, to create a JAR file containing precisely those classes.

配置监控信息，在web.xml中添加 <filter> <description>拦截获取js与css过滤</description> <filter-name>MergeFilter</filter-name> <filter-class>com.njzxw.filter.MergeFilter</filter-class> <init-param> <!-- js合并输出路径 --> <param-name>jsDir</param-name> <param-value>${js.path}</param-value> </init-param> <init-param> <!-- css合并输出路径 --> <param-name>cssDir</param-name> <param-value>${css.path}</param-value> </init-param> </filter> 同时添加一个合并js\css对应一个merge.xml，最好放置在同级，如： <merge> <group name="sss" > <js path="js/common/common.js" /> <js path="js/common/index.js" /> <css path="css/common/animate.css" /> <css path="css/common/normalize.css" /> </group> </merge> 访问项目：xxx/sss.js xxx/sss.css 同时配合maven插件： compress-maven-plugin结合使用： <plugin> <groupId>com.github.eliayng</groupId> <artifactId>compress-maven-plugin</artifactId> <version>1.0.0</version> <executions> <execution> <phase>compile</phase> <goals> <goal>compress</goal> </goals> </execution> </executions> <configuration> <skip>${skipCompress}</skip> <poolNum>50</poolNum> <jsOutDir>${jsOutDir}</jsOutDir> <cssOutDir>${cssOutDir}</cssOutDir> <!--是否监控编译class文件--> <isCompressClass>true</isCompressClass> <!-- 是否复制资源文件 --> <isResourcesCopy>true</isResourcesCopy> </configuration> </plugin>

TrueZIP is a Java based virtual file system (VFS) which enables client applications to perform CRUD (Create, Read, Update, Delete) operations on archive files as if they were virtual directories, even with nested archive files in multithreaded environments. As a library, TrueZIP provides simple, uniform, transparent, thread-safe, read/write access to archive files as if they were virtual directories in a file system path. As a framework, TrueZIP provides the interfaces and classes to write file system drivers which plug-in to its federated file system space.

In order to get around the JBI Lifecycle Classpath limitation in the application server, a new JBI jar file is being created called esb_jbi_framework.jar. This jar file will contain a MANIFEST.MF file that contains Class-Path: entries that point towards the jbi_rt.jar (JBI Runtime) and jbi_tests.jar (Scaffolding Registry et al) . This way we dont have to combine the throwaway jbi_tests.jar with the main jbi_rt.jar later. We would simply have to dereference it from jbi_framework.jar. Likewise adding a new JAR to the same classpath would simply mean adding a new entry to the ClassPath: header field.

The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system. It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java to SAP System as well as SAP System to Java calls. - All SAP Connectors are licensed without additional license fees as part of the respective solution or component license. However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems / SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed. - The redistribution of any connector is not allowed. - All SAP users accessing application functionality through the relevant connector are required to be licensed under a respective solution or component license. To use the SAP JCo with the jco-jar project, you need to either install the SAP JCo jar downloaded from SAP to your local Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b): (a) mvn install:install-file -DgroupId=com.github.easonjim -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.11 -Dpackaging=jar -Dfile=path/to/sapjco3.jar (b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=com.github.easonjim -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.11 -Dpackaging=jar -Dfile=path/to/sapjco3.jar