How to Install and Uninstall maven-archetype.noarch Package on Fedora 34
Last updated: November 27,2024
1. Install "maven-archetype.noarch" package
Please follow the instructions below to install maven-archetype.noarch on Fedora 34
$
sudo dnf update
Copied
$
sudo dnf install
maven-archetype.noarch
Copied
2. Uninstall "maven-archetype.noarch" package
Please follow the steps below to uninstall maven-archetype.noarch on Fedora 34:
$
sudo dnf remove
maven-archetype.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the maven-archetype.noarch package on Fedora 34
Last metadata expiration check: 1:15:04 ago on Tue Sep 6 08:10:37 2022.
Available Packages
Name : maven-archetype
Version : 3.2.0
Release : 2.fc34
Architecture : noarch
Size : 17 k
Source : maven-archetype-3.2.0-2.fc34.src.rpm
Repository : fedora
Summary : Maven project templating toolkit
URL : https://maven.apache.org/archetype/
License : ASL 2.0 and ASL 1.1
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.
Available Packages
Name : maven-archetype
Version : 3.2.0
Release : 2.fc34
Architecture : noarch
Size : 17 k
Source : maven-archetype-3.2.0-2.fc34.src.rpm
Repository : fedora
Summary : Maven project templating toolkit
URL : https://maven.apache.org/archetype/
License : ASL 2.0 and ASL 1.1
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.