Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace App Connect
Created by Guest
Created on May 7, 2024

maven support when building java projects with ibmint

Many customer are using Java within their integrations / flows. 
Beside the code the Java projects typically include resources like images, template files and others.  

When building with mqsicreatebar the customer has got the option to use "Maven mechanism" under the cover. 
(via builders and natures defined in the .project file). 
Based on this setup the resources are automatically package into the resulting jar file - when compiling the Java project. 

Based on the IBM strategy ibmint should become the new strategic cli tooling. 
However as of today ibmint does not support any "maven mechanism / handling". 
This means the customers need to re-org and adopt their complete build chain - as they now have to handle all resources files separately on their own. 

Thus it would be great if ibmint would also support such meachnism. 
This would allow many customers  to easily switch to the new cli tooling. 


Idea priority Urgent
  • Admin
    Ben Thompson
    May 10, 2024

    Idea Review. Thank you for taking the time to raise this enhancement idea. Under the covers, the implementation of the mqsicreatebar command is utilizing eclipse running in headless mode. This brings with mqsicreatebar a requirement to have Toolkit / Eclipse installed where the build script is executing, and so avoiding this pre-requisite was one of the main reasons for investing in other packaging options (mqsipackagebar and ibmint) which do not need Eclipse. The requirement mentions that when Maven invokes mqsicreatebar the builders and natures result in the Java dependencies being dragged into the jar / bar.

    We strongly suspect that this only works due to inheriting eclipse capabilities for grabbing the resources and building them in to the jar / bar. In order to get this same behaviour from ibmint, we would need to build capability into ibmint which has knowledge of eclipse builders and natures or alternatively options for Java building. It seems more maintainable for this to be done directly from your build tool or via your build tool calling into Maven to do this, rather than to do this indirectly through ibmint. Given this, on this occasion we will not be taking this suggestion forward right now.