Failed to build the client examples.
C:\Users\predix\Desktop\OPC\milo-master\milo-examples\client-examples\src\main\java\org\eclipse\milo\examples\client\ClientExampleRunner.java:2: Line does not match expected header line of ' * Copyright (c) \d\d\d\d.*$'. [RegexpHeader]
The checkstyle plugin is failing because that file does't have the license header it expects. Did you modify it?
Related
I followed the instruction here:
Deploying Your iOS Application for Submission to the App Store
Failed when Step 4:
Select Project > Deployment, and click the Deploy button to deploy your application.
It is suppose to generate an .ipa file, but I got the following error messages:
paclient command line for "Dell_Macbook_Air"
c:\program files (x86)\embarcadero\studio\21.0\bin\paclient.exe -u8 --ipa="ESF RC1.app,ESF RC1.ipa,'Apple Distribution: Courant Tseng
(LB289US7N2)','/Users/Courant/Library/MobileDevice/Provisioning Profiles/49871f08-e3ef-4ef6-9cef-2756304c93c1.mobileprovision',2" Dell_Macbook_Air
[PAClient Error] Error: E0776 2021-10-12 17:18:30.006 xcodebuild[1464:20952] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/wm/8hg70w3n355g3qsc5k9z34hh0000gn/T/ESF RC1_2021-10-12_17-18-30.002.xcdistributionlogs'.
[PAClient Error] Error: E0776 Exported ESF RC1 to: /Users/Courant/PAServer/scratch-dir/Courant-Dell_Macbook_Air/ESF RC1.archive/temp
[PAClient Error] Error: E0776 ** EXPORT SUCCEEDED **
Failed
Can anyone give some advise to solve the problem so that I can send it to App Store (Testflight)?
Got answer from Embarcadero Customer Support Center.
This "error" is connected with the CFBundleName/CFBundleDisplayName. If these parameters in the project's project option contains space characters, this error will occur.
I removed the spcace character off mu app name (ESF RC1--> ESF_RC1)
It works.
BTW, according to them, the bug had been fixed in Rad Studio 11.
I writing automation tests with Cucumber/Selenide and I want to rerun failed scenarios.
This is part of my project with only two small tests (one is failing) to demonstrate behavior: https://github.com/mtpx/cucumberRerun
I read how to do it on How to rerun the failed scenarios using Cucumber? and https://medium.com/#belek.bagishbekov/how-to-rerun-failed-test-cases-in-cucumber-b7fe9b1dcf9c
In my application.feature test runner(ApplicationTest) in #CucumberOptions's plugins section I have line: "rerun:rerun/failed_scenarios.txt", according to previous urls it should generate text file with failed scenario, but after test execution with 'mvn clean test' (with failed scenarios) - there's no any rerun.txt file.
Do You know what is wrong here? Why after build i dont have rerun.txt file?
I using Selenide instead of Selenium, maybe problem is here?
Create another scenario file as shown below. Let's say this as FailedScenarios.java. Whenever you notice any failed scenario run this file. This file will use target/rerun.txt as an input for running the scenarios.
This line is require:
features = "#target/rerun.txt",
Full CucumberOptions
#CucumberOptions(
monochrome = true,
features = "#target/rerun.txt", //Cucumber picks the failed scenarios from this file
format = {"pretty", "html:target/site/cucumber-pretty",
"json:target/cucumber.json"}
)
public class FailedScenarios {
}
You can use rerun file path other than target if you need to run failed Scenario also trigger from maven , In that case change the path in both file you main runner and failed test runner
problem solved :)
In pom i had line:
-Dcucumber.options="--plugin io.qameta.allure.cucumberjvm.AllureCucumberJvm"
This line overrides all plugins information in TestRunner
We have an application that makes a backup of a configuration file by copying it to a sub-folder (see log file entry below) using the following command:-
BOOL b = MoveFileEx(ExistingFileSpec, NewFileSpec, MOVEFILE_REPLACE_EXISTING | MOVEFILE_WRITE_THROUGH | MOVEFILE_COPY_ALLOWED);
This appears to work as expected on most systems but on two we get the following warning in our log file:-
11 Jun 2018 10:58:05.437 W. COMMON WARNING MoveFile failed on C:\Program Files\Configuration\Stores.xml to C:\Program Files\Configuration\Backup\Stores.xml LastError=183
Lasterror =183 means "ERROR_ALREADY_EXISTS"
This is odd since MOVEFILE_REPLACE_EXISTING is specifically meant to enable this command to work when the target file exists.
This is happening on Win7 x86 machines.
In a previous version of the code MoveFile was used but with a DeleteFile call immediately prior to ensure the target file did not exist. When the code was rolled back to this version it works.
Any suggestions?
I'm using SoapUI version 4.5.1 on a Windows 7 box to create a mock webservice. It includes a Groovy script that is fired at an OnRequest event which attempts to create and send a second response.
The issue is to do with the installation of the groovy-wslite library, which I'm trying to use in order to instantiate a SoapClient object which sends the additional response.
If I include the following at the top of the script (as per the wslite github site at https://github.com/jwagenleitner/groovy-wslite):
#Grab(group='com.github.groovy-wslite', module='groovy-wslite', version='0.7.1')
... I get the following error:
java.lang.NoClassDefFoundError: org/apache/ivy/core/settings/IvySettings
If I remove it from the script, I get the following error:
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: Script6.groovy: 23: unable to resolve class SOAPClient # line 23, column 18.
def client = new SOAPClient(clientURL)
^
org.codehaus.groovy.syntax.SyntaxException: unable to resolve class SOAPClient # line 23, column 18.
Can anyone suggest what I'm doing wrong, please? Do I need to install groovy-wslite separately within SoapUI?
Thanks in advance for any advice.
I have downloaded the groovy-wslite jar and added it to my SoapUI installation's bin/ext directory.
I've got a working Maven project setup includuing IDL compilation with the org.codehaus.mojo:idlj-maven-plugin. If I'm running mvn compile on my console, the IDL compiler works just fine. If I do this in Eclipse Indigo (3.7.2) with m2e (1.0.1), first I get the following messages (orignal paths replaced with ~~~):
18.05.12 13:13:55 MESZ: [INFO] Processing 1 grammar files to ~~~/target/generated-sources/idl
18.05.12 13:13:55 MESZ: [DEBUG] Processing: ~~~/src/main/idl/MyRegistry.idl
This is the same I get on my console along with the same configuration parameter infos.
But at the end of the m2e process I get this line:
18.05.12 13:13:55 MESZ: [DEBUG] Created marker 'IDL Compilation failure (org.codehaus.mojo:idlj-maven-plugin:1.1:generate:default:generate-sources)' on resource '/mypackage.myregistry/pom.xml'.
But there is no error or something like this showing up indicating what went wrong.
In Eclipse I already switched the Maven runtime from internal to the external one I use also on the console.