Bug 204666 - archivers/snappy-java: Force correct maven version, Take MAINTAINER'ship
Summary: archivers/snappy-java: Force correct maven version, Take MAINTAINER'ship
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Kurt Jaeger
URL:
Keywords: easy, patch, patch-ready
Depends on:
Blocks: 203432
  Show dependency treegraph
 
Reported: 2015-11-18 20:35 UTC by Mark Dixon
Modified: 2016-03-11 06:23 UTC (History)
4 users (show)

See Also:
koobs: maintainer-feedback+
koobs: merge-quarterly?


Attachments
Patch to force the correct maven version (545 bytes, patch)
2016-02-19 13:40 UTC, Mark Dixon
no flags Details | Diff
Patch to force the correct maven version and take over maintainership (856 bytes, patch)
2016-02-24 08:40 UTC, Mark Dixon
koobs: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Dixon 2015-11-18 20:35:41 UTC
Snappy java doesn't seem to build anymore, it looks like a Maven upgrade may have changed some of the plugin dependencies. Also we've just added a Maven 3.3 port for Spark so it might be worth the upgrade.

[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Unresolveable build extension: Plugin org.apache.maven.wagon:wagon-ssh-external:1.0-beta-7 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-7 has not been downloaded from it before. @ 
[ERROR] Unknown packaging: bundle @ line 9, column 14
 @ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project org.xerial.snappy:snappy-java:1.0.4.1 (/usr/ports/archivers/snappy-java/work/snappy-java-snappy-java-1.0.4.1/pom.xml) has 2 errors
[ERROR]     Unresolveable build extension: Plugin org.apache.maven.wagon:wagon-ssh-external:1.0-beta-7 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-7 has not been downloaded from it before. -> [Help 2]
[ERROR]     Unknown packaging: bundle @ line 9, column 14
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerException
Makefile:78: recipe for target 'target/snappy-java-1.0.4.1.jar' failed
gmake[1]: *** [target/snappy-java-1.0.4.1.jar] Error 1
gmake[1]: Leaving directory '/usr/ports/archivers/snappy-java/work/snappy-java-snappy-java-1.0.4.1'
*** Error code 2

Stop.
make: stopped in /usr/ports/archivers/snappy-java

See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203432 as this is breaking the Spark build for others.
Comment 1 Arjan van der Velde 2016-02-10 02:55:51 UTC
I had exactly the same problem. Apparently the problem was that I had maven-wrapper-1_2, maven3-3.0.5 and maven33-3.3.3_1 installed. After removing those, the build went fine. I suspect there is some interference between these packages (does snappy-java use a "local" maven?).

-- Arjan
Comment 2 Sergey Brunov 2016-02-13 20:42:19 UTC
(In reply to dj_noresult from comment #1)
Hello, Arjan!

Thank you for the hint: it helped!

Best regards,
Sergey Brunov.
Comment 3 Mark Dixon 2016-02-19 13:40:49 UTC
Created attachment 167175 [details]
Patch to force the correct maven version

This patch should force maven3 instead of using the system one.
Comment 4 Mark Dixon 2016-02-24 08:40:23 UTC
Created attachment 167356 [details]
Patch to force the correct maven version and take over maintainership

Also take over as maintainer as original maintainer is no longer using FreeBSD
Comment 5 Radim Kolar 2016-02-24 09:27:43 UTC
I approve patch
Comment 6 Mark Dixon 2016-02-24 13:57:30 UTC
Radim, do you need to change keywords / status for this to get merged?
Comment 7 Kubilay Kocak freebsd_committer freebsd_triage 2016-02-24 14:18:21 UTC
Comment on attachment 167356 [details]
Patch to force the correct maven version and take over maintainership

Good to go Mark, thank you for the patch
Comment 8 Kurt Jaeger freebsd_committer freebsd_triage 2016-03-10 18:56:25 UTC
testbuilds@work
Comment 9 commit-hook freebsd_committer freebsd_triage 2016-03-11 06:19:52 UTC
A commit references this bug:

Author: pi
Date: Fri Mar 11 06:19:27 UTC 2016
New revision: 410806
URL: https://svnweb.freebsd.org/changeset/ports/410806

Log:
  archivers/snappy-java: force correct maven, submitter becomes maintainer

  PR:		204666
  Submitted by:	Mark Dixon <mark@tranquillussoftware.co.uk>
  Approved by:	Radum Kolar <hsn@sendmail.cz> (maintainer)

Changes:
  head/archivers/snappy-java/Makefile
Comment 10 Kurt Jaeger freebsd_committer freebsd_triage 2016-03-11 06:22:07 UTC
Committed, thanks!