javaopt | Java optimization course | Learning library

The new JRebel Agent no longer works using -javaagent. This change affects users previously running with the Legacy Agent from a command line (as well as on a remote machine or container) from here: https://manuals.jrebel.com/jrebel/misc/jrebel7-agent-upgrade-cli.html

Remove -javaagent argument from javaoptions or downgrade to an older JRebel version. Its working well just with -agentpath argument. Tested on newer Hybris + latest Java 11 + latest JRebel

In one Helm deployment, you always run one Hazelcast cluster. You need to run Helm command twice to create 2 separate Hazelcast clusters.

I can't tell you why you're seeing the behaviour you're observing. I can reproduce the error with SBT 1.3.13. When I use SBT 1.4.9 the custom task only runs once as you would expect.

Figured it out finally!

There were a couple of issues that required fixing for the entire test to pass. The issue at hand was that the mixin didn't appear to be utilised in the test. I required to change @input="updateConfig('java', 'java_xmx', $event)" to @input.native="updateConfig('java', 'java_xmx', $event)" of course! .native.

I then discovered that I hadn't mocked my state and had to do that.

The final code for the test is

Since I'm trying to run a Springboot app, the trick is to not try and launch your main class as you'd typically do but instead to use org.springframework.boot.loader.JarLauncher

This is more properly explained in a blog post by the Spring team

So a complete working example with Springboot looks like:

The best practice is to place application.conf into src/main/resources/ for regular use and into src/test/resources/ for testing. You'll have 2 conf files with different values in test. If you don't need to change config for test you can simply keep one conf file in main.

You don't have to override the file explicitly with -Dconfig.resource or -Dconfig.file for your tests because loading resources from class path will work as you expect out of the box and your test config will be used. -D option is mostly used at runtime to provide external configuration or in some complex build scenarios.

If you use -Dconfig.resource or -Dconfig.file pay attention to the path. config.resource is just a filename, i.e. application.conf which will be loaded as resource while config.file is an absolute or relative file path.

If you are making a library you can get fancy with reference.conf file having default values and application.conf overriding them. This could also work in your scenario but would be more confusing because that's not the purpose or reference file.

For the purposes of testing just use 2 application.conf files.

Additionally, here are some options to override config at runtime:

Overriding multiple config values in Typesafe config when using an uberjar to deploy.

Overriding configuration with environment variables in typesafe config

Scala environment ${USER} in application.conf

More info here: https://github.com/lightbend/config#standard-behavior

OK, you are using this example from the plugin source code repository. Why didn't you just say so and link to it? You made it look as if you created the sample by yourself. I found it and also the project/plugins.sbt which you did not post here. Like I told you before in our chat, I am a Scala noob, I never used it in my whole life and had no idea that a file was missing. That cost me a lot of time. Why did you post an incomplete sample project here instead of publishing it on GitHub like I asked you to? Then I could just have cloned the project and run it. Not until I found the sample code online, did I realise that yours was incomplete.

Furthermore, my IDE IntelliJ IDEA cannot import the sample project, there must be some kind of bug in the current version. I can only compile and run from sbt shell. There, I could finally reproduce your problem.

Actually, the explanation is quite simple: The plugin is outdated and ought to be updated ASAP. It depends on AspectJ Compiler Tools 1.8.10 which only supports Java 8. It is not even the most recent 1.8 release, that should be 1.8.13. Also, the plugin exports AspectJ Runtime 1.8.10 as a runtime dependency to projects using the plugin. See also:

• https://github.com/sbt/sbt-aspectj/blob/8ff3a1ad4224934dabe222205eb89c985670f240/build.sbt#L7
• https://github.com/sbt/sbt-aspectj/blob/8ff3a1ad4224934dabe222205eb89c985670f240/src/main/scala/com/lightbend/sbt/SbtAspectj.scala#L30

As long as you compile and run your project on JDK 1.8, everything is fine. If you use a more recent JDK, the solution is to override the dependencies. Put this into project/plugins.sbt:

You are running Jenkins itself as a container. Therefore the docker command line application must be present in the container, not the host.

Easiest solution: Use a Jenkins docker image that contains the docker cli already, for example https://hub.docker.com/r/trion/jenkins-docker-client

If you follow the steps to install apktool: https://ibotpeaches.github.io/Apktool/install/

You will notice there are 2 files you need:

1. a script (the one you posted), which you should name apktool and set to executable on linux chmod +x apktool
2. a jar file: apktool.jar

You need to have both files in the same directory for the script to work, so if you've moved the apktool file to /usr/share/apktool, you need to also move apktool.jar to /usr/share/apktool.jar