How to Install and Uninstall maven-archetype Package on openSuSE Tumbleweed

Last updated: December 25,2024

1. Install "maven-archetype" package

Please follow the guidance below to install maven-archetype on openSuSE Tumbleweed

$ sudo zypper refresh $ sudo zypper install maven-archetype

2. Uninstall "maven-archetype" package

This is a short guide on how to uninstall maven-archetype on openSuSE Tumbleweed:

$ sudo zypper remove maven-archetype

3. Information about the maven-archetype package on openSuSE Tumbleweed

Information for package maven-archetype:
----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : maven-archetype
Version : 3.2.1-3.1
Arch : noarch
Vendor : openSUSE
Installed Size : 26.5 KiB
Installed : No
Status : not installed
Source package : maven-archetype-3.2.1-3.1.src
Upstream URL : https://maven.apache.org/archetype/
Summary : Maven project templating toolkit
Description :
Archetype is a Maven project templating toolkit. An archetype is
defined as an original pattern or model from which all other things of
the same kind are made. The names fits as we are trying to provide a
system that provides a consistent means of generating Maven
projects. Archetype will help authors create Maven project templates
for users, and provides users with the means to generate parameterized
versions of those project templates.
Using archetypes provides a great way to enable developers quickly in
a way consistent with best practices employed by your project or
organization. Within the Maven project we use archetypes to try and
get our users up and running as quickly as possible by providing a
sample project that demonstrates many of the features of Maven while
introducing new users to the best practices employed by Maven. In a
matter of seconds a new user can have a working Maven project to use
as a jumping board for investigating more of the features in Maven. We
have also tried to make the Archetype mechanism additive and by that
we mean allowing portions of a project to be captured in an archetype
so that pieces or aspects of a project can be added to existing
projects. A good example of this is the Maven site archetype. If, for
example, you have used the quick start archetype to generate a working
project you can then quickly create a site for that project by using
the site archetype within that existing project. You can do anything
like this with archetypes.
You may want to standardize J2EE development within your organization
so you may want to provide archetypes for EJBs, or WARs, or for your
web services. Once these archetypes are created and deployed in your
organization's repository they are available for use by all developers
within your organization.