Download JAR files tagged by properties with all dependencies

JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language.

This module contains library classes for accessing the ThreadFix REST API. The ThreadFix IDE plugins use this library to retrieve application and vulnerability marker information, and in the ThreadFix scanner plugins to get endpoint information and upload scans to ThreadFix applications. The easiest way to start using the library is with the PluginClient or ThreadFixRestClient classes. Both have constructors that take a PropertiesManager instance, which holds the ThreadFix API key and url information. The default PropertiesManager implementation stores these properties in threadfix.properties, but the ThreadFix plugins extend the default PropertiesManager class to override this behavior for the target platform.

This project provides the best of maven easily consumable a maven parent project, called MavenParent. With this project you get: Checkstyle and PMD checks that will work by default in eclipse with m2e-code-quality. OWASP vulnerability checks of your dependencies. Easy application of BSD-3 clause license to all your code with mycila-license plugin. The ability to easily enforce semantic version on a jar project with japicmp. Prevent duplicates on your classpath with basepom's duplicate-finder. All of the above can be configured or disabled easily with properties, just check their docs, except takari. A whole slew of pretty maven reports including the above are generated in the maven site. The ability to easily deploy to oss nexus, and publish maven generated sites back to github's sites pages.

JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language.

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"

It helps to quickly make settings for class and its fields of with properties XML. Instead of create a lot of files to describe every class and its fields it use describing by type, by name. E.g. setting "java.lang.Integer"-"INTEGER NOT NULL" will be assigned for every field of this type. Of course it can be overridden by settings for field name and so on. It is used by beige-web to describe how to render an entity and convert from HTML value. It is used by beige-orm to describe how to map an entity to a DBMS. It make simple settings - Map<String, String>, e.g. "title"-"Beige ORM 1.1", class settings Map<String, Map<String, String>>, e.g. "org.model.Customer"-["defaultOrder"-"ITSNAME", "wdgFilterOrder"-"filterOrderStd"], fields settings Map<String, Map<String, Map<String, String>>>, e.g. "org.model.Customer"-["itsId"["wdgNew"-"null", "wdgFilter"-"filterNumber"]]