| Summary: | www-apps/guacamole-0.9.9 : [ERROR] Plugin org.apache.maven.plugins:maven-source-plugin:2.4 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-source-plugin:jar:2.4: Could not transfer ar | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | Andreas Schürch <nativemad> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | java |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge-history.txt
environment www-apps:guacamole-0.9.9:20160628-032359.log |
||
|
Description
Toralf Förster
2016-06-28 08:45:07 UTC
Created attachment 439050 [details]
emerge-history.txt
Created attachment 439052 [details]
environment
Created attachment 439054 [details]
www-apps:guacamole-0.9.9:20160628-032359.log
>Unknown host repo.maven.apache.org
It looks like dns is not available within that chroot!?
(In reply to Andreas Schürch from comment #4) no - DNS is fine. And $> links https://repo.maven.apache.org/maven2 works within a chroot flawlessly. Okok, then I guess this is the problem: --- log4j:WARN No appenders could be found for logger (org.apache.maven.wagon.providers.http.httpclient.client.protocol.RequestAddCookies). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. --- Do you have the file log4j.properties somewhere?!? Are you doing the merge with a console (which would be the default appender) attached, or do you start emerge in the background somehow?!? Does it work if you manually chroot and emerge? (In reply to Andreas Schürch from comment #6) This is the tinderbox - so yes, it is emerged via script. The package log4j is installed. No manual log4j configure step was ever made. There's no log4j.properties at that image. Ok :-) Maybe we should create such a property file to send the logs to /dev/null or something!? ...But it's Friday evening, the weather is fine, some friends will come over in a few mins, I guess you understand if it takes a bit to play with such a file.. ;-) Cheers! ;-) (In reply to Andreas Schürch from comment #8) enjoy the weekend ! :-) I guess the best solution would be to move to the java-ant eclasses to handle mvn in the long run...
Nevertheless, you can try to modify the mvn command in the ebuild to write a log instead of displaying it:
mvn -s "${S}"/settings.xml -l "${S}"/mvnbuild.log package
*** Bug 593252 has been marked as a duplicate of this bug. *** This happens because of FEATURES="network-sandbox". You're using Maven to do online stuff in src_compile, which really isn't allowed. Java team never calls Maven within Portage because it is not an easy beast to tame. I'm currently exploring a new approach but it may take some time. *** Bug 621862 has been marked as a duplicate of this bug. *** Package treecleaned. |
