Upstreams are planning to release XMvn 2.0.0 and Javapackages 4.0.0 on 29 May. I am going to push them to rawhide as soon as they are released.
Some of more important changes which could affect some Java packages:
The notion of "depmap" is removed. %_mavendepmapdir and %_mavendepmapfragdir macros are deprecated and scheduled for removal in future. %add_maven_depmap is considered as obsolete and despite its name it doesn't create depmaps any longer, but a new kind of metadata. %mvn_build no longer creates depmaps either, but it will continue to use them for artifact resolution during transition period (for at least one Fedora release; after that depmap support may be removed completely).
Full release notes will be available at release time.
On 05/22/2014 08:24 AM, Mikolaj Izdebski wrote:
Upstreams are planning to release XMvn 2.0.0 and Javapackages 4.0.0 on 29 May. I am going to push them to rawhide as soon as they are released.
I forgot to add that experimental xmvn and javapackages-tools packages are (as always) available in YUM repos at [1,2]. Additionally I've creaded a Copr [3] containing latest packages where interested parties may built anything they want to test. I will grant write permissions to this Copr per request.
[1] http://jenkins.cloud.fedoraproject.org/job/javapackages-tools/ws/RPM/latest [2] http://jenkins.cloud.fedoraproject.org/job/xmvn/ws/RPM/latest [3] http://copr.fedoraproject.org/coprs/mizdebsk/xmvn20/
On 05/22/2014 08:24 AM, Mikolaj Izdebski wrote:
Upstreams are planning to release XMvn 2.0.0 and Javapackages 4.0.0 on 29 May. I am going to push them to rawhide as soon as they are released.
XMvn 2.0.0 and Javapackages 4.0.0 were pushed to rawhide a few hours ago.
I would like to remind you that %add_maven_depmap macro doesn't create depmaps any longer [*], but a new kind of metadata. Packages that still use the the old %_mavendepmapfragdir may fail to build now and need to be updated to follow current packaging guidelines.
[*] In Javapackages 3.x %add_maven_depmap used to create and install "depmap fragment" file in /usr/share/maven-fragments (aka %_mavendepmapfragdir). In Javapackages 4.x depmaps are not created at all (because XMvn 2.x doesn't need them to work) and instead %add_maven_depmap installs Maven metadata files in /usr/share/maven-metadata. There is no RPM macro for the new metadata directory as packages shouldn't be using it directly, but rely on .mfiles.
java-devel@lists.fedoraproject.org