Source strings

57 Strings
100%
Browse Translate
1,497 Words
100%
10,759 Characters
100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
57 1,497 10,759
All strings Browse Translate Zen
57 1,497 10,759
Read-only strings Browse Translate Zen
9 106 1,083
Strings with any failing checks Browse Translate Zen
9 106 1,083
Failing check: Ellipsis Browse Translate Zen

Summary

Project website forge.fedoraproject.org
Instructions for translators

Mailing list for translators: trans@lists.fedoraproject.org
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://forge.fedoraproject.org/localization-docs/java-packaging-howto.git
Repository branch master
Last commit in Weblate Added translation using Weblate (Portuguese (Brazil)) 86a7b76d
User avatar rffontenelle authored 04/09/2026
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-java-packaging-howto/masterantorayml/
File mask po/*/master/pages/mvn_macros.po
Translation file Download pot/master/pages/mvn_macros.pot
Last change April 9, 2026, 12:24 a.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,473,503
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
04/09/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 57 1,497 10,759
Translated 100% 57 100% 1,497 100% 10,759
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 57 100% 1,497 100% 10,759
Failing checks 15% 9 7% 106 10% 1,083
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
AprMayJunJulAugSepOctNovDecJanFebMar

Quick numbers

1,497
Hosted words
57
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

+100%
Hosted words
—
+100%
Hosted strings
—
+100%
Translated
—
—
Contributors
—
User avatar None

Source string added
All `%mvn_` macros have their own manual page which contains details on how to use them. All possible options should be documented there. These manual pages should be considered most up to date documentation right after source code. Try for example `man mvn_file`. These pages are also included in the xref:manpages.adoc#manpages[Appendix].
04/09/2026
User avatar None

Source string added
Read about XMvn's configuration http://mizdebsk.fedorapeople.org/xmvn/site/configuration.html[basics] and see full http://mizdebsk.fedorapeople.org/xmvn/site/config.html[configuration reference].
04/09/2026
User avatar None

Source string added
XMvn's configuration is quite complex, but well documented at project's http://mizdebsk.fedorapeople.org/xmvn/site/[official website]. The website should always be used as a primary source of information about XMvn configuration.
04/09/2026
User avatar None

Source string added
Some packages might need to modify XMvn's configuration in order to build successfully or from other reasons. This can be achieved with `mvn_config` macro. For example, some old package can use `enum` as an identifier, but it is also keyword since Java 1.5. Such package will probably fail to build on current systems. This problem can be easily solved by passing `-source 1.4` to the compiler, so one could add following line to the spec file:
04/09/2026
User avatar None

Source string added
It is possible to assign artifacts into a package called `__noinstall`. This package name has a special meaning. And as you can guess, artifacts assigned into this package won't be installed anywhere and the package itself won't be created.
04/09/2026
User avatar None

Source string added
`%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`
04/09/2026
User avatar None

Source string added
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}`.
04/09/2026
User avatar None

Source string added
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.
04/09/2026
User avatar None

Source string added
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 metadata). It can be later used in `%files` section of the spec file.
04/09/2026
User avatar None

Source string added
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 symbolic links to this JAR file located in `%{_javadir}/guice.jar`. Note the macro will add ".jar" extensions automatically.
04/09/2026
Browse all translation changes