Hello Mathieu,
It looks like a bug in maven-debian-helper, can you file a bug and I
will look at it next month, as I'm on holidays now.
Thanks,
Ludovic
Le 13/09/2012 11:19, Mathieu Malaterre a écrit :
Hi all,
I am trying to package Perf4j using mh_make. It seems to work quite
well. Steps:
$ wget https://github.com/perf4j/perf4j/tarball/perf4j-0.9.16
$ tar xvfz [...]
$ mh_make
Environment variable DEBLICENSE not set, using GPL-3+ by default
Enter the name of the new Debian source package. If empty, it will
defaults to perf4j
Enter the name of the binary package. If empty, it will defaults to
libperf4j-java
Run tests while building the package?
[y]/n > y
Generate the Javadoc while building the package?
[y]/n > y
Checking that apt-file is installed and has been configured...
[ok]
Checking that licensecheck is installed...
[ok]
Solving dependencies for package libperf4j-java (tests are included)
(documentation is included)
Analysing pom.xml...
Enter the upstream version for the package. If you press <Enter> it
will default to 0.9.16
Version of org.perf4j:perf4j is 0.9.16
Choose how it will be transformed:
[1] - Replace all versions starting by 0. with 0.x
2 - Change the version to the symbolic 'debian' version
3 - Keep the version
4 - Custom rule
Resolving log4j:log4j:jar:1.2.14 of scope compile...
Sep 13, 2012 9:16:29 AM
org.debian.maven.packager.DependenciesSolver$ToResolve resolve
SEVERE: Cannot resolve dependencies in ./pom.xml: Dangling meta
character '+' near index 0
+)\.(.*)/\$1\.\$2\.x/
^
java.util.regex.PatternSyntaxException: Dangling meta character '+' near index 0
+)\.(.*)/\$1\.\$2\.x/
^
at java.util.regex.Pattern.error(Pattern.java:1730)
at java.util.regex.Pattern.sequence(Pattern.java:1895)
at java.util.regex.Pattern.expr(Pattern.java:1769)
at java.util.regex.Pattern.compile(Pattern.java:1477)
at java.util.regex.Pattern.<init>(Pattern.java:1150)
at java.util.regex.Pattern.compile(Pattern.java:840)
at org.debian.maven.repo.Rule.<init>(Rule.java:44)
at org.debian.maven.repo.DependencyRule.<init>(DependencyRule.java:41)
at org.debian.maven.repo.POMInfo.getPublishedRules(POMInfo.java:275)
at
org.debian.maven.repo.Repository.searchMatchingPOM(Repository.java:130)
at
org.debian.maven.packager.DependenciesSolver.resolveDependency(DependenciesSolver.java:987)
at
org.debian.maven.packager.DependenciesSolver.resolveDependency(DependenciesSolver.java:883)
at
org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:878)
at
org.debian.maven.packager.DependenciesSolver.access$000(DependenciesSolver.java:56)
at
org.debian.maven.packager.DependenciesSolver$ToResolve.resolve(DependenciesSolver.java:353)
at
org.debian.maven.packager.DependenciesSolver.resolveDependenciesNow(DependenciesSolver.java:864)
at
org.debian.maven.packager.DependenciesSolver.solveDependencies(DependenciesSolver.java:598)
at
org.debian.maven.packager.DependenciesSolver.main(DependenciesSolver.java:1420)
Resolving org.apache.maven.plugins:maven-compiler-plugin:maven-plugin:2.0.2
of scope runtime...
Dependency org.apache.maven.plugins:maven-compiler-plugin:maven-plugin:2.0.2
found in package libmaven-compiler-plugin-java
[ok]
Resolving org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.2.1
of scope runtime...
In pom.xml:
This plugin is not useful for the build or its use is against Debian
policies. Ignore this plugin?
org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.2.1
Should I ignore the error message (with stacktrace) or not ?
Thanks much.
--
To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5058dc7c.6070...@laposte.net
