This content has been marked as final. Show 1 reply
That is an omission of which we are well-aware. There is no plan to treat it as an error or to fix it. The decision comes down to this question:
Would most users really prefer a fully or partially failed Connections import if existing connection names violate the new naming rules?In this case, the cure is worse than the disease. Most users are happy to ignore Logging pane messages if everything else seems to work. Over the course of the next couple of releases, this issue should be mostly self-correcting as user conform to the new rules and rename connections.
SQL Developer Team