maven-repo-helper_1.2~bpo50+1_i386.changes is NEW
(new) maven-repo-helper_1.2~bpo50+1.dsc optional java
(new) maven-repo-helper_1.2~bpo50+1.tar.gz optional java
(new) maven-repo-helper_1.2~bpo50+1_all.deb optional java
Helper tools for including Maven metatada in Debian packages
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's primary goal is to allow a developer to comprehend the complete
state of a development effort in the shortest period of time. In order to
attain this goal there are several areas of concern that Maven attempts
to deal with:
.
* Making the build process easy
* Providing a uniform build system
* Providing quality project information
* Providing guidelines for best practices development
* Allowing transparent migration to new features
.
This package enables Debian packages which are not using Maven in their
build process to provide and install Maven POMs and libraries in the
repository located in /usr/share/maven-repo.
.
Packages built with Maven (using maven-debian-helper) will benefit as
many of their dependencies are already packaged in Debian but they are
missing the necessary metadata (Maven POM) which is required by Maven
when it is using dependencies.
Changes: maven-repo-helper (1.2~bpo50+1) lenny-backports; urgency=low
.
* Rebuild for lenny-backports.
* Requires libstax-java backport.
.
maven-repo-helper (1.2) unstable; urgency=low
.
* Fix 'illegal NCName' error when gcj is used to run the mh_* scripts
* Expand more Maven properties in POM files.
* Support <property/> syntax in <properties> tag
* Handle better configuration elements in plugins (ignore them)
* Add support for plugin elements in <profile> tags
* Add support for dependency classifiers
* Add support for <reporting> tags and their plugins
* Fix some XML issues when gcj is used
* Add new unit tests and fix several small issues
* Insert the original versions of the dependencies in the cleaned poms,
this will help a future mh_upgrade tool
.
maven-repo-helper (1.1) unstable; urgency=low
.
* Add mh_patchpom, useful in some situations to patch
individual POM files
* Add mh_linkrepojar, to create a link from a jar present in the
Maven repository
* Correctly identify <extension> tag used by Maven (Closes: #584512)
* Add documentation for the package and in particular for the syntax
of the debian/<package>.poms file (Closes: #586151)
* All mh_* scripts now use debian/.mh/ as their temporary work folder
instead of debian/tmp, this better satisfies the Debian policies.
* Add mh_cleantmp to remove the temporary files produced when using
any other mh_* script
* Fix typo in package description (Closes: #586573)
.
maven-repo-helper (1.0.6) unstable; urgency=low
.
* Rule.java: harden our handling of version string (from pom.xml)
to cope with specials chars.
* POMTransformer: If we can't find a dependency, just skip it.
* Switch to 3.0 (native) format
.
maven-repo-helper (1.0.5) unstable; urgency=low
.
* mh_installjar: Add new -e/--set-version switchs and handle
them as we already do in mh_installpom.
.
maven-repo-helper (1.0.4) unstable; urgency=low
.
* Fix "ignores the --no-parent option in the .poms file" (Closes: #573049)
- mh_installpom: Pass "--no-parent" option to mh_cleanpom.
.
maven-repo-helper (1.0.3) unstable; urgency=low
.
* mh_installpoms: Fix call to mh_installpom.
Use MH_ARGS instead of (non-existing) MH_OPTS variable.
.
maven-repo-helper (1.0.2) unstable; urgency=low
.
* A leak of environment variables activated the no-rules option
on mh_cleanpom, preventing mh_installjar to work properly
in some cases (Closes: #570863)
.
maven-repo-helper (1.0.1) unstable; urgency=low
.
* Bump up Standards-Version to 3.8.4
* Fix NPE on mh_transformpoms
* Looks like I missed many files while merging changes
to Debian, it's now fixed.
.
maven-repo-helper (1.0) unstable; urgency=low
.
* Add more unit tests
* maven.ignoreRules now supports eliminating some plugins from the build
* maven.rules can be used to repair missing version numbers for
plugins and extensions as well as dependencies (Closes: #561420)
* If a pom file is followed by the --ignore option in the file
<package>.poms, then it is ignored from the build and all operations
(cleaning, patching)
* Add support for maven.cleanIgnoreRules to ignore additional dependencies or
plugins during the clean phase.
* mh_cleanpom automatically adds a published rule for any Maven plugin, this
rule is used later by maven-debian-helper to force the versions of the
Maven plugins used in a pom.xml file with the versions defined in the
repository
* Read rules from the Maven repository to force the version of
Maven plugins to be the same as in the repository
* Add --debian-build and --no-docs-build options to mh_patchpoms to remove
some elements from the POM during a Debian build
.
maven-repo-helper (0.9) unstable; urgency=low
.
* org/debian/maven/repo/POMReader.java:
Extend previous fix to parse much more properties
and use expandProperties() like other cases.
.
maven-repo-helper (0.8) unstable; urgency=low
.
* org/debian/maven/repo/POMReader.java:
Fix ${parent.version} parsing inside child's pom.xml
* Bump Standards-Version to 3.8.3 (no changes needed)
* Fix Vcs-* fields: use pkg-java SVN repository
.
maven-repo-helper (0.7) unstable; urgency=low
.
* Install jars in /usr/share/java and create link to them from
the Maven repository (as suggested by Marcus Better)
* Add a new script, mh_linkjar, which creates links to the jar into
/usr/share/maven-repo. Unlike mh_installjar, it does not copy the
jar into the build directory.
* Use install instead of dh_install in the scripts as it can
interfer if there is a .install file in the debian folder.
* Add Recommends: debhelper as debhelper is used in some scripts
(mh_install* and mh_linkjar)
* Add --set-version to mh_cleanpom, mh_installpom, mh_installpoms
to be able to force the version of the artifact in Maven without
needing patching the original POM file.
* More errors detected in repo scan
* Use http://maven.apache.org/xsd/maven-4_0_0.xsd as the location of
the xsd in the xml namespace declaration to keep gcj happy. It should
not affect Maven or other tools, provided that the xsd is registered
in a XML catalog.
* By default, remove the test dependencies from cleaned POMs (except for
multi-module POM) as they are not useful outside building the project
itself most of the time and they make checking consistency in the
Maven repository harder.
* mh_cleanpom, mh_installpom(s) and mh_transformpoms can remove
dependencies from the POM files
.
maven-repo-helper (0.6.1) experimental; urgency=low
.
* Add a workaround to use gcj with maven-repo-helper:
avoid using gnu xml stream when reading or writing XML documents.
.
maven-repo-helper (0.6) experimental; urgency=low
.
* Move mh_genrules scripts to the maven-debian-helper package,
as it needs mh_lspoms and other components from this package.
* Repair missing version information on dependencies
Override entries for your package:
Announcing to debian-backports-changes@lists.debian.org
Your package contains new components which requires manual editing of
the override file. It is ok otherwise, so please be patient. New
packages are usually added to the override file about once a week.
You may have gotten the distribution wrong. You'll get warnings above
if files already exist in other distributions.
eady exist in other distributions.
Reply to: