Пакет maven-archetype: Specfile
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 | Epoch: 0 Group: Development/Java # BEGIN SourceDeps(oneline): BuildRequires: rpm-build-java unzip # END SourceDeps(oneline) BuildRequires: /proc BuildRequires: jpackage-generic-compat # see https://bugzilla.altlinux.org/show_bug.cgi?id=10382 %define _localstatedir %{_var} Name: maven-archetype Version: 2.4 Release: alt1_8jpp8 Summary: Maven project templating toolkit # Most of the code is under ASL 2.0, but some bundled jdom sources are # under ASL 1.1 License: ASL 2.0 and ASL 1.1 URL: https://maven.apache.org/archetype/ Source0: http://repo.maven.apache.org/maven2/org/apache/maven/archetype/%{name}/%{version}/%{name}-%{version}-source-release.zip Patch1: 0001-Add-Maven-3-compatibility.patch Patch2: 0002-Fix-jetty-namespace.patch Patch3: 0003-Port-to-current-plexus-utils.patch BuildArch: noarch BuildRequires: maven-local BuildRequires: mvn(commons-collections:commons-collections) BuildRequires: mvn(commons-io:commons-io) BuildRequires: mvn(dom4j:dom4j) BuildRequires: mvn(jdom:jdom) BuildRequires: mvn(junit:junit) BuildRequires: mvn(net.sourceforge.jchardet:jchardet) BuildRequires: mvn(org.apache.felix:maven-bundle-plugin) BuildRequires: mvn(org.apache.maven:maven-compat) BuildRequires: mvn(org.apache.maven:maven-core) BuildRequires: mvn(org.apache.maven:maven-model) BuildRequires: mvn(org.apache.maven:maven-parent:pom:) BuildRequires: mvn(org.apache.maven:maven-plugin-api) BuildRequires: mvn(org.apache.maven:maven-project) BuildRequires: mvn(org.apache.maven.plugins:maven-dependency-plugin) BuildRequires: mvn(org.apache.maven.plugins:maven-plugin-plugin) BuildRequires: mvn(org.apache.maven.shared:maven-invoker) BuildRequires: mvn(org.apache.maven.shared:maven-plugin-testing-harness) BuildRequires: mvn(org.apache.maven.shared:maven-script-interpreter) BuildRequires: mvn(org.apache.maven.wagon:wagon-file) BuildRequires: mvn(org.apache.maven.wagon:wagon-http) BuildRequires: mvn(org.apache.velocity:velocity) BuildRequires: mvn(org.beanshell:bsh) BuildRequires: mvn(org.codehaus.modello:modello-maven-plugin) BuildRequires: mvn(org.codehaus.plexus:plexus-component-annotations) BuildRequires: mvn(org.codehaus.plexus:plexus-component-metadata) BuildRequires: mvn(org.codehaus.plexus:plexus-container-default) BuildRequires: mvn(org.codehaus.plexus:plexus-interactivity-api) BuildRequires: mvn(org.codehaus.plexus:plexus-utils) BuildRequires: mvn(org.codehaus.plexus:plexus-velocity) Source44: import.info Provides: maven-archetype2 = %version Obsoletes: maven-archetype2 < %version %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. %package javadoc Group: Development/Java Summary: API documentation for %{name} BuildArch: noarch %description javadoc %{summary}. %package catalog Group: Development/Java Summary: Maven Archetype Catalog model %description catalog %{summary}. %package descriptor Group: Development/Java Summary: Maven Archetype Descriptor model %description descriptor %{summary}. %package registry Group: Development/Java Summary: Maven Archetype Registry model %description registry %{summary}. %package common Group: Development/Java Summary: Maven Archetype common classes %description common %{summary}. %package packaging Group: Development/Java Summary: Maven Archetype packaging configuration for archetypes %description packaging %{summary}. %package -n %{name}-plugin Group: Development/Java Summary: Maven Plugin for using archetypes %description -n %{name}-plugin %{summary}. %prep %setup -q %patch1 -p1 %patch2 -p1 %patch3 -p1 # useless in packaging %pom_remove_plugin -r :apache-rat-plugin # Add OSGI info to catalog and descriptor jars pushd archetype-models/archetype-catalog %pom_xpath_remove "pom:project/pom:packaging" %pom_xpath_inject "pom:project" "<packaging>bundle</packaging>" %pom_xpath_inject "pom:build/pom:plugins" " <plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <extensions>true</extensions> <configuration> <instructions> <_nouses>true</_nouses> <Export-Package>org.apache.maven.archetype.catalog.*</Export-Package> </instructions> </configuration> </plugin>" popd pushd archetype-models/archetype-descriptor %pom_xpath_remove "pom:project/pom:packaging" %pom_xpath_inject "pom:project" "<packaging>bundle</packaging>" %pom_xpath_inject "pom:build/pom:plugins" " <plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <extensions>true</extensions> <configuration> <instructions> <_nouses>true</_nouses> <Export-Package>org.apache.maven.archetype.metadata.*</Export-Package> </instructions> </configuration> </plugin>" popd # groovy is not really needed %pom_remove_dep org.codehaus.groovy:groovy maven-archetype-plugin/pom.xml %pom_disable_module archetype-testing %pom_remove_plugin org.apache.maven.plugins:maven-antrun-plugin archetype-common/pom.xml %build %mvn_package :archetype-models maven-archetype # we don't have cargo so skip tests for now %mvn_build -s -f %install %mvn_install %files -f .mfiles-maven-archetype %doc LICENSE NOTICE %files catalog -f .mfiles-archetype-catalog %files descriptor -f .mfiles-archetype-descriptor %files registry -f .mfiles-archetype-registry %files common -f .mfiles-archetype-common %files packaging -f .mfiles-archetype-packaging %files -n %{name}-plugin -f .mfiles-maven-archetype-plugin %files javadoc -f .mfiles-javadoc %doc LICENSE %changelog * Thu May 31 2018 Igor Vlasenko <viy@altlinux.ru> 0:2.4-alt1_8jpp8 - java update * Thu Nov 09 2017 Igor Vlasenko <viy@altlinux.ru> 0:2.4-alt1_7jpp8 - fc27 update * Sun Oct 22 2017 Igor Vlasenko <viy@altlinux.ru> 0:2.4-alt1_5jpp8 - new jpp release * Fri Dec 16 2016 Igor Vlasenko <viy@altlinux.ru> 0:2.4-alt1_3jpp8 - new fc release * Fri Nov 25 2016 Igor Vlasenko <viy@altlinux.ru> 0:2.4-alt1_2jpp8 - new version * Wed Feb 03 2016 Igor Vlasenko <viy@altlinux.ru> 0:2.3-alt1_2jpp8 - new version * Wed Jan 20 2016 Igor Vlasenko <viy@altlinux.ru> 0:2.3-alt0.1jpp - bootstrap pack of jars created with jppbootstrap script - temporary package to satisfy circular dependencies * Mon Sep 08 2014 Igor Vlasenko <viy@altlinux.ru> 0:2.2-alt1_3jpp7 - new release * Mon Aug 25 2014 Igor Vlasenko <viy@altlinux.ru> 0:2.2-alt1_1jpp7 - new release * Fri Aug 08 2014 Igor Vlasenko <viy@altlinux.ru> 0:2.1-alt5_7jpp7 - rebuild with maven-local * Fri Jul 18 2014 Igor Vlasenko <viy@altlinux.ru> 0:2.1-alt4_7jpp7 - fixed build * Mon Jul 14 2014 Igor Vlasenko <viy@altlinux.ru> 0:2.1-alt3_7jpp7 - NMU rebuild to move poms and fragments * Tue Sep 11 2012 Igor Vlasenko <viy@altlinux.ru> 0:2.1-alt2_7jpp7 - fixed build * Fri Aug 24 2012 Igor Vlasenko <viy@altlinux.ru> 0:2.1-alt1_7jpp7 - new version * Fri Jun 22 2012 Igor Vlasenko <viy@altlinux.ru> 0:2.0-alt0.1jpp - bootstrap pack of jars created with jppbootstrap script - temporary package to satisfy circular dependencies |