Download JAR files tagged by marking with all dependencies

Exception types for marking unreachable/unimplemented code

JsfWarn - allows for Field level warning messages and marking.

Exception types for marking unreachable/unimplemented code (Test suite)

~Exception types for marking unreachable/unimplemented code (Checkstyle policy)

~Exception types for marking unreachable/unimplemented code (Checkstyle policy)

Annotation for the Naked Kotlin Compiler Plugin which is used for marking value classes to inline.

This project contains one class, a marking annotation, @Verify, that indicates that the AptSpringProcessor should verify a spring graph. All checks are fully enumerated in @Verify's javadoc.

PMatch component of the Open University's OpenMark project for marking free text question answers.

Dryuf BigIo is stateless, unlimited IO framework, solving few design problems of original JDK. It mainly provides three things - FlatBuffer with 64-bit address space and being stateless. Additionally, it provides FlatChannel interface and few implementations - providing the arbitrary reads and writes from chosen position. This is implemented only in FileChannel in NIO so this interface makes it easier to provide those stateless reads and writes on virtual channels too. BigIo also provides committable objects, allowing marking the object as completed or incomplete, so it correctly results into success or exception on receiving side.

GlassFish build depends on properly functioning several custom lifecycle mappings and artifact handlers. Because these are necessary to resolve dependencies and to run "gf:run" goal and etc., it is critical that these extensions be made available to Maven early on during Maven execution. This definition was originally in maven-glassfish-plugin, which was integrated into Maven POM through <plugin>/<extensions>true marking, but after a series of debugging to resolve artifact resolution failure problems, it turns out that that doesn't cause Maven to load components early enough. I tried to circumbent the prolem by also registering the maven-glassfish-plugin as an extension module (via <build>/<extensions/<extension>), but that apparently confuses Maven to no end --- I get build errors like this: [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar': Unable to find the mojo 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar' in the plugin 'org.apache.maven.plugins:maven-jar-plugin' This is obviously one of the problematic areas of Maven, so to avoid doing hack over hack, I'm simply moving the component definitions to its own module.