plexus-classworlds | Current master is now at https : //github

I am trying to call an OWL API java program through terminal and it crashes, while the exact same code is running ok when I run it in IntelliJ.

The exception that rises in my main code is this:

I am trying to obfuscate a jar-with-dependencies (although the same problem affects if I set as inFile the regular single jar).

I am using Java 8, but I have to use newer versions of Proguard and Proguard Maven Plugin, due to coverage of some jar dependencies that are from a higher version (otherwise I get an "Unsupported major-minor version" problem).

When executing "mvn clean install" the step is executed but I get a "proguard jar not found in pluginArtifacts error". See log below.

I have seen in Proguard Maven Plugin code that now you need (from 7.0.0) both proguard-base and proguard-core from com.guardsquare instead of the outdated previous version in net.sf.proguard - this one is not prepared for later jars.

Apparently the proguard jar is not found where I am specifying it - how should I include this dependency?

I am using this in my pom:

I have Maven installed, and it was working fine yesterday, however now it is displaying the infamous (Maven error: Could not find or load main class org.codehaus.plexus.classworlds.launcher.Launcher)

I followed this documentation to add Walkmod to eclipse but found that there is issue with the ivy-2.4.0. Previously I have tried Walkmod with CMD and its working. The steps I followed to make Walkmod commands recognizable in CMD are

1. Download the walkmod-Installer from https://walkmod.com
2. In environment variable added "WALKMOD_HOME" and "MAVEN_HOME" are added along with corresponding system path variables also added. i.e "%WALKMOD_HOME/bin%"
3. After this walkmod --version will be working but it will throw a issue with the command $ walkmod apply . It shows dependency issues. This issue can be fixed by replacing Walkmod_dir/Walkmod-3.0.0/lib/ivy-2.4.0 inside the walkmod-Installer you have downloaded from https://walkmod.com with ivy-2.5.0.

After the above three steps the Walkmod is making changes as per the requirement. The CMD output after $ walkmod check

I created a maven project with IntelliJ IDEA, following a tutorial.

The tiny project in JDK11 is to demo (for myself) how com.google.code.gson serializes an object to a json string.

This project's POM is:

so I have a simple project like:

I have a maven multi-module project on TeamCity. I'm using TeamCity's built in maven 3.5 tooling.

In one of the child projects, in the section of its pom.xml I set "dev".

Later in the pom I use the properties-maven-plugin to load a file with the name "${target.env}.env.properties"

Locally if I run "mvn package -Dtarget.env=prod" in the parent project, the child project loads prod.env.properties as expected.

If I configure my teamcity build with param("system.target.env", "prod"), I can see "-Dtarget.env=prod" passed to the maven execution in the build log (where teamcity invokes the plexus-classworlds launcher to do so), the child project loads dev.env.properties, breaking the build.

Here's my questions:

Why does the behavior differ? How do I reconcile this?

Update including some of the information @khmarbaise asked for:

The properties-maven-plugin is being used to load an environment specific set of properties based on which environment the application will run in. It is set up to choose which file to load based on a system property, and a default value is set in the properties block to avoid having to constantly add -Dtarget.env=dev during development. The properties-maven-plugin configuration for the child project is as follows:

I've encountered some difficulties trying to build JavaFX app using maven. The app work just fine from IDE. I run maven package task and it creates JAR file. The problem is this file doesn't run. I've checked included manifest and there wasn't entry point. I've added it, but the file still doesn't run. That's how the manifest looks now (the last string was added manually):

When I run mvn compile exec:exec, everything works fine, but when I click the debug button for the same configuration, it gives me the following error: