I am using HawtIO (2.7.1) standalone jar and trying to add new custom plugin in it but its throwing an exception as
enter image description here"java.lang.IllegalStateException: Failed to delete temp dir C:\Users\e5601428.hawtio\tmp at org.eclipse.jetty.webapp.WebInfConfiguration.configureTempDirectory(WebInfConfiguration.java:376)
at org.eclipse.jetty.webapp.WebInfConfiguration.resolveTempDirectory(WebInfConfiguration.java:264) at org.eclipse.jetty.webapp.WebInfConfiguration.preConfigure(WebInfConfiguration.java:69) at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:506) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:544) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:113) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131) at org.eclipse.jetty.server.Server.start(Server.java:452)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
at org.eclipse.jetty.server.Server.doStart(Server.java:419) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at io.hawt.embedded.Main.run(Main.java:154) "
enter image description here
Custom plugin is not yet supported in 2.7.1. It will be supported in 2.8.0 (we will release it soon). For the time being you can test it by checking out the source repository and run mvn clean install to get hawtio-app/target/hawtio-app-2.8-SNAPHOST.jar.
You can test a custom plugin by running as follows:
java -jar hawtio-app/target/hawtio-app-2.8-SNAPSHOT.jar -pd examples/simple-plugin/target/
after building the full project.
Related
I'm new to Go programming and trying to set up the BDD framework Godog. I have extracted the Linux binary from the Github releases page and placed it on my $PATH. When I run it, I get the following error:
Error: failed to compile testmain package: fork/exec /opt/hostedtoolcache/go/1.17.7/x64/pkg/tool/linux_amd64/compile: no such file or directory - output:
For some reason godog version does not show an actual version, which leads me to believe it's not installed correctly.
❯ godog version
Show current version
Additional system information:
❯ go version
go version go1.18.3 linux/amd64
I don't know if this is relevant, but I'm using asdf to manage my local go installation.
I am building a custom capacitor plugin with:
npm init #capacitor/plugin
This creates my plugin but following the directions it says to run:
npx cap sync
But I get this error: npm ERR! could not determine executable to run
I'm just adding this info as I'm not sure if it affects anything...
So I created my Java class in Android studio (AS) to extend capacitor-push-notifications. All this works in AS but I wanted to create a plugin so if something happens to the android folder I can rely on my plugin to add the Java files.
I import the file (in Java):
import com.capacitorjs.plugins.pushnotifications.PushNotificationsPlugin
My question is: How do I import the capacitor-push-notifications when I am in VS Code? I get the following error when I run npm run verify:android:
Could not find com.capacitorjs.plugins.pushnotifications:pushnotifications:1.0.9.
Required by:
project :
also, I did install the plugin:
npm i #capacitor/push-notifications
also added this to build.gradle under dependancies:
implementation "com.capacitorjs.plugins.pushnotifications:pushnotifications:1.0.9"
So do I just ignore the error as I know it works in AS? I looked everywhere and cannot find any reference to this.
I am facing similar issue like this mentioned in the post:
Triying to run VLC for unity plugin demo
Build platform is WIN 10 x64 (build 2004).
I am using LibVLC from the nightly build: https://artifacts.videolan.org/vlc/nightly-win64-llvm/20200914-0434/
LibVLCSharp gets built successfully (https://code.videolan.org/videolan/LibVLCSharp/-/tree/master/).
I was trying to build "VLCUnityPlugin.dll" but failing (have installed https://github.com/mstorsjo/llvm-mingw/tree/20200325 (LLVM MinGW)), using MSYS64 to run ./build.sh and it was coming up with this error:
MSYS error while building VLCUnity plugin dll
I thought maybe since "VLCUnityPlugin.dll" is NOT present, Unity x64 (v 2019.4.8f1) keeps on complaining with the following errors:
UNITY errors
But after, I hacked "common" make file as shown below:
make file changes to build VLCUnityPlugin.dll
I successfully built VLCUnityPlugin.dll and my plugin file structure looks like this now:
Plugin directory structure
Still, I do see UNITY Errors:
"Assets\VLCUnity\Demos\Scripts\MinimalPlayback.cs(99,39): error CS1061: 'MediaPlayer' does not contain a definition for 'GetTexture' and no accessible extension method 'GetTexture' accepting a first argument of type 'MediaPlayer' could be found (are you missing a using directive or an assembly reference?)"
The free trial version is available for download here https://videolabs.io/vlc-unity/vlc-unity-windows-trial.unitypackage.
That being said, if you want to build it yourself, you should follow what the CI does https://code.videolan.org/videolan/vlc-unity/-/blob/master/.gitlab-ci.yml
The libvlcsharp build is a special one, you need to define UNITY when you build it. It has the added GetTexture method.
For VLCPlugin.dll, you should crosscompile from Linux, where you install llvm-mingw and run it from bash (for example). MSYS not needed.
I made a JavaFX app and packaged it as a .exe. When I installed it on another pc and tried to run it I get a screen with:> Error invoking method
After that I get a screen with:
Failed to launch JVM
I added my libraries to the compile & run sections. But probably there is still something wrong with them (not being packaged or something).
When I try to run the jar I get:
Caused by: java.lang.ClassNotFoundException: javax.persistence.Persistence
Make sure you bundled the jar containing that class... looking at this similar thread you can get the jar from here: http://ebr.springsource.com/repository/app/bundle/version/detail?name=com.springsource.javax.persistence&version=2.0.0
While trying to build Hadoop 2.0.5 I got this error:
[ERROR] Failed to execute goal
org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-3:compile (hdfs) on
project hadoop-hdfs: Execution hdfs of goal
org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-3:compile failed:
Unable to load the mojo 'compile' in the plugin
'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-3'. A required
class is missing: groovy/lang/GroovyObject
This happened after running:
mvn package -Pdist -DskipTests -Dtar
I installed Groovy and put it in my PATH variable, didn't help.
Any ideas?
Solved
The repository files located in ~/.m2/repository were curropted
I deleted all of them and when trying to rebuild it automatically downloaded the required, uncurropted files