Problems executing file in the packaged application - kotlin-multiplatform

I am making a desktop app with compose. When I run it in IntelliJ IDEA it works fine, but when I package it (.\gradlew :createDistributable ) it gives me the following error "Provider 'jar' not installed". The application fails when trying to open a file found in resources, the part of the code is as follows:
val url = PointerEventPass.Main::class.java.classLoader.getResource("repositorio/$archivo")!!
val file: File = Paths.get(url.toURI()).toFile()
val desktop: Desktop = Desktop.getDesktop()
desktop.open(file)
Thanks for your time.

Related

How to point document library to a network drive when run Liferay as Window Service

I installed Liferay as a Windows service following this tutorial .
After that I created a Network Drive 'D', I created a folder named 'document_library' in this drive D and updated Advanced File System Store to point to this folder. It work well when I run liferay from CMD window:
catalina.bat run
However, if I start Liferay by starting installed service, it throws exception: Unable to create directory D:\document_library
I tried adding full permission for everyone but still not solved yet.
How can I fix this issue?
I have this answer . Followed him and it work.
Instead of using shared driver letter, we must use UNC path. Something like
\\server\share\path

codecept: command not found in PhpStorm + Babun

I´m trying to use Codeception for WordPress.
Environment
OS : Windows 10
IDE : PhpStorm
Terminal (in PhpStorm) : Babun
I managed with composer to build the project wp-browser but when I try to run a command with the key word codecept, I got this error :
bash: codecept: command not found
I checked my PhpStorm configuration in Settings > Languages & Frameworks > PHP > Test Frameworks and I can see :
Path to codeception executable : E:\path\my-test-project\vendor\codeception\codeception
I had in PATH for all users E:\path\my-test-project\vendor\codeception\codeception after following this question, without success.
When I test the command codecept in Babun outside the PHPStorm Terminal, that works, so it seems to be a PhpStorm problem.
What could be the thing I forgot ?
I tried again and now it works.
I´m not sure the reason why but it could be because on PHPStorm I clicked (to resolve an other problem ) on
File > Invalidated Caches / Restart....

Not able to run .vbs file from jenkins which is having excel script

I’m new to Jenkins and now I'm doing basic level of execution. And I need your help resolve my issue. Issue Description: I’m trying to run the .VBS file by using jenkins and getting below error:
C:\Users\Amar\Desktop\Test_Sample.vbs(3, 2) Microsoft Excel: Microsoft Excel cannot access the file ‘C:\Users\Amar\Desktop\New.xlsx’.
There are several possible reasons:
The file name or path does not exist.
The file is being used by another program.
The workbook you are trying to save has the same name as a currently
open workbook.
I have not opened any excel file and path also correct.
please find below batch command : CScript “C:\Users\Amar\Desktop\Test_Sample.vbs”
And in Test_Sample.vbs file having:
Dim ExcelObj, WbookObj, mysheet
Set ExcelObj= CreateObject("excel.application")
Set WbookObj= ExcelObj.workbooks.open("C:\Users\Amar\Desktop\New.xlsx")
Set mysheet= ExcelObj.ActiveWorkbook.Worksheets("Sheet1")
ExcelObj.Visible = False
ExcelRowCount = mysheet.UsedRange.Rows.Count
For Iterator = 2 To ExcelRowCount
ModuleName = Ucase(Trim(mysheet.Cells(Iterator,1)))
ExecutionFlag = Ucase(Trim(mysheet.Cells(Iterator,2)))
if (moduleName="Raj") Then
Set qtApp = CreateObject("QuickTest.Application")
If qtApp.launched True then
qtApp.Launch
End If
qtApp.Visible = True
qtApp.Open "F:\Jenkins_Jobs\OnCall_Sanity_Automation\DriverScript\Sample", False
Set QTPTest=qtApp.Test
QTPTest.Run 'Run the Test QTPTest.Close
qtApp.quit
Set qtApp = Nothing
else
MsgBox "Name not exists"
End If
Next
Please help me to resolve the issue.
Thanks, Amar
Update
Console Output:
Building in workspace C:\Program Files
(x86)\Jenkins\workspace\Excel_Test [Excel]
$ cmd /c call C:\WINDOWS\TEMP\jenkin02.bat (C:\Program Files
(x86)\Jenkins\workspace\Excel_Test>CScript )
C:\Users\Admin\Desktop\Test_Sample.vbs"
C:\Users\Admin\Desktop\Test_Sample.vbs(3, 2) Microsoft Excel:
Microsoft Excel cannot access the file
C:\Users\Admin\Desktop\New.xlsx. There are several possible reasons:
** The file name or path does not exist.** The file is being used by another program. The workbook you are trying to save has the same
name as a currently open workbook.
If you are working on 64-bit Windows Operating System.
Then go to
C:\Windows\SysWOW64\config\systemProfile
Above Folder and create an empty Folder, and name it "Desktop" inside "systemProfile".
For doing this, you need system admin access
After creating the folder as mentioned, then run your build in Jenkins.
Run the jenkins job in command prompt on a slave,it will work!
Set Full control permissions for below path "Desktop" directory
"C:\Windows\SysWOW64\config\systemprofile\Desktop " (for 64 bit Windows) or "C:\Windows\System32\config\systemprofile\Desktop " (for 32 bit Windows)
If Desktop directory in present please create and give Full control permissions

javafx native package error invoking method

I'm developing a desktop application using javafx v8.0.60. I have created an exe package with ant in netbeans 8. When I run exe file in my computer, it is installed and run without any problem.
On the other hand, when I try to install and run it on some other computer, at the end of installation, window dialog pops up:
"Error invoking method"
I click Ok. Another window pop up saying:
"Failed to launch jvm"
Davood, greetings! I had this same problem and I, like you, found no help anywhere.
I submit to you a solution, which miraculously worked for me and helped me make sense of those blasted "Error invoking method." and "Failed to launch JVM" dialogs:
Find your .jar file
It has the same name as your Project and it's in your application's installation directory under AppData\Local\{ApplicationTitle}\app (shortcut: type %appdata% into explorer); if your project was named HelloWorld, there you will find HelloWorld.jar
Navigate to it's directory in command prompt
shift+Right Click any blank spot in the Explorer window and choose "Open command window here" (that's a fancy trick I recently learned; alternatively you would cd to the same directory using the command prompt)
Run your .jar via the command line
type java -jar "HelloWorld.jar" and hit Enter
Tadah! Behold your hidden exceptions (the existence of which "Error invoking method." so vaguely tries to communicate to you). *
If your problem is similar to mine it stems from a file structure difference between the project out folder and the installation directory, and that's why the program compiles just fine in the editor and builds just fine—there isn't a problem until it's built out, and the file structure is a little different.
*If you didn't get anything when you ran it via the command line, look for any errors that could be happening during that initialize() method; that's where your problem likely is. You can expose any exceptions during runtime by using a Popup Exception Dialog like shown in a similar problem, here.

AIR3 Native Process will not start in release build

Currently I am building an application that launches crtmpd (a rtmp server written in C++).
Whenever I launch the application from within Flash Builder it works great, if I install a release build from an air file the process.start() returns a generic "could not start process" error.
The crtmpserver.exe is stored in applicationDirectory and the config file is kept in applicationStorageDirectoy.
So I've moved it to the native storage directory. But the problem persists. I've found the following though:
startupInfo = new NativeProcessStartupInfo();
startupInfo.executable = binFile;
processArgs = new Vector.<String>();
processArgs.push(luaFile.nativePath);
startupInfo.arguments = processArgs;
In the IDE after this startupInfo is setup correctly. On client machines all properties of startupInfo are still null.
You might want to try putting it in the application storage directory. I've seen permissions issues were the user wasn't Admin and could't run a native process once it was installed.
The problem was I was packaging with an Air installer rather than a native installer.
Once I packaged with the appropriate installer the problem has resolved itself.

Resources