Download JAR files tagged by archetype with all dependencies

The TrueLicense Maven Archetype is a turn-key solution for designing and implementing a custom licensing schema for your software product. The archetype generates a tailor-made project which is composed of ready-made modules for vending and consuming license keys. The modules contain code templates which you can easily customize without writing code by configuring a set of properties.

The TrueLicense Maven Archetype is a turn-key solution for designing and implementing a custom licensing schema for your software product. The archetype generates a tailor-made project which is composed of ready-made modules for vending and consuming license keys. The modules contain code templates which you can easily customize without writing code by configuring a set of properties.

The TrueLicense Maven Archetype is a turn-key solution for designing and implementing a custom licensing schema for your software product. The archetype generates a tailor-made project which is composed of ready-made modules for vending and consuming license keys. The modules contain code templates which you can easily customize without writing code by configuring a set of properties.

The TrueLicense Maven Archetype is a turn-key solution for designing and implementing a custom licensing schema for your software product. The archetype generates a tailor-made project which is composed of ready-made modules for vending and consuming license keys. The modules contain code templates which you can easily customize without writing code by configuring a set of properties.

The Sakai Wicket Maven Archetype allows you to generate a sample Sakai app via a single Maven command. The app is based on Apache Wicket which integrates nicely with Sakai. The app demonstrates how to get a Sakai tool styled, internationalised and registered, setup your own APIs, wire them up with Spring and inject them via annotations. The 1.1 and up releases also include multi database support via Spring JDBC. It could easily be used as a base for a real tool.

Basic Java 8 archetype. Options: -testLibrary: [junit, testng, none]. DEFAULT: junit. Adds the requested test library to the POM deps. -compilerMode: [simple, test-only, retrolambda-main, retrolambda-all]. DEFAULT: simple. --simple: everything is compiled as Java 8. --test-only: set up test for Java 8, and main for Java 7. --retrolambda-main: main code is compiled as Java 8, and then converted to Java 7 via retrolambda. --retrolambda-all: all code is compiled as Java 8, and then converted to Java 7 via retrolambda. NOTE: Retrolambda support provided "as is" - if you have any problems, please file a ticket on the GitHub page!

Spring Batch archetypes are simple project templates containing just enough code to get you started running a job. For more detailed examples of using particular features of the framework, look at the Spring Batch Samples project. Currently the archetypes are deployed as regular Maven projects (not archetypes), because of limitations in the archetype plugin (or our understanding of how it works). For most effective use, copy one into Eclipse and use Q4E to manage the dependencies.

This is a Maven plug-in for Jini service based projects. It's initial capabilities are: * Archetype for Jini service project creation * Starting/Stopping of Jini starter kit services: Reggie, Mahalo, Phoenix, Fiddler, Norm, Mercury, Outrigger, Browser, and HTTP daemon * Configurable RMI runtime: JRMP, JERI, or JERI/JSSE * Configurable activation and persistence modes: transient, activatable, nonactivatable

This archetype is creating a full Sling Project composed of a OSGi Bundle and a Content Package which can be deployed to the Sling using specific profiles. It also contains two shadow folders that provide example code / files which are not part of the default build but can be easily copied into the active modules. If the project was created with the **optionAll** property set to **y** (yes) then an **All** package is created with acts as the single deployment unit of all bundles and packages in that project. Otherwise the **ui.apps** package is the deployment unit.

Customizable cruft-free Scala archetype. Options: -sourceFolders: [all-in-src-java, scala-only, both-split-src]. DEFAULT: all-in-src-java. --all-in-src-java: Scala and Java code are both in src/main/java (same for test). Plays nicely with IDEs. --scala-only: only src/main/scala set up, and set as source folder. --both-split-src: both src/main/java and src/main/scala. Can play merry havock with IDEs, so not the default. -testLibrary: [scalatest, specs2, scalacheck-only, junit-only]. DEFAULT: scalatest. --scalatest: adds Scalatest AND Scalacheck AND JUnit for most of your testing needs. --specs2: adds specs2 AND Scalacheck AND JUnit. --scalacheck-junit: adds Scalacheck AND JUnit. --junit-only: adds JUnit ONLY. -scalaVersion: 2.10.x+. DEFAULT: 2.11.2. *The Scala tool version is generated automatically. *Some Scala versions may not be compatible with selected test library versions. Adjust as necessary.