maven-plugins | General Maven Plugins | Build Tool library

I copied configuration of maven shade plugin straight from apache maven documentation https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html

This is my current set up:

When trying to start a Spring Boot application with mvn spring-boot:run I get this error:

When I first run the install command, it runs into following problem.

i am using Maven 3.5.3 with JDK 1.8. When i try to compile from cmd my project with mvn clean compile, the console return the following errors:

Maven configuration failed this line just ruined my Friday night and still i am unable to solve it. Well,I am a big fan of visual studio code so i just decided to switch on vscode to eclipse for java development. but this is not the problem,Problem raise when i just try to add an external java library.I am unable to use it and i just get an error something like Class-not-Found or so on.

Well,this is my project structure in vscode

I've seen Building and deploying native code using Maven - but can't get this (very similar) deployment working as I'd like..

I have a C++ project that builds with Maven, and the Maven CMake Plugin. This involves several Maven profiles, to select the correct settings for the various C++ compilers I use on the platforms I'm building on. (Windows 10, Ubuntu 16.04, Ubuntu 18.04, CentOS 7, Raspbian, macOS High Sierra). I use Jenkins to run this build on the various VMs/Raspberry Pi - yielding a .tar.gz or .zip via the Maven Assembly Plugin. The final result is six archive files, that vary in their classifier/type. They all have the same groupId/artifactId.

I wanted each of these jobs to deploy its archive to Sonatype's OSSRH Nexus system, using the nexus-staging-maven-plugin.

I had this plugin configured to not automatically close the repository, so that the multiple builds could run via Jenkins (sequentially), and deploy to the same repo. I would then review this in the web UI, then Release or Drop it appropriately.

This worked fine, when the project had a version number of 0.0.1-SNAPSHOT. However, when I decided to (manually) release this, by setting the version to 0.0.1, and run my Jenkins builds... the deployment behaviour was different to what I'd seen when it was a SNAPSHOT.

Each platform-specific deployment created its own staging repository in the OSSRH Snapshots repo.

After reading https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin, I have tried a variety of these settings, but nothing seems to work:

I am using Maven in order to automatically download a dependency, set up (and start) the JBoss server and deploy that downloaded dependency there. I created a pom.xml, which uses several Maven-Plugins. For JBoss-related interactions I am using the wildfly-maven.plugin (currently version 2.0.1.Final).

Since I am not building an artifact, but rather downloading it, I am not really producing a JAR (or any archived artifact).

The problem I currently have is: the wildfly-maven-plugin does not seem to do anything if packaging is set to pom.

As a workaround I currently set the project packaging to JAR and added the following to prevent the project JAR from building:

I install hadoop by brew install hadoop and then use pip install pyarrow as the client

The app i am trying to build with Jenkins can't seem to build correctly because plugins/dependencies are missing. I am using JFrog Artifactory in my pipeline and i believe that's what causing this problem. Whenever i use mvn clean install it seems to download all dependencies but when I use Jenkins to build the project it generates the following error: