Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
HEAD-SNAPSHOT not being published
See original GitHub issueAccording to the docs I can get the latest master build via HEAD-SNAPSHOT from sonatype.
The latest build on there is outdated for a few weeks though.
The snapshot script that travis runs, fails. https://travis-ci.org/google/dagger/builds/219818626
It starts:
$ util/publish-snapshot-on-commit.sh
Publishing maven snapshot...
Throws a few warnings
til/execute-deploy.sh: 19: util/execute-deploy.sh: [[: not found
util/execute-deploy.sh: 22: util/execute-deploy.sh: [[: not found
and aborts with the errors
gpg: no default secret key: secret key not available
gpg: signing failed: secret key not available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.491s
[INFO] Finished at: Fri Apr 07 19:31:07 UTC 2017
[INFO] Final Memory: 11M/203M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.6:sign-and-deploy-file (default-cli) on project standalone-pom: Exit code: 2 -> [Help 1]
[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/MojoExecutionException
INFO: Loading complete. Analyzing...
INFO: Found 3 targets...
INFO: Building...
[0 / 6] BazelWorkspaceStatusAction stable-status.txt
[4 / 12] Building source jar compiler/libcompiler-src.jar
INFO: Elapsed time: 2.871s, Critical Path: 1.22s
util/execute-deploy.sh: 19: util/execute-deploy.sh: [[: not found
util/execute-deploy.sh: 22: util/execute-deploy.sh: [[: not found
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=192m; support was removed in 8.0
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-gpg-plugin:1.6:sign-and-deploy-file (default-cli) @ standalone-pom ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.132s
[INFO] Finished at: Fri Apr 07 19:31:15 UTC 2017
[INFO] Final Memory: 8M/143M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.6:sign-and-deploy-file (default-cli) on project standalone-pom: /home/travis/build/google/dagger/bazel-bin/shaded_compiler.jar not found. -> [Help 1]
[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/MojoFailureException
INFO: Loading complete. Analyzing...
INFO: Found 3 targets...
INFO: Building...
[0 / 3] BazelWorkspaceStatusAction stable-status.txt
[3 / 7] Building source jar producers/libproducers-src.jar
INFO: Elapsed time: 1.061s, Critical Path: 0.53s
util/execute-deploy.sh: 19: util/execute-deploy.sh: [[: not found
util/execute-deploy.sh: 22: util/execute-deploy.sh: [[: not found
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=192m; support was removed in 8.0
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-gpg-plugin:1.6:sign-and-deploy-file (default-cli) @ standalone-pom ---
gpg: no default secret key: secret key not available
gpg: signing failed: secret key not available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.744s
[INFO] Finished at: Fri Apr 07 19:31:21 UTC 2017
[INFO] Final Memory: 9M/143M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.6:sign-and-deploy-file (default-cli) on project standalone-pom: Exit code: 2 -> [Help 1]
[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/MojoExecutionException
INFO: Loading complete. Analyzing...
INFO: Loading package: @androidsdk//
INFO: Loading package: @androidsdk//com.android.support
INFO: Found 3 targets...
INFO: Building...
[1 / 16] BazelWorkspaceStatusAction stable-status.txt
[10 / 32] Writing file java/dagger/android/libandroid-src.jar-2.params
[25 / 34] Building AAR package for //java/dagger/android:android
INFO: Elapsed time: 7.390s, Critical Path: 1.27s
util/execute-deploy.sh: 19: util/execute-deploy.sh: [[: not found
util/execute-deploy.sh: 22: util/execute-deploy.sh: [[: not found
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=192m; support was removed in 8.0
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-gpg-plugin:1.6:sign-and-deploy-file (default-cli) @ standalone-pom ---
gpg: no default secret key: secret key not available
gpg: signing failed: secret key not available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.594s
[INFO] Finished at: Fri Apr 07 19:31:33 UTC 2017
[INFO] Final Memory: 9M/143M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.6:sign-and-deploy-file (default-cli) on project standalone-pom: Exit code: 2 -> [Help 1]
[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/MojoExecutionException
INFO: Loading complete. Analyzing...
INFO: Found 3 targets...
INFO: Building...
[0 / 28] BazelWorkspaceStatusAction stable-status.txt
[136 / 142] Building source jar java/dagger/android/support/libsupport-src.jar
INFO: Elapsed time: 3.980s, Critical Path: 1.96s
util/execute-deploy.sh: 19: util/execute-deploy.sh: [[: not found
util/execute-deploy.sh: 22: util/execute-deploy.sh: [[: not found
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=192m; support was removed in 8.0
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-gpg-plugin:1.6:sign-and-deploy-file (default-cli) @ standalone-pom ---
gpg: no default secret key: secret key not available
gpg: signing failed: secret key not available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.516s
[INFO] Finished at: Fri Apr 07 19:31:42 UTC 2017
[INFO] Final Memory: 9M/143M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.6:sign-and-deploy-file (default-cli) on project standalone-pom: Exit code: 2 -> [Help 1]
[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/MojoExecutionException
INFO: Loading complete. Analyzing...
INFO: Found 1 target...
INFO: Building...
[0 / 2] BazelWorkspaceStatusAction stable-status.txt
bazel-genfiles/shaded_android_processor.jar
INFO: Elapsed time: 0.667s, Critical Path: 0.05s
util/execute-deploy.sh: 19: util/execute-deploy.sh: [[: not found
util/execute-deploy.sh: 22: util/execute-deploy.sh: [[: not found
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=192m; support was removed in 8.0
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-gpg-plugin:1.6:sign-and-deploy-file (default-cli) @ standalone-pom ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.240s
[INFO] Finished at: Fri Apr 07 19:31:46 UTC 2017
[INFO] Final Memory: 8M/143M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.6:sign-and-deploy-file (default-cli) on project standalone-pom: POM not found /home/travis/build/google/dagger: /home/travis/build/google/dagger (Is a directory) -> [Help 1]
[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/MojoExecutionException
util/execute-deploy.sh: 77: util/execute-deploy.sh: java/dagger/android/processor/libprocessor-src.jar: not found
Issue Analytics
- State:
- Created 6 years ago
- Comments:8
Top Results From Across the Web
Record heap snapshots - Chrome Developers
Learn how to record heap snapshots with the Chrome DevTools heap profiler and find memory leaks.
Read more >How-to: Heap Snapshots. Handling Node.js Memory Leaks in…
Write a snapshot to the current working directory every half hour. Taking a snapshot is not free. It will peg a CPU until...
Read more >Take heap snapshot | Developer Guide - Nightwatch.js
Learn how to record heap snapshots right from your Nightwatch tests and use DevTools heap profiler to find memory leaks.
Read more >Heap Snapshots–Tracing All Heap Allocations | Random ASCII
The key thing about heap snapshots is that they only retain data for outstanding allocations – memory that has not yet been freed....
Read more >Fact (Truth HEAD-SNAPSHOT)
Creates a fact with no value, which will be printed in the format "key" (with no ... For example, isNotEmpty() would generate the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was looking into this yesterday actually. I haven’t had time to submit the changes, but the two things I believe need to be done are invoke the script with
bashnotshto get the[[working, and also make sure the deploy script properly loads the secrets. I believe those two things should be sufficient to get this fixedOk this is actually fixed and verified now 😃