We are using install4j 7.0.12 with JDK 1.8 and when building in linux giving below error (--win-keystore-password' password is wrong ) , whereas password of the keystore is correct . and we are passing the password from pom.xml only . same build is ruuning fine in local (windows ) .
Please advise
15:12:58 The ' characters around the executable and arguments are
15:12:58 not part of the command.
15:12:59 [INFO] install4j version 7.0.12 (build 7368), built on 2019-06-25
15:12:59 [INFO] Using Java 1.8.0_181 from /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-7.b13.el7.x86_64/jre
15:12:59 [INFO] Registered to
15:12:59 [INFO] 15:12:59 [INFO] Loading config file /home/jdk_install/compl/target/installer/my-setup.install4j
15:13:01 [INFO] install4j: compilation failed. Reason: Password might be wrong. (Windows)
Please advise
one update , just found that this failing at this plugin
install4j-maven-plugin:1.1.1:compile (compile-installers)
Related
I am just starting off on google-cloud-platform. I have created an account and a project on cloud console. I was trying to run some of the sample apps provided.
I started with the sample app for cloud storage provided at:
https://github.com/GoogleCloudPlatform/java-docs-samples/tree/master/storage/cloud-client
I have installed apache maven 3.5.0 on my PC.
I followed the steps provided in the link, that is I gave the following commands:
mvn clean package -DskipTests
and then
mvn exec:java -Dexec.mainClass=com.example.storage.QuickstartSample -Dexec.args="my-bucket-name"
The first command succeeded. However, the second command failed.
I got the following error:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:06 min
[INFO] Finished at: 2017-06-15T18:27:55+05:30
[INFO] Final Memory: 15M/172M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:java (default-cli) on project storage-google-cloud-samples: An exception occured while executing the Java class. connect timed out -> [Help 1]
Now, the computer where I was running this command on, is behind a proxy. However, my proxy settings have been set in the file conf/settings.xml, also when I ran the first command, it successfully downloaded some packages, so I'm not sure if it is due to some proxy issue, however to check, I tried it on another machine, which is not behind a proxy.
I gave the same two commands. The first one succeeded and the second failed again, with the following (different) error:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:02 min
[INFO] Finished at: 2017-06-15T18:22:31+05:30
[INFO] Final Memory: 13M/32M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:java (d
efault-cli) on project storage-google-cloud-samples: An exception occured while
executing the Java class. 401 Unauthorized -> [Help 1]
So my queries are:
What could be the cause for the error in the first case? Is it something to do with proxy settings? If yes, then where/how should I specify the settings?
What could be the cause for the error in the second case where I am not behind any proxy?
Am i missing some step here?
Also , if you look at the source for this sample app, there is just a single file which basically creates a bucket. The bucket is passed as an argument from command line. Now, as per my understanding, first there needs to a project in the cloud console to create any resources. So where will this bucket be created? As in shouldn't we be specifying the project-ID where this bucket is to be created?
TL;DR - You're missing the credentials, the example relies on to invoke the desired Google Cloud APIs. Using Application Default Credentials is the recommended approach when using the Google Cloud APIs using any of the Client libraries.
Longer version
The example relies on Application Default Credentials (as explained in the README.md of the github repo you're using).
How the Application Default Credentials work
You can get Application Default Credentials by making a single client
library call. The credentials returned are determined by the
environment the code is running in. Conditions are checked in the
following order:
The environment variable GOOGLE_APPLICATION_CREDENTIALS is checked. If this variable is specified it should point to a file that
defines the credentials. The simplest way to get a credential for this
purpose is to create a Service account key in the Google API Console:
a. Go to the API Console Credentials page.
b. From the project drop-down, select your project.
c. On the Credentials page, select the Create credentials drop-down,
then select Service account key.
d.From the Service account drop-down, select an existing service
account or create a new one.
e. For Key type, select the JSON key option, then select Create. The
file automatically downloads to your computer.
f. Put the *.json file you just downloaded in a directory of your
choosing. This directory must be private (you can't let anyone get
access to this), but accessible to your web server code.
g. Set the environment variable GOOGLE_APPLICATION_CREDENTIALS to
the path of the JSON file downloaded.
If you have installed the Google Cloud SDK on your machine and have run the command gcloud auth application-default login, your
identity can be used as a proxy to test code calling APIs from that
machine.
If you are running in Google App Engine production, the built-in service account associated with the application will be used.
If you are running in Google Compute Engine production, the built-in service account associated with the virtual machine instance
will be used.
If none of these conditions is true, an error will occur.
As the title says, After I have updated my OS to El Capitan all my apps on Appcelerator Studio does not build successfully anymore. Even newly created sample apps does not build. I only get a very generic error message from the console.
My app is targeted for iOS and Android and it does not work for both. I get the same error message as below.
[INFO] : ----- OPTIMIZING -----
[INFO] : - android/alloy.js
[INFO] : - android/alloy/sync/localStorage.js
[INFO] : - android/alloy/sync/properties.js
[INFO] : - android/alloy/sync/sql.js
[INFO] :
[INFO] : Alloy compiled in 1.48612s
[INFO] : Alloy compiler completed successfully
[ERROR] : invalid request
How to resolve this? I already tried to project clean multiple times.
That has nothing to deal with the operating system.
Solution;
Open terminal
appc logout
appc login
Ta dah! - solved :-)
Following Jenkins documentation jenkins docs
I can use the POM_VERSION environment variable to take the current version from the pom file.
But for some reason the POM_VERSION environment variable is not being refreshed from build to build. for example:
I changed the version number manually but the build number that exported was the last from the previous build.
From my python script:
print 'Current version is ' + os.environ['POM_VERSION']
which gives the following log Current version is 0.1.5 which is clearly wrong because i changed it. you can further see it in my maven versions goal output:
[INFO]
[INFO] --- versions-maven-plugin:2.1:set (default-cli) # ep-reporter ---
[INFO] Searching for local aggregator root...
[INFO] Local aggregation root: /var/lib/jenkins/jobs/exchange-planner- reporter/workspace
[INFO] Processing com.exelate:ep-reporter
[INFO] Updating project com.company:ep-reporter
[INFO] from version 0.1.8 to 0.1.6
Props: {project.version=0.1.6, project.artifactId=ep-reporter, project.groupId=com.company}
note that it went from 0.1.5 because i have a script that advances it. but maven clearly states that its changing it from 0.1.8 to 0.1.6 which is not what POM_VERSION says
Thanks.
That environment variable is set at the time Jenkins first reads your POM file. You are clearly changing it during the build.
If you are changing it during the build, you know what you are changing to, and you should use the same mechanism to display it later.
I had the same problem and I resolved it by setting "Check-out Strategy" option to "Always checkout a fresh copy" in Source Code Management section.
I followed instructions from the phonegap platform guides to create a hello world app and deploy to BB10. Had no problems with Android or iOS, but when I try to run the app on a BB10 I get this output:
$ platforms/blackberry10/cordova/run --device --keystorepass passhere --devicepass devicepasshere
[INFO] Target Z30-2ba65880 selected
[INFO] The existing debug token is valid
[INFO] Deploying debug token to target "Z30-2ba65880"
[INFO] Sending request: INSTALL_DEBUG_TOKEN
[INFO] Action: Install Debug Token
[INFO] File size: 2645
[INFO] result::success
[INFO] Populating application source
[INFO] Parsing config.xml
[INFO] Generating output files
[INFO] Package created: /Users/adriaan/Documents/phonegap/hello/platforms/blackberry10/build/simulator/bb10app.bar
[INFO] Package created: /Users/adriaan/Documents/phonegap/hello/platforms/blackberry10/build/device/bb10app.bar
[INFO] BAR packaging complete
[INFO] Sending request: INSTALL_AND_LAUNCH
[INFO] Action: Install and Launch
[INFO] File size: 78983
[INFO] Installing com.example.hello.testDev_ample_hellodf4765a1...
[INFO] Processing 78983 bytes
[INFO] actual_dname::actual_id::
[INFO] actual_version::result::failure 500 'ascii' codec can't decode byte 0xe2 in position 120: ordinal not in range(128)
I've tried this on Mountain Lion and Mavericks. On Mountain Lion I had the native and webworks sdks installed, on Mavericks only the Web Works.
Somewhere in your project some data is not correctly encoded as UTF-8. Check your filenames and file content for non UTF-8 characters and make sure you escape or replace them.
I face same issue please follow below step i resolve this issue by change the author name from bar-descriptor.xml
solution 1)
changed the author simply to "Julian Buss", recreated the debug token, cleaned the project and then I could run it on the device. Problem solved. click here
solution 2)
Remove debug token from your device or simulator please follow below step
1) goto Setting->Security and Privacy->Development Mode-> click on remove debug token button(This button is display if and only if you have install any debug token )
2) if you have not install debug token then regenerate debug token and install it.
I hope this will work This solution is work for me.
I am in need of accessing data that is produced through a maven build during a run on Jenkins which is then used in a curl command. This ultimately sends a message to a bot to post in a chat room. Plugins are not an option for this particular chat client unless I would be the one to make them. Any other plugins that would be able to execute curl or hit url are fine given I can get to the data.
Currently when I run the command
mvn surefire-report:report
I am able to see output like this from the job:
...
Results :
Failed tests:
passwordLengthRequirement(test.java.com.company.appium.suites.RegistrationTest): expected:<P[assword must be 6 characters or longer].> but was:<P[lease accept the Terms of Service].>
...
Tests in error:
SendText(test.java.com.company.appium.suites.ChatTest): Timed out after 10 seconds waiting for presence of element located by: By.xpath: //window[2]/UIAKeyboard[1]/UIAKey[5]
...
Tests run: 40, Failures: 3, Errors: 2, Skipped: 4
[ERROR] There are test failures.
Please refer to .../target/surefire-reports for the individual test results.
[INFO]
[INFO] <<< maven-surefire-report-plugin:2.16:report (default-cli) # ios_junit <<<
[INFO]
[INFO] --- maven-surefire-report-plugin:2.16:report (default-cli) # ios_junit ---
[WARNING] Unable to locate Test Source XRef to link to - DISABLED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17:26.412s
[INFO] Finished at: Mon Jan 13 11:19:25 EST 2014
[INFO] Final Memory: 16M/81M
[INFO] ------------------------------------------------------------------------
Recording test results
If there are variables that can be used to get the data that would be a huge help but I don't know what they are if they even exist. My latest attempt has been to use the Post Build Task plugin to access the build.xml or log files with completed output. When trying to grep the build.xml that is created and extract the data I need grep is not working for some reason
XML:
`<failCount>72</failCount>`
`<skipCount>4</skipCount>`
`<totalCount>76</totalCount>`
Command:
$FAIL_COUNT=grep "failCount" ../../builds/$BUILD_NUMBER/build.xml | cut -d">" -f2,2 | cut -d"<" -f1,1
Output:
+ =grep failCount ../../builds/25/build.xml
/var/folders/2b/jv3l9cys1sqbbk6l2hxx_n1000007c/T/hudson6366869578068337646.sh: line 3: =grep: command not found
This page has been helpful with getting other variables but does not list what could be available during a maven run
https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-JenkinsSetEnvironmentVariables
The message I am ultimately trying to send would be something like
Finished with status '$BUILD_STATUS'. Total tests run '$TOTAL_COUNT'. Total failed tests '$FAIL_COUNT'.
Thanks in advance for any suggestions.