mavenize | A tool which will attempt to mavenise ' any number | Object-Relational Mapping library

I am getting below error when I try to access a page in my application.

I have an issue with m2e plugin for cyclic dependent projects.

First of all, I know that circular dependencies are bad , maven also does not permit it, they should be avoided and etc. but our legacy projects were mavenized without project structure change (circular dependencies were continued).

Previously, adding each project to other projects build path and setting circular dependencies build path problem to warning was the workaround solution. That way, I could make changes in one project and see the effect in the other immediately.

Now that projects are mavenized, I want to achieve the same workspace environment by enabling m2e workspace resolution (by checking "Resolve dependencies from workspace projects" option).

In eclipse neon (Version: Neon.3 Release (4.6.3) Build id: 20170314-1500) with m2e version 1.7.0.20160603-1933 this is possible. Corresponding maven dependency is resolved from workspace project although there is cycle in build path.

However, in eclipse 2019-09 R (Version: 2019-09 R (4.13.0) Build id: 20190917-1200 with m2e version 1.13.0.20190716-1624) and later releases, build results in infinite loop. For two cyclic projects MY PROJECT A and MY PROJECT B with maven artifact ids MYPROJECTAARTIFACTID, MYPROJECTBARTIFACTID respectively, below is the m2e log for infinite build from 2019-09 R version (I could not gather logs from neon version).

To repeat, I know that maven itself does not allow cyclic project setup but in general eclipse does allow it even for projects with maven nature.

How can I achieve the same in latest eclipse releases?

I know this can sound very noobish and I apologize for that.

My question is simple :

I developed a project locally, it contains many external dependencies that are referred to in the pom.xml file. When I deploy on the remote server using mvn deploy, only the application jar is deployed, but not its dependencies.

So I end-up with java.lang.NoClassDefFoundError when I try to execute my program on the remote server.

What do I need to do to make this work in a proper way ?

EDIT : I would rather avoid ending up with a massive sumo jar with all dependences in it. I would prefer to export the dependencies separately to the remote server (if that makes sense)

EDIT 2: Is there a way to "Mavenize" the remote server and execute Maven Dependency lookup directly from there ? And only deploy my "real" jar when I update the code ?

I will have a look at the maven-dependency-plugin with the dependency:copy-dependencies mojo. Looks interesting.

Below my pom.xml : jar-with-dependencies did not work (I must have missed something)

I am trying to mavenize an existing project. I was able to build the EAR file(since i have to deploy in Websphere), When I try to deploy, using admin console - Able to install successfully , But application is not working, After investigating, I found the class files size is very less compare to the reference EAR file(old existing EAR file)

Steps I followed to build the EAR file

1. M2E plugin installed
2. Configure to Maven
3. Add ALL the jar files from lib folder like below(I read in SO, this is not the recommended way, but to complete the project, I have to do this)

I am trying to build an EAR file - Which can be deployed in IBM websphere server. This is an existing struts appliation, i am trying to mavenize it. This project contains two folders

I'm using fabric8 maven plugin in order to deploy my spring boot services on kubernetes.

Nevertheless, I'd like to deploy other kind of services, like postgresql, hashicorp vault, so on so forth.

So I've my configmap.yaml, deploymentconfig.yaml, service.yaml and route.yaml in order to deploy hashicorp vault, so they are not maven projects.

I think that's not mandatory to mavenize this kind of "projects" in order to be able to deploy them on kubernetes or openshift.

Is there any way to use fabric8 as cli or another idea in order to avoud to mavenize this kind of projects?

I expect I've explained so well.

We have a CICD process in place with defined set of TCs executed always for gating process. Sometimes its not needed to run all tests, instead we would like to trigger only set of TCs based on change made by developers. Our tests are cucumber based User Stories and hence we can control the test run by Tags. My idea is to parameterize cucumber.options from teamcity's maven command line parameters field and let Dev/support people define the tag as needed.

If i mention command line parameter as

I have a simple Mavenized Java Project with the expected directory structure an no "business" classes yet:

The pom.xml is rather mundane. It declares dependencies on JUnit4 and JUnit5, and the "surefire" plugin (enclosing project noise elided):

I had mavenize my project, trying to find the right way to handle DEV, Pre-Production and Production properties. I created a property named mule.env, and added context property like