Red Hat Bugzilla – Bug 977980
javapackages-tools: mvn-rpmbuild should be marked as deprecated
Last modified: 2013-11-07 02:11:11 EST
Description of problem:
mvn-rpmbuild should be deprecated (but not removed yet). Ideally the script itself would print a warning saying that it's not supposed to be used any longer and that users should mograte to other ways of building packages.
Version-Release number of selected component (if applicable):
Mikolaj, how should we do the equivalent of mvn-rpmbuild in eclipse builds ? Note: we haven't integrated with xmvn yet and do all our builds using mvn-rpmbuild. I want to be sure that we have a clean path forward before declaring it as deprecated.
Deprecating mvn-rpmbuild doesn't mean removing it. As long as there are more than a few packages using it and no obvious alternative is available it will be kept around.
As a long-term solution I think that adding support for installing Eclipse plugins would be ideal. I am working on automating installation of Eclipse plugins and features and I am aiming for Fedora 20.
Also take a look at bug#977984. One of important use cases of that feature is replacing binary JARs in lib/ directory of OSGi bundles with symlinks so that Eclipse plugins can be installed automatically.
Fixed in javapackages-tools-3.4.1-1
I believe that this bug is fixed in javapackages-tools-3.4.1-1,
which is available in Fedora Rawhide, so I am closing this bug now.
The build containing the fix can be found at Koji: