Hello,
Better late than never. Here comes quick summary of most important changes in latest javapackages-tools release:
- changes in %pom_* macros (contributed by Michael Simacek, thanks!): - new macro %pom_change_dep for changing dependencies in Maven POM files or Ivy modules - see man pom_change_dep for more details - macros %pom_change_dep, %pom_remove_dep, %pom_remove_plugin, %pom_xpath_remove and %pom_xpath_replace now support recursive mode - see corresponding man pages for more details - Requires generator now generates auto-requires instead of XMvn when (sub)packages contain only POM artifacts - this change shouldn't be visible to end users - new subpackage javapackages-local - %mvn_* macros (except %mvn_build) were moved to this subpackage - no changes to existing spec files shouldn't be needed. This subpackage is useful when you don't build your package with xmvn, but you still want to use the rest of the %mvn_ macros (e.g. %mvn_install).
Latest javapackages-tools release internally works with new metadata and no longer produce old fragments/depmaps. This can cause "error: File not found: ... /usr/share/maven-fragments/%{name}" build failure. For more information on this topic see my "how to fix..." email [1].
Michal
[1]: https://lists.fedoraproject.org/pipermail/java-devel/2014-June/005269.html
On 06/12/2014 10:07 AM, Michal Srb wrote:
- changes in %pom_* macros (contributed by Michael Simacek, thanks!):
- new macro %pom_change_dep for changing dependencies in Maven POM
files or Ivy modules - see man pom_change_dep for more details
I can't see manpage for this macro:
$ man pom_change_dep No manual entry for pom_change_dep
Unlike all other macros it's not documented in /usr/lib/rpm/macros.d/macros.fjava either.
- macros %pom_change_dep, %pom_remove_dep, %pom_remove_plugin,
%pom_xpath_remove and %pom_xpath_replace now support recursive mode - see corresponding man pages for more details
Even as one of developers of javapackages I didn't know about this. That's why release notes are very important IMO.
- Requires generator now generates auto-requires instead of XMvn when
(sub)packages contain only POM artifacts - this change shouldn't be visible to end users
There is another change related to auto-provides and requires. Requires for POM artifacts are now in the usual format like any other artifacts.
java-devel@lists.fedoraproject.org