| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
| Name: maven-archetype | Distribution: openSUSE:Factory:zSystems |
| Version: 3.2.1 | Vendor: openSUSE |
| Release: 3.2 | Build date: Wed Feb 21 11:49:37 2024 |
| Group: Unspecified | Build host: reproducible |
| Size: 27142 | Source RPM: maven-archetype-3.2.1-3.2.src.rpm |
| Packager: https://bugs.opensuse.org | |
| Url: https://maven.apache.org/archetype/ | |
| Summary: Maven project templating toolkit | |
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.
Apache-2.0
* Wed Feb 21 2024 Gus Kenion <gus.kenion@suse.com>
- Use %patch -P N instead of deprecated %patchN.
* Sat Sep 09 2023 Fridrich Strba <fstrba@suse.com>
- Reproducible builds: use SOURCE_DATE_EPOCH for timestamp
* Thu Apr 28 2022 Fridrich Strba <fstrba@suse.com>
- Upgrade to version 3.2.1
- Added patches:
* 0001-Avoid-reliance-on-groovy.patch
+ Groovy is only used for running a post generation script,
removing this continues the old behaviour of ignoring it
* port-to-maven-script-interpreter-1_3.patch
+ Adapt to the new function signatures in
maven-script-interpreter-1.3
* Tue Dec 29 2020 Wang Jun <jgwang@suse.com>
- Update to version 3.2.0
* Allow skip non-archetypes
* http to central not supported anymore, switch to https
* Use HTTPS instead of HTTP to resolve dependencies
* Fixed newlines broken
* Fixed license header
* Fix referenced parameter
* Fix NullPointerException
* Update jdom, commons-io, artifact transfer and JUnit
* Update plexus, xmlunit and ivy
* Update EasyMock
* Make build Reproducible
* Make archetype:jar reproductible
* Reset relativePath to remove build warnings
* Drop maven version from message
* Wed Feb 26 2020 Fridrich Strba <fstrba@suse.com>
- Initial packaging of maven-archetype 3.1.2
/usr/share/doc/packages/maven-archetype /usr/share/doc/packages/maven-archetype/NOTICE /usr/share/licenses/maven-archetype /usr/share/licenses/maven-archetype/LICENSE /usr/share/maven-metadata/maven-archetype-maven-archetype.xml /usr/share/maven-poms/maven-archetype /usr/share/maven-poms/maven-archetype/archetype-models.pom /usr/share/maven-poms/maven-archetype/maven-archetype.pom
Generated by rpm2html 1.8.1
Fabrice Bellet, Tue Apr 9 12:43:14 2024