File: control

package info (click to toggle)
uber-pom 1.0.3-2
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, bullseye, forky, sid, trixie
  • size: 204 kB
  • sloc: java: 1,247; xml: 552; makefile: 2
file content (28 lines) | stat: -rw-r--r-- 1,073 bytes parent folder | download
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
Source: uber-pom
Section: java
Priority: optional
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Uploaders: Roger Shimizu <rosh@debian.org>
Build-Depends:
 debhelper-compat (= 12),
 default-jdk-headless,
 maven-debian-helper
Build-Depends-Indep:
 libcommons-io-java,
 libmaven-plugin-tools-java
Standards-Version: 4.5.1
Rules-Requires-Root: no
Vcs-Git: https://salsa.debian.org/java-team/uber-pom.git
Vcs-Browser: https://salsa.debian.org/java-team/uber-pom
Homepage: https://github.com/raydac/uber-pom

Package: libuber-pom-java
Architecture: all
Depends: ${misc:Depends}, ${maven:Depends}
Suggests: ${maven:OptionalDepends}
Description: UberPom - merging maven pom hierarchy parameters
 The Plugin just merging all pom.xml in project module hierarchy (or
 only defined depth of the hierarchy) and saves the generated uber-pom
 into defined place, then it saves link to the file into the current
 maven project model. It works on the VALIDATE phase. So the result
 packed artifact will have the uber-pom packed into the result archive.