13.12.11
How to configure Maven to Work with JDK 1.6/JUnit4
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
<encoding>UTF-8</encoding>
</configuration>
</plugin>
</plugins>
</build>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<archive>
<manifest>
<mainClass>fully.qualified.MainClass</mainClass>
</manifest>
</archive>
<descriptorRefs>
<descriptorRef>jar-with-dependencies</descriptorRef>
</descriptorRefs>
</configuration>
</plugin>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.10</version>
</dependency>
Other plugin search:
Maven Repository: Search/Browse/Explore
3 ways to run Java main from Maven | Vineet Manohar's blog
12.12.11
Ant vs. Maven: An Entertaining Look at the Arguments | Javalobby
- if you do not have a good architecture which is modular in nature and which separates concerns that should be separated you'll run into trouble no matter what you use.
21.10.10
Maven: Such a Good Thing!
When I was still away from maven, I could not even imagine there is a powerful thing in the world. What does really matter is the idea of global, but not centralized repository.
There are thousands of plugin system in the world, but I would like to regard Maven is the most successful one. I don’t know where this success comes from, and why people want to contribute to such a specific plugin system. But, apparently, people did, and are still doing.
For the finial deployed system, it is alright to have a complicated one and you can establish the system elaborately. But for the development system, from my own point of view, I need to have a simple set up procedure, a short test cycle, and integrated environment. Maven gives me all these.
20.10.10
Contrasting Nexus and Artifactory
I just came across JFrog’s Artifactory and found is very similar to Sonatype’s Nexus, therefore, I searched on the Google using these two names and found the following article. It’s a little bit old and came from Sonatype, but it is worthy to take a look at.
Contrasting Nexus and Artifactory
January 19th, 2009By Brian Fox
Contrast #1: Network: WebDAV vs. REST
The first major difference is that Artifactory uses Jackrabbit as a WebDAV implementation for artifact uploads. Nexus implements a simple, lightweight HTTP PUT via Restlet instead. We had a WebDAV implementation in early Alpha releases but found it to be far too heavy and slow. Switching to a simple REST call improved our performance and significantly decreased the memory footprint. A profile of the memory use in Artifactory that I ran on previous versions showed that the majority of the object creation and memory allocation is related to Jackrabbit. Sure, you can’t mount a Nexus repository with a webfolder using WebDAV, but is that really what you need a repository manager to do, or would you rather it be blazingly fast doing Maven builds? It is possible to use the lightweight wagon against Artifactory (http vs dav:http), but the choice of Jackrabbit in our opinion is overhead that isn’t needed.
Contrast #2: Storage: Relational Database vs. Filesystem
The second major difference is that Nexus deliberately chooses to use a regular Maven 2 repository layout to store the data on disk. Doing this effectively isn’t always easy and we’ve had many discussions about it amongst the team, but I hold fast to this approach for several reasons:
- It makes importing and exporting the repositories a no brainer. Simply copy the data into the correct folder in the Nexus work folder and you’re done, import finished. Copy it out, export done.
- The incremental nature of the file changes in a Maven 2 repository layout makes it extremely well suited for incremental backups to tape or other archiving medium.
- Nexus also keeps its metadata (not to be confused with the maven-metadata) separate from the artifacts, and the data is rebuilt on the fly if it’s missing. If you are unlucky and have some hardware or disk error, you will likely only get one file corrupted, not the entire repository.
- Having the metadata separate means Nexus upgrades don’t have to touch any data in the repository folder. Upgrades and rollbacks of the system can happen as fast as you can stop one instance and start the next.
Artifactory takes the polar opposite approach and stores the metadata and the artifacts themselves in a huge database. The reason they claim it’s needed is for transactional behavior. Using a database doesn’t guarantee transactionality and it certainly isn’t the only way to get transactional behavior.
In order to use a database, Artifactory needs to have import and export tools. The imports and exports of this data are reported to take a significant amount of time (http://issues.jfrog.org/jira/browse/RTFACT-317). Some upgrades require a full dump and re-import of the database, taking out large systems for a significant amount of time. Also, what happens if you need to tweak or repair a file in the system? Break out your dba books and go to town. How about incremental backups? Would you be happy if a single disk error made your entire repository garbage?
We feel strongly that introducing a repository manager into your system shouldn’t require a dba to manage the data. Quite reliable backups can be performed with Nexus using robocopy or rsync tools and a simple script, and transactions can be obtained with much less overhead. In fact, with the Staging plugin, Nexus is able to turn an entire multimodule build into a single transaction. There are ways to implement “transactional” interactions in a piece of software without having to throw everything into a database. We think that loading the entire contents of a repository into Jackrabbit and modelling the repository in a relational database is introducing much more complexity into the problem than is necessary.
Contrast #3: Storage Size
It has also been reported that the indexes and metadata introduced by Artifactory can double or triple the size of a repo. See this thread for real examples. Perhaps that’s manageable on a 1gb repo, but how about something like Central at 60+ gb? Nexus uses the Nexus-indexer (Artifactory uses it as well to provide search capability) which is just a Lucene index. We can provide indexes of Central that are only 30mb…not double the size of the repo itself. Note that the Nexus indexes also include cross references of the Java classes contained in the jars. Once again, we think involving a relational database into this problem is an unnecessarily complicating factor.
A preliminary test import of a 116mb release repo took 5 minutes and the resulting data size was 323mb (2.78x the original size). Extrapolating that out to a 4gb repository gets you about 3 hours of import and a total data size of 11gb. Sure disks are cheap these days, but still tripling the size of your data has many long term ramifications when you consider backups, replication etc.
Note: The actual import I ran failed 3 times on data from central due to too strict checking, I had to prune or repair the files just to get it to import. Fortunately that didn’t happen midway through a 3 hour import…. which leads me to the next point…
Contrast #4: Nexus Doesn’t Interfere
We believe that Nexus shouldn’t interfere with your builds. We all know that the data in remote repos like Central can be incomplete. However, if Maven is able to use it, then we make sure Nexus won’t get in the way. Artifactory proactively blocks any data that isn’t parse-able as it comes through as a feature. This means you may have a build that works without Artifactory and breaks with it because it refuses to proxy (and apparently import) any files it doesn’t like. Nexus will report that there’s a problem to the admins to deal with, but won’t cause Maven to blow up for the developer. Nexus favors stability over correctness for proxy repositories.
Download Nexus Today
Nexus is available as an open source project for free. There is also a Pro version that includes additional commercial level functionality and professional support and for only $2995 per server. While the Open Source version is capable and popular, Nexus Professional adds some new features that are targeted at Enterprise Users: staging, procurement, and LDAP integration.
http://www.sonatype.com/people/2009/01/contrasting-nexus-and-artifactory/
10.9.10
List for Archetype
1: remote -> docbkx-quickstart-archetype (null)
2: remote -> gquery-archetype (null)
3: remote -> gquery-plugin-archetype (null)
4: remote -> liferay-layouttpl-archetype (Provides an archetype to create Liferay layout templates.)
5: remote -> liferay-portlet-archetype (Provides an archetype to create Liferay portlets.)
6: remote -> liferay-theme-archetype (Provides an archetype to create Liferay themes.)
7: remote -> j2me-simple (Maven 2 Archetype for midlet application using j2me-maven-plugin)
8: remote -> vaadin-archetype-clean (This archetype generates a simple Vaadin application as a Maven project.
No custom widgetset is included.)
9: remote -> vaadin-archetype-sample (This archetype generates a Vaadin application as a Maven project.
The application contains a custom GWT widgetset that is compiled
by the GWT compiler and integrated into the project as part of the
build process. The application is based on the Vaadin Color Picker
Demo application available at http://vaadin.com.)
10: remote -> vaadin-archetype-widget (This archetype generates a Vaadin widget project for Vaadin 6.2+ and a test application.)
11: remote -> jbosscc-seam-archetype (Maven Archetype to generate a Seam Application)
12: remote -> rails-maven-archetype (archetype to mavenize an existing rails 2.3.x or rails3 application)
13: remote -> maven-archetype-flex (An archetype which contains a sample Maven Flex project using the israfil maven plugin)
14: remote -> javate-zk-archetype (Archetype for a JavATE project that uses Hibernate and ZK.)
15: remote -> data-app (To make creating a new Databinder application easier, this archetype includes all required sources and resources.)
16: remote -> data-app (To make creating a new Databinder application easier, this archetype includes all required sources and resources.)
17: remote -> gae-archetype-gwt (Archetype for creating maven-gae projects that uses GWT for the view)
18: remote -> gae-archetype-jsp (Archetype for creating maven-gae projects that uses jsp for the view)
19: remote -> gae-archetype-wicket (Archetype for creating maven-gae projects based on apache wicket framework)
20: remote -> lift-archetype-basic (Basic project archetype for Lift Web Framework (with database, logging, user management).)
21: remote -> lift-archetype-basic_2.7.7 (Basic project archetype for Lift Web Framework (with database, logging, user management).)
22: remote -> lift-archetype-basic_2.8.0 (Basic project archetype for Lift Web Framework (with database, logging, user management).)
23: remote -> lift-archetype-blank (Blank project archetype for Lift Web Framework.)
24: remote -> lift-archetype-blank_2.7.7 (Blank project archetype for Lift Web Framework.)
25: remote -> lift-archetype-blank_2.8.0 (Blank project archetype for Lift Web Framework.)
26: remote -> lift-archetype-hellolift (Archetype - hellolift, a sample Lift application)
27: remote -> lift-archetype-jpa-basic (Basic JPA archetype for Lift Web Framework.)
28: remote -> lift-archetype-jpa-basic_2.7.7 (Basic JPA archetype for Lift Web Framework.)
29: remote -> lift-archetype-jpa-basic_2.8.0 (Basic JPA archetype for Lift Web Framework.)
30: remote -> lift-archetype-jpa-blank (Blank JPA archetype for Lift Web Framework.)
31: remote -> lift-archetype-jpa-blank-single (Blank JPA archetype for Lift Web Framework (single project).)
32: remote -> lift-archetype-jpa-blank-single_2.7.7 (Blank JPA archetype for Lift Web Framework (single project).)
33: remote -> lift-archetype-jpa-blank-single_2.8.0 (Blank JPA archetype for Lift Web Framework (single project).)
34: remote -> lift-archetype-jpa-blank_2.7.7 (Blank JPA archetype for Lift Web Framework.)
35: remote -> lift-archetype-jpa-blank_2.8.0 (Blank JPA archetype for Lift Web Framework.)
36: remote -> lift-archetype-sbt (Basic project archetype for Lift Web Framework (with database, logging, user management) using the sbt build system)
37: remote -> lift-archetype-sbt_2.7.7 (Basic project archetype for Lift Web Framework (with database, logging, user management) using the sbt build system)
38: remote -> lift-archetype-sbt_2.8.0 (Basic project archetype for Lift Web Framework (with database, logging, user management) using the sbt build system)
39: remote -> jlue-archetype-basic (Archetype - basic project for Jlue)
40: remote -> jlue-archetype-blank (Archetype - blank project for Jlue)
41: remote -> maven-archetype-har (null)
42: remote -> maven-archetype-sar (null)
43: remote -> maven-archetype-gwt (An archetype which contains a sample Maven GWT project.)
44: remote -> portletunit-portlet-archetype (An archetype that creates a simple porltet with unit tests.)
45: remote -> antlr3-maven-archetype (null)
46: remote -> camel-component (null)
47: remote -> camel-router (null)
48: remote -> camel-archetype-activemq (Creates a new Camel project that configures and interacts with ActiveMQ.)
49: remote -> camel-archetype-component (Creates a new Camel component.)
50: remote -> camel-archetype-java (Creates a new Camel project using Java DSL.)
51: remote -> camel-archetype-scala (Creates a new Camel project using Scala DSL.)
52: remote -> camel-archetype-spring (Creates a new Camel project with added Spring DSL support.)
53: remote -> camel-archetype-war (Creates a new Camel project that deploys the Camel Web Console, REST API, and your routes as a WAR)
54: remote -> cocoon-22-archetype-block (null)
55: remote -> cocoon-22-archetype-block-plain (null)
56: remote -> cocoon-22-archetype-webapp (null)
57: remote -> cocoon-archetype-block (null)
58: remote -> cocoon-archetype-parent (null)
59: remote -> cocoon-archetype-sample (null)
60: remote -> cocoon-archetype-webapp (null)
61: remote -> cxf-http-basic (null)
62: remote -> cxf-jaxws-javafirst (null)
63: remote -> apacheds-schema-archetype (null)
64: remote -> apacheds-testcase-archetype (null)
65: remote -> maven-ipojo-plugin (Maven Plugin to package iPOJO-powered bundles.)
66: remote -> geronimo-archetype-testsuite (Plugin to help create a testsuite)
67: remote -> geronimo-assembly-archetype (null)
68: remote -> geronimo-plugin-archetype (null)
69: remote -> geronimo-archetype-testsuite (Plugin to help create a testsuite)
70: remote -> geronimo-samples-archetype (Plugin to help create a samples project)
71: remote -> maven-archetype-archetype (An archetype which contains a sample archetype.)
72: remote -> maven-archetype-j2ee-simple (An archetype which contains a simplifed sample J2EE application.)
73: remote -> maven-archetype-marmalade-mojo (null)
74: remote -> maven-archetype-mojo (An archetype which contains a sample a sample Maven plugin.)
75: remote -> maven-archetype-plugin (An archetype which contains a sample Maven plugin.)
76: remote -> maven-archetype-plugin-site (An archetype which contains a sample Maven plugin site. This archetype can be layered upon an
existing Maven plugin project.)
77: remote -> maven-archetype-portlet (An archetype which contains a sample JSR-268 Portlet.)
78: remote -> maven-archetype-profiles (null)
79: remote -> maven-archetype-quickstart (An archetype which contains a sample Maven project.)
80: remote -> maven-archetype-site (An archetype which contains a sample Maven site which demonstrates some of the supported document types like
APT, XDoc, and FML and demonstrates how to i18n your site. This archetype can be layered
upon an existing Maven project.)
81: remote -> maven-archetype-site-simple (An archetype which contains a sample Maven site.)
82: remote -> maven-archetype-webapp (An archetype which contains a sample Maven Webapp project.)
83: remote -> myfaces-archetype-helloworld (Archetype to ease the burden of creating a new application based in myfaces)
84: remote -> myfaces-archetype-helloworld-facelets (Archetype to ease the burden of creating a new application based in myfaces and facelets)
85: remote -> myfaces-archetype-helloworld-portlets (Archetype to ease the burden of creating a new portlet application based in myfaces)
86: remote -> myfaces-archetype-jsfcomponents (Archetype to ease the burden of creating a library of JSF components)
87: remote -> myfaces-archetype-trinidad (Archetype to ease the burden of creating a new application based with Trinidad)
88: remote -> myfaces-archetype-trinidad (Archetype to ease the burden of creating a new application based with Trinidad)
89: remote -> application-archetype (Jetspeed-2 Maven2 Archetype used to generate portal application templates.)
90: remote -> component-archetype (Jetspeed-2 Maven2 Archetype used to generate component templates to
be used by other components and applications.)
91: remote -> jetspeed-archetype (Jetspeed 2 Maven Archetype)
92: remote -> portal-archetype (Jetspeed-2 Maven2 Archetype used to generate portal instances.)
93: remote -> portal-component-archetype (Jetspeed-2 Maven2 Archetype used to generate component templates to
be injected/installed as a library in the portal application itself.)
94: remote -> shared-component-archetype (Jetspeed-2 Maven2 Archetype used to generate component templates to
be installed as a shared library for all portlet/web applications.)
95: remote -> servicemix-bean-service-unit (null)
96: remote -> servicemix-binding-component (null)
97: remote -> servicemix-camel-service-unit (null)
98: remote -> servicemix-cxf-bc-service-unit (null)
99: remote -> servicemix-cxf-se-service-unit (null)
100: remote -> servicemix-cxf-se-wsdl-first-service-unit (null)
101: remote -> servicemix-drools-service-unit (null)
102: remote -> servicemix-eip-service-unit (null)
103: remote -> servicemix-embedded-simple (null)
104: remote -> servicemix-file-poller-service-unit (null)
105: remote -> servicemix-file-sender-service-unit (null)
106: remote -> servicemix-ftp-poller-service-unit (null)
107: remote -> servicemix-ftp-sender-service-unit (null)
108: remote -> servicemix-http-consumer-service-unit (null)
109: remote -> servicemix-http-provider-service-unit (null)
110: remote -> servicemix-jms-consumer-service-unit (null)
111: remote -> servicemix-jms-provider-service-unit (null)
112: remote -> servicemix-jsr181-annotated-service-unit (null)
113: remote -> servicemix-jsr181-wsdl-first-service-unit (null)
114: remote -> servicemix-lwcontainer-service-unit (null)
115: remote -> servicemix-ode-service-unit (null)
116: remote -> servicemix-osworkflow-service-unit (null)
117: remote -> servicemix-project-root (null)
118: remote -> servicemix-saxon-xquery-service-unit (null)
119: remote -> servicemix-saxon-xslt-service-unit (null)
120: remote -> servicemix-service-assembly (null)
121: remote -> servicemix-service-engine (null)
122: remote -> servicemix-service-unit (null)
123: remote -> servicemix-shared-library (null)
124: remote -> struts2-archetype-starter (null)
125: remote -> quickstart (Archetype for creating a basic Tapestry 5 application, including Eclipse control
files.)
126: remote -> tapestry-archetype (null)
127: remote -> tapestry-simple (Archetype for creating a basic Tapestry 5 application, including Eclipse control files.)
128: remote -> tuscany-contribution-jar (null)
129: remote -> tuscany-contribution-zip (null)
130: remote -> tuscany-quickstart (null)
131: remote -> tuscany-quickstart-bpel (null)
132: remote -> tuscany-quickstart-jsf (null)
133: remote -> tuscany-quickstart-jsonp (null)
134: remote -> tuscany-quickstart-stripes (null)
135: remote -> wicket-archetype-quickstart (null)
136: remote -> appfuse-basic-jsf (Maven 2 archetype that creates a web application with AppFuse embedded in it.)
137: remote -> appfuse-basic-spring (Maven 2 archetype that creates a web application with AppFuse embedded in it.)
138: remote -> appfuse-basic-struts (Maven 2 archetype that creates a web application with AppFuse embedded in it.)
139: remote -> appfuse-basic-tapestry (Maven 2 archetype that creates a web application with AppFuse embedded in it.)
140: remote -> appfuse-core (Maven 2 archetype that creates a backend (Managers, DAOs and Web Services)
application with AppFuse embedded in it.)
141: remote -> appfuse-modular-jsf (Maven 2 archetype that creates a modular web application with AppFuse. This archetype creates two modules:
"core" and "web". The core module depends on appfuse-service, while the web module depends on core as well
as AppFuse's JSF implementation.)
142: remote -> appfuse-modular-spring (Maven 2 archetype that creates a modular web application with AppFuse. This archetype creates two modules:
"core" and "web". The core module depends on appfuse-service, while the web module depends on core as well
as AppFuse's Spring MVC implementation.)
143: remote -> appfuse-modular-struts (Maven 2 archetype that creates a modular web application with AppFuse. This archetype creates two modules:
"core" and "web". The core module depends on appfuse-service, while the web module depends on core as well
as AppFuse's Struts implementation.)
144: remote -> appfuse-modular-tapestry (Maven 2 archetype that creates a modular web application with AppFuse. This archetype creates two modules:
"core" and "web". The core module depends on appfuse-service, while the web module depends on core as well
as AppFuse's Tapestry implementation.)
145: remote -> appfuse-basic-jsf (Maven 2 archetype that creates a web application with AppFuse embedded in it.)
146: remote -> appfuse-basic-jsf-archetype (AppFuse Archetype)
147: remote -> appfuse-basic-spring (Maven 2 archetype that creates a web application with AppFuse embedded in it.)
148: remote -> appfuse-basic-spring-archetype (AppFuse Archetype)
149: remote -> appfuse-basic-struts (Maven 2 archetype that creates a web application with AppFuse embedded in it.)
150: remote -> appfuse-basic-struts-archetype (AppFuse Archetype)
151: remote -> appfuse-basic-tapestry (Maven 2 archetype that creates a web application with AppFuse embedded in it.)
152: remote -> appfuse-basic-tapestry-archetype (AppFuse Archetype)
153: remote -> appfuse-core (Maven 2 archetype that creates a backend (Managers, DAOs and Web Services)
application with AppFuse embedded in it.)
154: remote -> appfuse-core-archetype (null)
155: remote -> appfuse-light-jsf-archetype (AppFuse Archetype)
156: remote -> appfuse-light-spring-archetype (AppFuse Archetype)
157: remote -> appfuse-light-spring-freemarker-archetype (AppFuse Archetype)
158: remote -> appfuse-light-spring-security-archetype (AppFuse Archetype)
159: remote -> appfuse-light-stripes-archetype (AppFuse Archetype)
160: remote -> appfuse-light-struts-archetype (AppFuse Archetype)
161: remote -> appfuse-light-tapestry-archetype (AppFuse Archetype)
162: remote -> appfuse-light-wicket-archetype (AppFuse Archetype)
163: remote -> appfuse-modular-jsf (Maven 2 archetype that creates a modular web application with AppFuse. This archetype creates two modules:
"core" and "web". The core module depends on appfuse-service, while the web module depends on core as well
as AppFuse's JSF implementation.)
164: remote -> appfuse-modular-jsf-archetype (AppFuse Archetype)
165: remote -> appfuse-modular-spring (Maven 2 archetype that creates a modular web application with AppFuse. This archetype creates two modules:
"core" and "web". The core module depends on appfuse-service, while the web module depends on core as well
as AppFuse's Spring MVC implementation.)
166: remote -> appfuse-modular-spring-archetype (AppFuse Archetype)
167: remote -> appfuse-modular-struts (Maven 2 archetype that creates a modular web application with AppFuse. This archetype creates two modules:
"core" and "web". The core module depends on appfuse-service, while the web module depends on core as well
as AppFuse's Struts implementation.)
168: remote -> appfuse-modular-struts-archetype (AppFuse Archetype)
169: remote -> appfuse-modular-tapestry (Maven 2 archetype that creates a modular web application with AppFuse. This archetype creates two modules:
"core" and "web". The core module depends on appfuse-service, while the web module depends on core as well
as AppFuse's Tapestry implementation.)
170: remote -> appfuse-modular-tapestry-archetype (AppFuse Archetype)
171: remote -> drools4-integration-helper-archetype (Support of the archetype for the Maven plugin)
172: remote -> drools5-integration-helper-archetype (This is an Maven 2 Archetype to support creation of a ready to
use Maven 2 project with Drools support. This archetype contains
examples of code based on interface, classes and pre/post
condition. JUnit 4 examples are also included.)
173: remote -> cargo-archetype-webapp-functional-tests-module (Sample Maven 2 Archetypes showing how to configure Cargo and Maven to run functional tests
for a webapp by creating a functional-tests module.)
174: remote -> cargo-archetype-webapp-single-module (Sample Maven 2 Archetypes showing how to configure Cargo and Maven to run functional tests
directly from a single webapp module.)
175: remote -> codegen-testcase (null)
176: remote -> cpa-testcase (null)
177: remote -> enunciate-simple-archetype (null)
178: remote -> gmaven-archetype-basic (null)
179: remote -> gmaven-archetype-mojo (null)
180: remote -> gmaven-archetype-basic (null)
181: remote -> gmaven-archetype-mojo (null)
182: remote -> maven-archetype-nbm (Archetype for Netbeans Modules Maven setup)
183: remote -> gwt-maven-plugin (Maven plugin for the Google Web Toolkit.)
184: remote -> latex-maven-archetype (The LaTeX Maven Archetype is kickstarts your LaTeX / Maven projects.)
185: remote -> xmlbeans-maven-plugin (Runs the xmlbeans parser/code generator against schemas in files and dependent jars.)
186: remote -> appframework (Archetype for creating application based on JSR 296)
187: remote -> ear-j2ee14 (Archetype for creating J2EE 1.4 EAR)
188: remote -> ear-javaee6 (Archetype for creating Java EE 6 EAR)
189: remote -> ear-jee5 (Archetype for creating JEE 5 EAR)
190: remote -> ejb-j2ee14 (An archetype which contains a sample J2EE 1.4 EJB Maven project.)
191: remote -> ejb-javaee6 (Java EE 6 ejb jar archetype)
192: remote -> ejb-jee5 (JEE 5 ejb jar archetype)
193: remote -> nbm-archetype (Archetype for development of NetBeans modules in Maven.)
194: remote -> netbeans-platform-app-archetype (Archetype for sample application based on NetBeans platform. Creates parent pom with branding and empty NBM project.)
195: remote -> pom-root (Root project archetype for creating multi module projects)
196: remote -> webapp-j2ee14 (J2EE 1.4 web application archetype)
197: remote -> webapp-javaee6 (Java EE 6 web application archetype)
198: remote -> webapp-jee5 (JEE 5 web application archetype)
199: remote -> groovy-maven-archetype (An archetype for creating Maven modules/projects using the Groovy language.)
200: remote -> groovy-mojo-archetype (An archetype for writing Maven 2 plugins in the Groovy language.)
201: remote -> org.openxma.dsl.sample-archetype (null)
202: remote -> sonar-basic-plugin-archetype (Maven archetype to create a basic Sonar plugin)
203: remote -> sonar-gwt-plugin-archetype (Maven archetype to create a Sonar plugin including GWT pages)
204: remote -> cometd-archetype-dojo-jetty6 (null)
205: remote -> cometd-archetype-dojo-jetty7 (null)
206: remote -> cometd-archetype-jquery-jetty6 (null)
207: remote -> cometd-archetype-jquery-jetty7 (null)
208: remote -> coos-plugin-actor (null)
209: remote -> coos-plugin-api (null)
210: remote -> coos-plugin-noapi (null)
211: remote -> jee6-basic-archetype (Basic Java EE application with just configuration for CDI, JSF, JPA and a sample empty page.)
212: remote -> jee6-minimal-archetype (Minimal Java EE application with a single page demo of CDI, JSF, JPA and Validation to verify everything works.)
213: remote -> jee6-sandbox-archetype (Sandbox project for Java EE 6 with CDI, JSF, JPA and a sample model and test data to play around with, try new things, and use as a foundation for tutorials)
214: remote -> jee6-sandbox-demo-archetype (Complete demo example using CDI, JSF, JPA and validation showcasing a number of features available in Java EE 6 as well as demonstrating how to make them all work together)
215: remote -> jee6-servlet-basic-archetype (Java EE application for servlet containers (Jetty,Tomcat) with just a single page and a persistence provider .)
216: remote -> jee6-servlet-demo-archetype (Bookmarking application demonstrating JSF, CDI, JPA and Bean Validation on Tomcat/Jetty servlet containers)
217: remote -> jee6-servlet-minimal-archetype (Minimal Java EE application for servlet containers (Jetty,Tomcat) with a single page demo of CDI, JSF, JPA and Validation to verify everything works.)
218: remote -> jee6-servlet-sandbox-archetype (Java EE 6 archetype for servlet containers (Jetty,Tomcat) with sandbox data built in.)
219: remote -> scalate-archetype-empty (An archetype which creates an empty Scalate web application)
220: remote -> scalate-archetype-guice (An archetype which creates an empty Scalate Guice web application)
221: remote -> geomajas-gwt-archetype (Geomajas GWT application archetype)
222: remote -> geoserver-archetype-wfsoutputformat (null)
223: remote -> grails-maven-archetype (null)
224: remote -> imixs-workflow-jee-archetype (Imixs Workflow JEE Archetype provides a JEE Sample Application)
225: remote -> jboss-javaee6-webapp (An archetype that generates a starter Java EE 6 webapp project)
226: remote -> weld-jsf-jee (Weld archetype for creating a Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1 and JPA 2.0 (persistence unit included))
227: remote -> weld-jsf-jee-minimal (Weld archetype for creating a minimal Java EE 6 application using JSF 2.0, CDI 1.0 and EJB 3.1 (persistence unit not included))
228: remote -> weld-jsf-servlet-minimal (Weld archetype for creating an application using JSF 2.0 and CDI 1.0 for Servlet Containers (Tomcat 6 / Jetty 6))
229: remote -> jbundle-util-webapp-cgi-archetype (null)
230: remote -> jbundle-util-webapp-files-archetype (null)
231: remote -> jbundle-util-webapp-proxy-archetype (null)
232: remote -> jbundle-util-webapp-redirect-archetype (null)
233: remote -> jbundle-util-webapp-upload-archetype (null)
234: remote -> jbundle-util-webapp-webdav-archetype (null)
235: remote -> jbundle-util-webapp-website-archetype (null)
236: remote -> jbundle-util-webapp-webstart-archetype (null)
237: remote -> jini-service-archetype (Archetype for Jini service project creation)
238: remote -> maven-hpi-plugin (Maven2 plugin for developing Hudson plugins)
239: remote -> makumba-archetype (Archetype for a makumba web-application)
240: remote -> ibean-archetype (An archetype for creating an empty ibean maven project)
241: remote -> mule-example-archetype (An archetype for creating a Mule example application.)
242: remote -> mule-module-archetype (An architype for creating a Mule Module. It provides options for adding certain mule features and configuring the
module for Muleforge.)
243: remote -> mule-project-archetype (An architype for creating Mule applications.)
244: remote -> mule-transport-archetype (Archetype for Mule 2.0 and above transport projects.)
245: remote -> multiverse-project-archetype (Skeleton for a project using Multiverse)
246: remote -> application-archetype (null)
247: remote -> remoting-support (null)
248: remote -> application (null)
249: remote -> hibernate-support (null)
250: remote -> html-war (null)
251: remote -> htmlviewer-war (null)
252: remote -> application (null)
253: remote -> icons (null)
254: remote -> maven-archetype-cecilia-app (This archetype is useful to quick start Cecilia applications,
having a source tree template already filled.)
255: remote -> maven-archetype-cecilia-application (This archetype is useful to quick start Cecilia applications, having a
source tree template already filled.)
256: remote -> maven-archetype-cecilia-library (This archetype is useful to quick start Cecilia components library
projects, having a source tree template already filled.)
257: remote -> maven-archetype-petals-jbi-binding-component (>This project is Maven 2 archetype associated to a JBI binding component project.)
258: remote -> maven-archetype-petals-jbi-service-assembly (This project is Maven 2 archetype associated to a JBI service assembly project.)
259: remote -> maven-archetype-petals-jbi-service-engine (This project is Maven 2 archetype associated to a JBI service engine project.)
260: remote -> maven-archetype-petals-jbi-service-unit (This project is Maven 2 archetype associated to a JBI service unit project.)
261: remote -> maven-archetype-osgi-bundle (null)
262: remote -> maven-archetype-osgi-project (null)
263: remote -> maven-archetype-osgi-service (null)
264: remote -> maven-archetype-osgi-wrapper (null)
265: remote -> maven-archetype-spring-bean (null)
266: remote -> maven-archetype-paxexam-junit ()
267: remote -> kerneos-module-archetype (null)
268: remote -> kerneos-war-archetype (null)
269: remote -> maven-archetype-petals-jbi-binding-component (This project is Maven 2 archetype associated to a JBI binding component project.)
270: remote -> maven-archetype-petals-jbi-service-assembly (This project is Maven 2 archetype associated to a JBI service assembly project.)
271: remote -> maven-archetype-petals-jbi-service-engine (This project is Maven 2 archetype associated to a JBI service engine project.)
272: remote -> maven-archetype-petals-jbi-service-unit (This project is Maven 2 archetype associated to a JBI service unit project.)
273: remote -> maven-archetype-petals-jbi-shared-library (This project is Maven 2 archetype associated to a JBI Shared Library project.)
274: remote -> parancoe-pluginarchetype (null)
275: remote -> parancoe-webarchetype (null)
276: remote -> liftweb-archetype-blank (Archetype - blank project for liwftweb)
277: remote -> liftweb-archetype-hellolift (Archetype - hellolift sample liwftweb application)
278: remote -> scala-archetype-simple (null)
279: remote -> slf4j-archetype (The slf4j Archetype)
280: remote -> flexmojos-archetypes-application (null)
281: remote -> flexmojos-archetypes-library (null)
282: remote -> flexmojos-archetypes-modular-webapp (null)
283: remote -> nexus-plugin-archetype (null)
284: remote -> spring-osgi-bundle-archetype (Spring OSGi Maven2 Archetype)
285: remote -> spring-ws-archetype (Spring Web Services Maven2 Archetype.)
286: remote -> trails-archetype (null)
287: remote -> trails-secure-archetype (null)
288: remote -> tynamo-archetype (null)
289: remote -> wicket-scala-archetype (Basic setup for a project that combines Scala and Wicket,
depending on the Wicket-Scala project. Includes an example Specs
test.)
290: remote -> circumflex-archetype (null)