[Bug 210471] syslog-ng fails to build with JAVA option enabled
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Jun 22 16:32:48 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210471
Bug ID: 210471
Summary: syslog-ng fails to build with JAVA option enabled
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: Karli.Sjoberg at slu.se
Created attachment 171684
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=171684&action=edit
syslog-ng build log
Building with Poudriere and these options:
# This file is auto-generated by 'make config'.
# Options for syslog-ng-3.7.3_4
_OPTIONS_READ=syslog-ng-3.7.3_4
_FILE_COMPLETE_OPTIONS_LIST=DOCS GEOIP IPV6 JAVA JSON PYTHON REDIS SMTP SPOOF
SQL TCP_WRAPPERS
OPTIONS_FILE_SET+=DOCS
OPTIONS_FILE_UNSET+=GEOIP
OPTIONS_FILE_SET+=IPV6
OPTIONS_FILE_SET+=JAVA
OPTIONS_FILE_UNSET+=JSON
OPTIONS_FILE_UNSET+=PYTHON
OPTIONS_FILE_UNSET+=REDIS
OPTIONS_FILE_UNSET+=SMTP
OPTIONS_FILE_UNSET+=SPOOF
OPTIONS_FILE_UNSET+=SQL
OPTIONS_FILE_UNSET+=TCP_WRAPPERS
Fails with:
Could not resolve all dependencies for configuration
':common:compileClasspath'.
> Could not resolve log4j:log4j:1.2.16.
Required by:
java-modules:common:unspecified
> Could not resolve log4j:log4j:1.2.16.
> Could not get resource
'https://repo1.maven.org/maven2/log4j/log4j/1.2.16/log4j-1.2.16.pom'.
> Could not GET
'https://repo1.maven.org/maven2/log4j/log4j/1.2.16/log4j-1.2.16.pom'.
> repo1.maven.org
_One_ hit on google reveals:
https://syslog-ng.org/question/the-make-of-syslog-ng-is-failing-connection-to-httpsrepo1-maven-org-refused/
"The resolution was to add a gradle.properties file with the http proxy details
under the /modules/java-modules/ directory. Where the build.gradle was.
It would be good to update the documentation to include this tip."
Log attached to bug report.
TIA
Karli Sjöberg
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list