Toolkit - Option to find all unused resources

Thank you for confirming that the intention of this RFE is related to the current Eclipse workspace and is not related to building artifacts into a BAR file, nor about identifying resources which you don't want to deploy. When voting and deciding on actions for this RFE we will limit ourselves to consideration of use case 1 ... ie Provide a way to identify that there exists an ESQL file in one of the projects in the current Eclipse workspace which is not being used by any of the message flows in the current Eclipse workspace. Of course for many users, this situation would not necessarily be a concern if they had a library of ESQL files, but in the current developers checked out artifacts they only had a handful of message flows, then in this situation there would be lots of "unused" ESQL files (from point of view of current workspace). If we were to prioritize this RFE then we would make display of this warning a non-default activateable preference. We will continue to monitor the RFE, but for now status is updated to Uncommitted Candidate.

The purpose of this RFE is to raise a warning in the IIB toolkit when there are unused ressources in the workspace. Please check use case 1) to understand what we need. Currently there is no way to detect if a ressource (especially an ESQL file) is unused. To detect this we had to develop a script to analyse all our message flows to check if there is a reference or not to an ESQL file. If not, we can consider this ESQL file has dead code and we can remove it.

RFE Review. RFE 63942 was closed as a duplicate of 70056 in June 2015, but a recent comment (Nov 2020) indicates that the initial raiser of 63942 feels it is unfair to couple these issues together. Reading the use cases presented on 70056, I agree that use case 1 implied searching for redundant resources in the Toolkit project prior to a BAR file being built ... but use case 2 does seem to be focussed on noticing when an unused artifact will be *deployed*. So, use case 2 of 70056 does appear very related because if we were to provide a BAR file build feature to display unused files this seems closely related to allowing removal of particular files from within an application when building it into a BAR. Given that the confusion lies with the two disparate use cases on 70056, and also given the recent active comment showing continued interest in 63942, we are re-opening 63942. This update will also be posted on 70056 which will be place in to Need More Info status pending feedback from the creator of 70056. 70056 will be reviewed again in 30 days time.

An update was posted to RFE 63942 - Allow Exclusions from Build Paths for IIB Application BAR files, linking it as a duplicate to this RFE.

The two RFE's are not the same.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB

For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB

Thank you for raising. For use case (1), grouping related artifacts in an application will ensure they are deployed and undeployed together, but this does not help in cases like (2) where a resource is in the application but "unused" at runtime. Typically, I'm not sure why you would want to deploy resources which are not used (perhaps that's your concern!), but I could conceive of occasions where this would possibly be desirable (eg a file which is used at buildtime only such as a .dbm, but which you wish to version and keep together in a BAR file for source control purposes). On this basis, warning the user in case (2) might be appropriate as a usability enhancement for the toolkit, so status of this RFE is updated to Uncommitted Candidate.