How to locally merge an upstream pull request in GitHub?

How to import the Public Certificate of one WSO2 product to the trust store of another?

To demonstrate this point, I will use the 2 products WSO2 API Manager 2.1.0 (referred as APIM from here onwards) and WSO2 Enterprise Integrator 6.1.1 (referred as EI from here onwards). When using EI as the Business Process Server during configuration of Workflows in APIM, one step to perform is to import the public certificate of EI to the truststore of APIM [1]. So now let's see how this can be done. Step 1: Go to <EI_HOME>/repository/resources/security/ folder and execute the following keytool command. This command is used to export the public certificate of EI as a certificate file called wso2carbon.cer. Since the default keystore in EI is wso2carbon.jks, we have specified it as the keystore and the default alias is wso2carbon. Provide wso2carbon as the keystore password when prompted as it is the default password. After executing the above command from within the security folder in EI, you will see that a file with the name of wso2carbon.cer is created...

The JAR/ZIP file (...) seems corrupted, error: zip file is empty during maven build

You can easily solve this problem in 2 steps. Delete the file given in (...) this path, which is given in the error trace. Build the project again using mvn clean install . Cheers!

Integrating the JaCoCo code coverage plugin into a Java Maven project for unit testing with testng

I’ll show how to do this for both offline instrumentation and for using the JaCoCo runtime agent. It is very easy because you don’t need to change the usual way of writing your tests. Its only a matter of changing the pom.xml file in your maven project. 1. JaCoCo code coverage with JaCoCo runtime agent Since we use testng for unit test writing, we put the following dependency under dependencies. < dependencies > < dependency > < groupId > org.testng </ groupId > < artifactId > testng </ artifactId > < version > ${testng.version} </ version > < scope > test </ scope > </ dependency > </ dependencies > Then under build, we first need to have the JaCoCo plugin put under the plugins section of your project pom.xml. (Note - this is the parent pom we are referring to) This plugin configuration...

TechFacts

Search This Blog