javapackages-tools 3.1.0 released - support for artifacts in build-classpath family

[Stanislav Ochotnicky]

As the subject mentions the main feature in new javapackages-tools is
improvement of build-classpath, build-jar-repository and related functions to
support Maven artifacts in form of:

groupId:artifactId[:extension[:classifier]][:version]

You can also mix and match so this is valid:

build-classpath junit:junit commons-lang

For Maven artifacts the dependencies are added transitively. This obviously
requires XMvn, but it's a soft requirement. As long as you don't use Maven
artifacts in the scripts that is...

Other things:
  * Support for SCLs in macros, scrips etc which needed serious rework so bugs
    may be present bug backward compatibility should be preserved
  * Man pages for RPM macros (also in previous release, just forgot to mention it)
  * 230 tests for pom_ macros, provides/requires generators, backend library,
    mvn_* scripts. More to come

rawhide build: http://koji.fedoraproject.org/koji/taskinfo?taskID=5954475

[Mikolaj Izdebski]

On 09/19/2013 12:06 PM, Stanislav Ochotnicky wrote:
> For Maven artifacts the dependencies are added transitively.

They are not.  Only the artifact that was requested is added, it's
dependencies are not.  This is consistent with previous behavior of
build-classpath.

[Severin Gehwolf]

Hi!

Great news, thanks!

On Thu, 2013-09-19 at 12:06 +0200, Stanislav Ochotnicky wrote:
> As the subject mentions the main feature in new javapackages-tools is
> improvement of build-classpath, build-jar-repository and related functions to
> support Maven artifacts in form of:
> groupId:artifactId[:extension[:classifier]][:version]
>
> You can also mix and match so this is valid:
> build-classpath junit:junit commons-lang
>
> For Maven artifacts the dependencies are added transitively. This obviously
> requires XMvn, but it's a soft requirement. As long as you don't use Maven
> artifacts in the scripts that is...
>
> Other things:
> Support for SCLs in macros, scrips etc which needed serious rework so bugs
> may be present bug backward compatibility should be preserved
> Man pages for RPM macros (also in previous release, just forgot to mention it)

Can I ask you to add this to:
https://fedoraproject.org/wiki/Packaging:Java#Apache_Maven

Something like "For more information please see 'man %mvn_build'" should
be sufficient.
> 230 tests for pom_ macros, provides/requires generators, backend library,
> mvn_* scripts. More to come
>
> rawhide build: http://koji.fedoraproject.org/koji/taskinfo?taskID=5954475

Thanks,
Severin

[Stanislav Ochotnicky]

Quoting Severin Gehwolf (2013-09-19 12:12:15)
> > Other things:
> > Support for SCLs in macros, scrips etc which needed serious rework so bugs
> > may be present bug backward compatibility should be preserved
> > Man pages for RPM macros (also in previous release, just forgot to mention it)
>
> Can I ask you to add this to:
> https://fedoraproject.org/wiki/Packaging:Java#Apache_Maven
>
> Something like "For more information please see 'man %mvn_build'" should
> be sufficient.

I'd love to, except all guideline changes have to go through FPC. I was planning
to redo whole Java guidelines and split off macros into a "howto" style
document[1]. I started working on it, then went on PTO for a month, then came a
lot of different issues that needed to be solved ASAP so this was low
priority...In any case current guidelines don't reflect current state of Java
packaging (once again).

[1] http://sochotni.fedorapeople.org/java-packaging-howto/#_macros_for_pom_xml_m...