@carlw the server is always only accessed by one user (the browser plugin) connections from outside of the computer is not possible, the server only listens on localhost

so I am not too worried about blocking or sync problems

@ron the jetty server is embedded in the plugin?

no its embedded in keepassFX

do you use gitlab?

no (looking it up)

an alternative to GitHub?

yes but with the possibility for private repo's in the free package

i just signed up as walkerca

you have an invite

thx. checking it out. i have some rare Kotlin time this morning. I'll be good to look some over. I'm really interested in the serverside Kotlin you had going even if it's not a server in the sense of a separate piece of hardware.

rofl be gentle, I learned javafx and kotlin in this project, been rewritten so often now

np. did you have the slackspace and fxlauncher jars installed from another maven repo?

no I cloned and compiled them

is this a standalone app or something you're running in jpro?

its a standalone app

and jetty is used for compatibility with the existing protocols and api?

no, its just an easy http server to hang into it

I actually thought about just doing it with

ServerSocket

😉

did you look at it shows the interaction between the browser plugin and keepassFX

got it. i missed the UI -> server <- browser interplay

i'm getting compiler errors in the Java classes looking for Kotlin classes. For example, /home/carl/git/keepassFX/src/main/java/keepassFX/keepassserver/KeePassLookup.java:[6,23] cannot find symbol [ERROR] symbol: class Cryptor [ERROR] location: package keepassFX.utils

yeah for some reason it works fine when I use it once from intellij then maven finds it. seems to be a chicken egg situation where the kotlin is not compiled before the java

is one reason why I started to rewrite the java classes to kotlin last week

are you able to pin your build against a release version of openkeypass?

no there is stuff in the latest snapshot that I use

looking into the compilation problem

i think i fixed it. I moved the kotlin compiler up earlier in the phases <plugin> <groupId>org.jetbrains.kotlin</groupId> <artifactId>kotlin-maven-plugin</artifactId> <version>${kotlin.version}</version> <executions> <execution> <id>compile</id> <phase>process-sources</phase> <goals> <goal>compile</goal> </goals> </execution> <execution> <id>test-compile</id> <phase>process-test-sources</phase> <goals> <goal>test-compile</goal> </goals> </execution> </executions> </plugin>

using process-sources rather than compile