Enhance and harmonize the Java development experience/process for message flows

#1 Our situation:

We are using Java ComputeNodes and thus Java to develop parts of our message flows. 
In this context we have the requirement to 
-    manage additional third party libraries 
-    manage additional resourcew within the Java projects (e.g. template files)

Today from our perspective the only way to achieve this is to 
-    use maven – for the dependency management of the third party libs and 
-    mqsicreatebar – to create the bar file

As mqsicreatebar is using Eclipse it will also take care about the maven dependencies if the right builders are set in the .project file. 
So far so good.

However: on our build pipelines we want and we need to avoid mqsicreatebar. 
Reason: it’s quite slow (because of the headless eclipse) and it’s more complex reg. the setup. 
Further we can not use mqsicreatebar at all – as we are not allowed to install additional tooling like xvfb on our build server 
Instead: we would like to use light weight tooling like ibmint (which is by the way promoted as new strategic CLI tool) 
However here we see two things: 
1) ibmint does not support Maven at all 
2.) ibmint does not provide any resource packaging for Java project.

#2 Our request / Idea: 
Well the maven support is of course “special” –  but at least it would be great if all ibm build/packaging tooling would behave the same way about additional resource files. 
Further: 
- what would be your recommend end-to-end development process for message flows including Java projects? Is there anything we have overseen?
 

Looking forward to your feedback. Thanks.