Consider deleting corb.jar from deploy/lib/java when upgrading Roxy

[sashamitrovich]

RFE Template

The RFE

Short description of the problem:
Upgraded Roxy from an older version that was still including Corb (1). My objective was to use Corb2 with Roxy. Noticed that corb.jar still remains in deploy/lib/java along the corb2 jar. Roxy keeps defaulting to Corb (1) in this situation.

Your business use case. How much time would this save you? Can you currently work around this missing feature?

Lost some time figuring out what's happening. The problem can be solved if you manually remove the deploy/lib/java/corb.jar file.

Timeframe : How urgently do you feel you need this RFE addressed? Why?
It's one of those little things - not urgent since there's a simple workaround (manual delete) but might save time for the next Roxy user who stumbles upon this problem.

[grtjn]

The issue is broader actually. You might end up with multiple ML xcc, and xml stream jars. Also, we flushed ml4/5/6 test configs, which are not removed either..

[heelix]

When this came up last time, we were one of the teams that was tapping corb. We've since updated to corb2.