A few thoughts on my part. First, there is a challenge when you use the same library name for both an internal and an external library. In that case, the IDE must choose the internal library that may be found first, but can also choose to choose an external library to override the internal library.
In addition, to display a help text in the IDE, the IDE uses the corresponding XML doctype file with the same file name with the extension xml. If you give the XML file a different name, you break that relationship. This argues for renaming the jar file and the associated XML Doctype file name to the same filename (NFC and NFCOld).
Finally, renaming a java source file in Eclipse also requires renaming the java class name to prevent an error.
Based on these thoughts, I advice to try the following:
- Choose the NFC as the file name for the most commonly used library (probably the new one because that is the way to go in the future).
- Rename the old NFC short name if it is NFC to NFCOld.
- Rename the library shortname to NFCOld.jar
- Rename the Doctype help file to NFCOld.xml.
- If necessary, adjust the text to reflect the difference between NFC and NFCOldin the NFCOld.xml file.
Note I use the term filename meaning without the jar or xml extension.