Zen

Translation

English type: Block title
Maven
5/100 · 5

Sign in to save the translation.

English Spanish Actions
Resource files such as images or localisation data
 
Optionaly the source code of our project (called source JAR then)
 
They can also contain additional bundled software which is something we don't want to have in packages. You can inspect the contents of given JAR file by extracting it. That can be done with following command:
 
jar xf something.jar
 
The detailed description of JAR file format is in the link:http://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html[JAR File Specification].
 
Classpath
 
The classpath is a way of telling JVM where to look for user classes and 3rd party libraries. By default, only current directory is searched, all other locations need to be specified explicitly by setting up CLASSPATH environment variable, or via `-cp` (`-classpath`) option of a Java Virtual Machine.
 
Setting the classpath
 
java -cp /usr/share/java/log4j.jar:/usr/share/java/junit.jar mypackage/MyClass.class
CLASSPATH=/usr/share/java/log4j.jar:/usr/share/java/junit.jar java mypackage/MyClass.class
 
Please note that two JAR files are separated by colon in a classpath definition.
 
See http://docs.oracle.com/javase/8/docs/technotes/tools/windows/classpath.html[official documentation] for more information about classpath.
 
Wrapper scripts
 
Classic compiled applications use dynamic 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. Note that this is not necessary for libraries.
 
Build System Identification
 
Build system used by upstream can be usually identified by looking at their configuration files, which reside in project directory structure, usually in its root or in specialized directories with names such as `build` or `make`.
 
Maven
Maven
Build managed by Apache Maven is configured by an XML file that is by default named `pom.xml`. In its simpler form it usually looks like this:
 
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.example.myproject</groupId>
<artifactId>myproject</artifactId>
<packaging>jar</packaging>
<version>1.0</version>
<name>myproject</name>
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.1</version>
<scope>test</scope>
</dependency>
</dependencies>
</project>
 
It describes project's build process in a declarative way, without explicitly specifying exact steps needed to compile sources and assemble pieces together. It also specifies project's dependencies which are usually the main point of interest for packagers. Other important feature of Maven that packagers should know about are plugins. Plugins extend Maven with some particular functionality, but unfortunately some of them may get in the way of packaging and need to be altered or removed. There are RPM macros provided to facilitate modifying Maven dependencies and plugins.
 
Ant
Ant
Apache Ant is also configured by an XML file. It is by convention named `build.xml` and in its simple form it looks like this:
 
<project name="MyProject" default="dist" basedir=".">
<property name="src" location="src"/>
<property name="build" location="build"/>
<property name="dist" location="dist"/>
 
<target name="init" description="Create build directory">
<mkdir dir="${build}"/>
</target>
 
<target name="compile" depends="init"
description="Compile the source">
<javac srcdir="${src}" destdir="${build}"/>
</target>
 
<target name="dist" depends="compile"
description="Generate jar">
<mkdir dir="${dist}/lib"/>
 
<jar jarfile="${dist}/myproject.jar" basedir="${build}"/>
</target>
 
<target name="clean" description="Clean build files">
<delete dir="${build}"/>
<delete dir="${dist}"/>
</target>
</project>
 
Ant build file consists mostly of targets, which are collections of steps needed to accomplish intended task. They usually depend on each other and are generally similar to Makefile targets. Available targets can be listed by invoking `ant -p` in project directory containing `build.xml` file. If the file is named differently than `build.xml` you have to tell Ant which file should be used by using `-f` option with the name of the actual build file.
 
Some projects that use Apache Ant also use Apache Ivy to simplify dependency handling. Ivy is capable of resolving and downloading artifacts from Maven repositories which are declaratively described in XML. Project usually contains one or more `ivy.xml` files specifying the module Maven coordinates and its dependencies. Ivy can also be used directly from Ant build files. To detect whether the project you wish to package is using Apache Ivy, look for files named `ivy.xml` or nodes in the `ivy` namespace in project's build file.
 
Make
 
While unlikely, it's still possible that you encounter a project whose build is managed by plain old Makefiles. They contain a list of targets which consist of commands (marked with tab at the begining of line) and are invoked by `make` _target_ or simply `make` to run the default target.
 

Loading…

User avatar vareli

Translation added
Maven
Maven
7 months ago
User avatar None

String updated in the repository
Maven
 
a year ago
Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English Spanish
No related strings found in the glossary.

15429979 String information

Source string description
type: Block title
Flags
no-wrap
Source string location
./pages/introduction_for_packagers.adoc:175
String age
a year ago
Last updated
7 months ago
Source string age
4 years ago
Translation file
po/es/master/pages/introduction_for_packagers.po, string 51