[javapackages] [doc] Add section for jpackage_script
by Stanislav Ochotnicky
commit f255e1f2b439315f18739ac58437ac9fd15cb010
Author: Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Date: Thu Mar 7 17:58:55 2013 +0100
[doc] Add section for jpackage_script
doc/index.txt | 29 +++++++++++++++++++++++++++++
1 files changed, 29 insertions(+), 0 deletions(-)
---
diff --git a/doc/index.txt b/doc/index.txt
index 40bed54..cb7985d 100644
--- a/doc/index.txt
+++ b/doc/index.txt
@@ -231,6 +231,35 @@ This form should be used when a package consists of multiple jar files that are
installed into a subdirectory of `%{_javadir}`. Note that in this case, the POM
file name includes the optional subdirectory field.
+==== Generating Application Shell Scripts
+As mentioned in section about xref:XFor_Packagers[Java packaging basics], all
+Java applications need wrapper shell scripts to setup the environment before
+running JVM and associated Java code.
+
+
+The jpackage-utils package contains a convenience `%jpackage_script` macro that
+can be used to create scripts that work for the majority of packages. See its
+definition and documentation in `/etc/rpm/macros.jpackage`. One thing to pay
+attention to is the 6th argument to it - whether to prefer a JRE over a full SDK
+when looking up a JVM to invoke - most packages that don't require the full Java
+SDK will want to set that to `true` to avoid unexpected results when looking up
+a JVM when some of the installed JRE's don't have the corresponding SDK (*-devel
+package) installed.
+
+[source,spec]
+--------
+%install
+...
+%jpackage_script msv.textui.Driver "" "" msv-msv:msv-xsdlib:relaxngDatatype:isorelax msv true
+...
+--------
+
+The previous example installs the "msv" script (5th argument) with main class
+being msv.textui.Driver (1st argument). No optional flags (2nd argument) or
+options (3rd argument) are used. This script will add several libraries to
+classpath before executing main class (4th argument, jars separated with
+":"). `build-classpath` is run on every part of 4th argument to create full
+classpaths.
== Build systems
11 years, 3 months
[javapackages] [doc] Add initial information for packagers
by Stanislav Ochotnicky
commit ec94e4a1a902b6466fd5ac5414324c595da53b8b
Author: Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Date: Thu Mar 7 17:51:23 2013 +0100
[doc] Add initial information for packagers
doc/basics.txt | 30 ++++++++++++++++++++++++------
1 files changed, 24 insertions(+), 6 deletions(-)
---
diff --git a/doc/basics.txt b/doc/basics.txt
index 57ecd2b..173d3fb 100644
--- a/doc/basics.txt
+++ b/doc/basics.txt
@@ -1,18 +1,36 @@
This section includes basic introduction to Java packaging world to people
coming from different backgrounds. Goal is to understand language of all groups
involved. If you are a Java developer coming into contact with RPM packaging for
-the first time start reading xref:Xbasic_devs[Java developer] section. On the
+the first time start reading xref:XFor_Devs[Java developer] section. On the
other hand if you are coming from RPM packaging background an
-xref:Xbasic_packagers[introduction to Java world] is probably better starting point.
+xref:XFor_Packagers[introduction to Java world] is probably a better starting
+point.
+It should be noted that especially in this section we might sacrifice
+correctness for simplicity
-[[Xbasic_packagers]]
+[[XFor_Packagers]]
=== For Packagers
-Packagers!
+Java is a programming language which is usually compiled into bytecode for JVM
+(Java Virtual Machine). For more details about the JVM and bytecode
+specification see
+link:http://docs.oracle.com/javase/specs/jvms/se7/html/index.html[JVM
+documentation]. Resulting bytecode is then assembled into zip files with
+specific layout and additional metadata. Most commonly these special zip files
+have `.jar` suffix, but other variations exist. These files have their format
+specified in the
+link:http://docs.oracle.com/javase/7/docs/technotes/guides/jar/jar.html[JAR File
+Specification].
+Classic compiled applications use linker to find dependencies (linked
+libraries), Python interpreter has predefined directories where it searches for
+imported modules. JVM itself has no embedded knowledge of installation paths and
+thus no automatic way to resolve dependencies of Java projects. This means that
+all Java applications have to use wrapper shell scripts to setup the environment
+before invoking the JVM and running the application itself.
+// JVM, classpaths, imports, POM files, JAR files
-
-[[Xbasic_devs]]
+[[XFor_Devs]]
=== For Java Developers
Developers!
11 years, 3 months
[javapackages] [doc] Start basic section
by Stanislav Ochotnicky
commit 645c036516ab7486e2e2c324891f1c0709f7d05b
Author: Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Date: Thu Mar 7 16:53:19 2013 +0100
[doc] Start basic section
doc/basics.txt | 18 ++++++++++++++++++
doc/index.txt | 4 +---
2 files changed, 19 insertions(+), 3 deletions(-)
---
diff --git a/doc/basics.txt b/doc/basics.txt
new file mode 100644
index 0000000..57ecd2b
--- /dev/null
+++ b/doc/basics.txt
@@ -0,0 +1,18 @@
+This section includes basic introduction to Java packaging world to people
+coming from different backgrounds. Goal is to understand language of all groups
+involved. If you are a Java developer coming into contact with RPM packaging for
+the first time start reading xref:Xbasic_devs[Java developer] section. On the
+other hand if you are coming from RPM packaging background an
+xref:Xbasic_packagers[introduction to Java world] is probably better starting point.
+
+
+[[Xbasic_packagers]]
+=== For Packagers
+Packagers!
+
+
+
+
+[[Xbasic_devs]]
+=== For Java Developers
+Developers!
diff --git a/doc/index.txt b/doc/index.txt
index d768020..40bed54 100644
--- a/doc/index.txt
+++ b/doc/index.txt
@@ -15,9 +15,7 @@ software on Fedora.
:numbered:
== The Basics
-This section includes basic introduction to Java world, describes `jar` file
-contents and basically describes to people unfamiliar with Java world enough to
-understand Java packaging later on.
+include::basics.txt[]
== Packaging principles
11 years, 3 months
[javapackages] [doc] Use uppercase POM consistently
by Stanislav Ochotnicky
commit 482c4d3856b4f73335d5dd4386682addfc074dc4
Author: Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Date: Thu Mar 7 15:29:24 2013 +0100
[doc] Use uppercase POM consistently
doc/index.txt | 40 ++++++++++++++++++++--------------------
1 files changed, 20 insertions(+), 20 deletions(-)
---
diff --git a/doc/index.txt b/doc/index.txt
index 9e7041c..d768020 100644
--- a/doc/index.txt
+++ b/doc/index.txt
@@ -144,12 +144,12 @@ Using `%pom_*` macros not only increases readability of the spec file, but also
Maven identifies jar files by a set of strings: groupId, artifactId and version
(mostly). To let mvn-rpmbuild know what groupId:artifactId corresponds to which
-pom or jar file, we use the `%add_maven_depmap`
+POM or jar file, we use the `%add_maven_depmap`
macro. `%add_maven_depmap` reads the groupId and artifactId from the
-pom file and creates a file in `%{_mavendepmapfragdir}` that maps
+POM file and creates a file in `%{_mavendepmapfragdir}` that maps
groupId:artifactId pairs to jar files under `%{_javadir}`. All
fragments in this directory are read by mvn-rpmbuild during startup, allowing
-the locally installed jar files and poms to be used as a maven repository.
+the locally installed jar and POM files to be used as a maven repository.
Note that -- unless you use the `-f` option as shown below -- all
depmap fragments for a given package are written to the same file,
@@ -157,7 +157,7 @@ depmap fragments for a given package are written to the same file,
file in the `%files` section of your RPM.
For the macro to work properly, all jar files must be copied into `%{_javadir}`
-and all pom files must be copied into `%{_mavenpomdir}` and given file names of
+and all POM files must be copied into `%{_mavenpomdir}` and given file names of
the following form, where `jarname` is the name of the jar without the .jar
suffix:
@@ -168,30 +168,30 @@ suffix:
Note that the subdirectory is only necessary if the jar file is put into a subdirectory of `%{_javadir}`. For example:
-* For junit, the jar is `%{_javadir}/junit.jar`, so the pom would be
+* For junit, the jar is `%{_javadir}/junit.jar`, so the POM would be
`%{_mavenpomdir}/JPP-junit.pom`.
* For plexus-ant-factory, the jar is `%{_javadir}/plexus/ant-factory.jar`, so
- the pom would named `%{_mavenpomdir}/JPP.plexus-ant-factory.pom`.
+ the POM would named `%{_mavenpomdir}/JPP.plexus-ant-factory.pom`.
-If a pom is installed with no corresponding jar file -- for example, for parent
-poms -- the same convention should be followed:
+If a POM is installed with no corresponding jar file -- for example, for parent
+POM files -- the same convention should be followed:
-* The Apache commons parent pom is installed in
+* The Apache commons parent POM is installed in
`%{_mavenpomdir}/JPP-commons-parent.pom`.
-In its simplest form (a pom without a jar file), `%add_maven_depmap` looks like this:
+In its simplest form (a POM without a jar file), `%add_maven_depmap` looks like this:
-.Parent pom
+.Parent POM
[source,spec]
--------
%add_maven_depmap JPP-%{name}.pom
--------
-This will read the pom file in question and provide a mapping between the
-groupId and artifactId inside the pom file and the pom file placed into
+This will read the POM file in question and provide a mapping between the
+groupId and artifactId inside the POM file and the POM file placed into
`%{_mavenpomdir}`.
-For a pom that maps directly to a jar file, the following is the correct form:
+For a POM that maps directly to a jar file, the following is the correct form:
.Standard invocation
[source,spec]
@@ -199,20 +199,20 @@ For a pom that maps directly to a jar file, the following is the correct form:
%add_maven_depmap JPP-%{name}.pom %{name}.jar
--------
-In addition to creating the pom mapping, this will also ensure that the correct
-jar is associated with the groupId and artifactId from the pom.
+In addition to creating the POM mapping, this will also ensure that the correct
+jar is associated with the groupId and artifactId from the POM.
.Providing additional artifact mappings
[source,spec]
--------
%add_maven_depmap JPP-%{name}.pom %{name}.jar -a "org.apache.commons:commons-lang"
--------
-This form also adds additional mappings for given pom/jar file. For example, if
-the pom file indicates that it contains groupId commons-lang, artifactId
+This form also adds additional mappings for given POM/jar file. For example, if
+the POM file indicates that it contains groupId commons-lang, artifactId
commons-lang, this form ensures that we also add a mapping between groupId
org.apache.commons and the installed jar/pom files. This is necessary in cases
where the groupId or artifactId may have changed, and other packages might
-require different IDs than those reflected in the installed pom.
+require different IDs than those reflected in the installed POM.
.Multiple subpackages
[source,spec]
@@ -230,7 +230,7 @@ subpackages where each has its own jar files.
--------
This form should be used when a package consists of multiple jar files that are
-installed into a subdirectory of `%{_javadir}`. Note that in this case, the pom
+installed into a subdirectory of `%{_javadir}`. Note that in this case, the POM
file name includes the optional subdirectory field.
11 years, 3 months
[javapackages] [doc] Add more complex xpath example for pom_ macro
by Stanislav Ochotnicky
commit 01b099523c44671b466c35d650c6389df88e78be
Author: Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Date: Thu Mar 7 15:26:19 2013 +0100
[doc] Add more complex xpath example for pom_ macro
doc/index.txt | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
---
diff --git a/doc/index.txt b/doc/index.txt
index a2cb633..9e7041c 100644
--- a/doc/index.txt
+++ b/doc/index.txt
@@ -119,6 +119,14 @@ some examples for these macros.
<artifactId>awesomeproject</artifactId>
<version>1.0.0.GA</version>
</dependency>"
+
+# Use a bit more complex XPath to add additional exclusion into
+# maven-wagon dependency
+%pom_xpath_inject "pom:dependency[pom:artifactId[text()='maven-wagon']]/pom:exclusions" "
+ <exclusion>
+ <groupId>antlr</groupId>
+ <artifactId>antlr</artifactId>
+ </exclusion>"
--------
.Handling XML namespaces
11 years, 3 months
[javapackages] [doc] Remove reference to wiki anchor
by Stanislav Ochotnicky
commit 5b560c34bb406dab3ac7950b19daf179464ebf1e
Author: Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Date: Thu Mar 7 15:19:22 2013 +0100
[doc] Remove reference to wiki anchor
doc/index.txt | 9 ++++-----
1 files changed, 4 insertions(+), 5 deletions(-)
---
diff --git a/doc/index.txt b/doc/index.txt
index 12a44bb..a2cb633 100644
--- a/doc/index.txt
+++ b/doc/index.txt
@@ -148,11 +148,10 @@ depmap fragments for a given package are written to the same file,
`%{_mavendepmapfragdir}/%{name}`. You should be sure to include this
file in the `%files` section of your RPM.
-For the macro to work properly, all jar files must be copied into
-`%{_javadir}` (see [[#JAR_file_installation|JAR file installation]]),
-and all pom files must be copied into `%{_mavenpomdir}` and given
-file names of the following form, where `jarname` is the name of the
-jar without the .jar suffix:
+For the macro to work properly, all jar files must be copied into `%{_javadir}`
+and all pom files must be copied into `%{_mavenpomdir}` and given file names of
+the following form, where `jarname` is the name of the jar without the .jar
+suffix:
[source,spec]
--------
11 years, 3 months
[javapackages] [doc] Move maven part into separate file
by Stanislav Ochotnicky
commit 261a8c014c5e0f6042ca037128bcd15d16a1471a
Author: Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Date: Thu Mar 7 15:13:25 2013 +0100
[doc] Move maven part into separate file
doc/index.txt | 161 +--------------------------------------------------------
doc/maven.txt | 159 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 160 insertions(+), 160 deletions(-)
---
diff --git a/doc/index.txt b/doc/index.txt
index 439c73b..12a44bb 100644
--- a/doc/index.txt
+++ b/doc/index.txt
@@ -238,166 +238,7 @@ Will probably include some information about <<Xdepmap,depmap>> files.
=== Apache Maven ===
-[quote,,http://maven.apache.org]
-______
-Apache Maven is a software project management and comprehension tool. Based on
-the concept of a project object model (POM), Maven can manage a project's build,
-reporting and documentation from a central piece of information.
-______
-
-Maven is by far the most consistent Java build system, allowing large amount of
-automation. In most common situations only following steps are necessary:
-
-1. In `%build` section of the spec file use `%mvn_build` macro
-2. In `%install` section, use `%mvn_install` macro
-3. Use generated file `.mfiles` lists to populate `%files` section with `-f` switch
-
-.Common spec file sections
-[source,spec]
---------
-BuildRequires: maven-local
-...
-%build
-%mvn_build
-...
-
-%install
-%mvn_install
-...
-
-
-%files -f .mfiles
-%dir %{_javadir}/%{name}
-
-%files javadoc -f .mfiles-javadoc
--------
-
-
-The macros `%mvn_build` and `%mvn_install` automatically handle building of the
-JAR files and their subsequent installation to the correct directory. The
-corresponding POM and <<Xdepmap,depmap>> files are also installed.
-
-==== Additional mappings ====
-[[pom_jar_mapping]]
-
-The macro `%mvn_alias` can be used to add additional mappings for given POM/JAR
-file. For example, if the POM file indicates that it contains groupId
-commons-lang, artifactId commons-lang, this macro ensures that we also add a
-mapping between groupId org.apache.commons and the installed JAR/POM files. This
-is necessary in cases where the groupId or artifactId may have changed, and
-other packages might require different IDs than those reflected in the installed
-POM.
-
-.Adding more mappings for JAR/POM files example
-[source,spec]
--------
-%prep
-...
-%mvn_alias "commons-lang:commons-lang" "org.apache.commons:commons-lang"
--------
-
-==== Alternative JAR file names ====
-In some cases, it may be important to be able to provide symlinks to actual JAR
-files. This can be achieved with `%mvn_file` macro. This macro allows packager
-to specify names of the JAR files, their location in `%{_javadir}` directory and
-also can create symlinks to the JAR files. These symlinks can be possibly
-located outside of the `%{_javadir}` directory.
-
-.Adding file symlinks to compatibility
-[source,spec]
--------
-%prep
-...
-%mvn_file :guice google/guice guice
--------
-
-This means that JAR file for artifact with ID "guice" (and any groupId) will be
-installed in `%{_javadir}/google/guice.jar` and there also will be a symlink to
-this JAR file located in `%{_javadir}/guice.jar`. Note the macro will add ".jar"
-extensions automatically.
-
-==== Single artifact per package ====
-If the project consists of multiple artifacts, it is recommended to install each
-artifact to the separate subpackage. The macro `%mvn_build -s` will generate
-separate `.mfiles` file for every artifact in the project. This file contains
-list of files related to specific artifact (typically JAR file, POM file and
-depmap). It can be later used in `%files` section of the spec file.
-
-.Creating one subpackage for each generated artifact
-[source,spec]
--------
-...
-%description
-The Maven Plugin Tools contains...
-
-%package -n maven-plugin-annotations
-Summary: Maven Plugin Java 5 Annotations
-
-%description -n maven-plugin-annotations
-This package contains Java 5 annotations to use in Mojos.
-
-%package -n maven-plugin-plugin
-Summary: Maven Plugin Plugin
-
-%description -n maven-plugin-plugin
-The Plugin Plugin is used to...
-...
-
-%build
-%mvn_build -s
-
-%install
-%mvn_install
-
-%files -f .mfiles-maven-plugin-tools
-%doc LICENSE NOTICE
-%files -n maven-plugin-annotations -f .mfiles-maven-plugin-annotations
-%files -n maven-plugin-plugin -f .mfiles-maven-plugin-plugin
-%files -f .mfiles-javadoc
-...
--------
-
-==== Assignment of the Maven artifacts to the subpackages ====
-The macro `%mvn_package` allows maintainer to specify in which exact package the
-selected artifact will end up. It is something between singleton packaging, when
-each artifact has its own subpackage and default packaging, when all artifacts
-end up in the same package.
-
-.Assigning multiple artifacts to single subpackage
-[source,spec]
--------
-...
-%prep
-%mvn_package ":plexus-compiler-jikes" plexus-compiler-extras
-%mvn_package ":plexus-compiler-eclipse" plexus-compiler-extras
-%mvn_package ":plexus-compiler-csharp" plexus-compiler-extras
-
-%build
-%mvn_build
-
-%install
-%mvn_install
-
-%files -f .mfiles
-%files -f .mfiles-plexus-compiler-extras
-%files -f .mfiles-javadoc
--------
-
-In above example, the artifacts `plexus-compiler-jikes`,
-`plexus-compiler-eclipse`, `plexus-compiler-csharp` will end up in package named
-`plexus-compiler-extras`. If there are some other artifacts beside these three
-mentioned (e.g. some parent POMs), then these will all end up in package named
-`%{name}`.
-
-[TIP]
-======
-`%mvn_package` macro supports wildcards and brace expansions, so whole `%prep` section from previous example can be replaced with single line:
-`%mvn_package ":plexus-compiler-{jikes,eclipse,csharp}" plexus-compiler-extras`
-======
-
-.XMvn package relationships
-image:images/xmvn.svg["XMvn related packages",width=600]
-
+include::maven.txt[]
=== Ant
diff --git a/doc/maven.txt b/doc/maven.txt
new file mode 100644
index 0000000..b5fd43a
--- /dev/null
+++ b/doc/maven.txt
@@ -0,0 +1,159 @@
+[quote,,http://maven.apache.org]
+______
+Apache Maven is a software project management and comprehension tool. Based on
+the concept of a project object model (POM), Maven can manage a project's build,
+reporting and documentation from a central piece of information.
+______
+
+Maven is by far the most consistent Java build system, allowing large amount of
+automation. In most common situations only following steps are necessary:
+
+1. In `%build` section of the spec file use `%mvn_build` macro
+2. In `%install` section, use `%mvn_install` macro
+3. Use generated file `.mfiles` lists to populate `%files` section with `-f` switch
+
+.Common spec file sections
+[source,spec]
+--------
+BuildRequires: maven-local
+...
+%build
+%mvn_build
+...
+
+%install
+%mvn_install
+...
+
+
+%files -f .mfiles
+%dir %{_javadir}/%{name}
+
+%files javadoc -f .mfiles-javadoc
+-------
+
+
+The macros `%mvn_build` and `%mvn_install` automatically handle building of the
+JAR files and their subsequent installation to the correct directory. The
+corresponding POM and <<Xdepmap,depmap>> files are also installed.
+
+==== Additional mappings ====
+[[pom_jar_mapping]]
+
+The macro `%mvn_alias` can be used to add additional mappings for given POM/JAR
+file. For example, if the POM file indicates that it contains groupId
+commons-lang, artifactId commons-lang, this macro ensures that we also add a
+mapping between groupId org.apache.commons and the installed JAR/POM files. This
+is necessary in cases where the groupId or artifactId may have changed, and
+other packages might require different IDs than those reflected in the installed
+POM.
+
+.Adding more mappings for JAR/POM files example
+[source,spec]
+-------
+%prep
+...
+%mvn_alias "commons-lang:commons-lang" "org.apache.commons:commons-lang"
+-------
+
+==== Alternative JAR file names ====
+In some cases, it may be important to be able to provide symlinks to actual JAR
+files. This can be achieved with `%mvn_file` macro. This macro allows packager
+to specify names of the JAR files, their location in `%{_javadir}` directory and
+also can create symlinks to the JAR files. These symlinks can be possibly
+located outside of the `%{_javadir}` directory.
+
+.Adding file symlinks to compatibility
+[source,spec]
+-------
+%prep
+...
+%mvn_file :guice google/guice guice
+-------
+
+This means that JAR file for artifact with ID "guice" (and any groupId) will be
+installed in `%{_javadir}/google/guice.jar` and there also will be a symlink to
+this JAR file located in `%{_javadir}/guice.jar`. Note the macro will add ".jar"
+extensions automatically.
+
+==== Single artifact per package ====
+If the project consists of multiple artifacts, it is recommended to install each
+artifact to the separate subpackage. The macro `%mvn_build -s` will generate
+separate `.mfiles` file for every artifact in the project. This file contains
+list of files related to specific artifact (typically JAR file, POM file and
+depmap). It can be later used in `%files` section of the spec file.
+
+.Creating one subpackage for each generated artifact
+[source,spec]
+-------
+...
+%description
+The Maven Plugin Tools contains...
+
+%package -n maven-plugin-annotations
+Summary: Maven Plugin Java 5 Annotations
+
+%description -n maven-plugin-annotations
+This package contains Java 5 annotations to use in Mojos.
+
+%package -n maven-plugin-plugin
+Summary: Maven Plugin Plugin
+
+%description -n maven-plugin-plugin
+The Plugin Plugin is used to...
+...
+
+%build
+%mvn_build -s
+
+%install
+%mvn_install
+
+%files -f .mfiles-maven-plugin-tools
+%doc LICENSE NOTICE
+%files -n maven-plugin-annotations -f .mfiles-maven-plugin-annotations
+%files -n maven-plugin-plugin -f .mfiles-maven-plugin-plugin
+%files -f .mfiles-javadoc
+...
+-------
+
+==== Assignment of the Maven artifacts to the subpackages ====
+The macro `%mvn_package` allows maintainer to specify in which exact package the
+selected artifact will end up. It is something between singleton packaging, when
+each artifact has its own subpackage and default packaging, when all artifacts
+end up in the same package.
+
+.Assigning multiple artifacts to single subpackage
+[source,spec]
+-------
+...
+%prep
+%mvn_package ":plexus-compiler-jikes" plexus-compiler-extras
+%mvn_package ":plexus-compiler-eclipse" plexus-compiler-extras
+%mvn_package ":plexus-compiler-csharp" plexus-compiler-extras
+
+%build
+%mvn_build
+
+%install
+%mvn_install
+
+%files -f .mfiles
+%files -f .mfiles-plexus-compiler-extras
+%files -f .mfiles-javadoc
+-------
+
+In above example, the artifacts `plexus-compiler-jikes`,
+`plexus-compiler-eclipse`, `plexus-compiler-csharp` will end up in package named
+`plexus-compiler-extras`. If there are some other artifacts beside these three
+mentioned (e.g. some parent POMs), then these will all end up in package named
+`%{name}`.
+
+[TIP]
+======
+`%mvn_package` macro supports wildcards and brace expansions, so whole `%prep` section from previous example can be replaced with single line:
+`%mvn_package ":plexus-compiler-{jikes,eclipse,csharp}" plexus-compiler-extras`
+======
+
+.XMvn package relationships
+image:images/xmvn.svg["XMvn related packages",width=600]
11 years, 3 months
[jetty] Add missing BR: glassfish-el
by Mikolaj Izdebski
commit 43b5730bb6fdcd15de8a460c7b500f1297eaedba
Author: Mikolaj Izdebski <mizdebsk(a)redhat.com>
Date: Thu Mar 7 17:26:16 2013 +0100
Add missing BR: glassfish-el
jetty.spec | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
---
diff --git a/jetty.spec b/jetty.spec
index 7b244ff..dd45f27 100644
--- a/jetty.spec
+++ b/jetty.spec
@@ -52,7 +52,7 @@
Name: jetty
Version: 9.0.0
-Release: 0.3.%{addver}%{?dist}
+Release: 0.4.%{addver}%{?dist}
Summary: Java Webserver and Servlet Container
Group: Applications/Internet
@@ -71,6 +71,8 @@ BuildRequires: geronimo-annotation
BuildRequires: geronimo-jaspic-spec
BuildRequires: geronimo-jta
BuildRequires: geronimo-parent-poms
+BuildRequires: glassfish-el
+BuildRequires: glassfish-el-api
BuildRequires: glassfish-jsp
BuildRequires: glassfish-jsp-api
BuildRequires: jakarta-taglibs-standard
@@ -765,6 +767,9 @@ getent passwd %username &>/dev/null || useradd -r -u %jtuid -g %username \
%doc NOTICE.txt LICENSE*
%changelog
+* Thu Mar 7 2013 Mikolaj Izdebski <mizdebsk(a)redhat.com> - 9.0.0-0.4.RC3
+- Add missing BR: glassfish-el
+
* Mon Mar 4 2013 Mikolaj Izdebski <mizdebsk(a)redhat.com> - 9.0.0-0.3.RC3
- Update to Jetty 9 RC3
11 years, 3 months
Broken dependencies: jetty
by Fedora Koji Build System
jetty has broken dependencies in the rawhide tree:
On x86_64:
jetty-jsp-9.0.0-0.2.RC2.fc19.noarch requires mvn(org.eclipse.jetty.orbit:org.apache.taglibs.standard.glassfish)
jetty-jsp-9.0.0-0.2.RC2.fc19.noarch requires mvn(org.eclipse.jetty.orbit:javax.servlet.jsp.jstl)
On i386:
jetty-jsp-9.0.0-0.2.RC2.fc19.noarch requires mvn(org.eclipse.jetty.orbit:org.apache.taglibs.standard.glassfish)
jetty-jsp-9.0.0-0.2.RC2.fc19.noarch requires mvn(org.eclipse.jetty.orbit:javax.servlet.jsp.jstl)
Please resolve this as soon as possible.
11 years, 3 months