1. Create a simple blueprint. In the atlassian-plugin.xml set the blueprint name to "name1" like so:

<blueprint key="my-blueprint" content-template-key="simplebp-template" index-key="my-index" name="name1"/>

Observe that the attribute used is "name", which is not documented here: https://developer.atlassian.com/display/CONFDEV/Blueprint+Module

2. Upload your plugin
3. In Confluence click "Create" and verify your new blueprint is there
4. Go to Space Tools > Content Tools
5. Observe your blueprint is listed as "name1"
6. In atlassian-plugin.xml change the name of the blueprint to "name2"
7. Rebuild your plugin and upload it
8. Go to Go to Space Tools > Content Tools and observe your blueprint is still listed as "name1"
9. Go to Confluence Admin > Add-ons and view the modules for your plugin
10. Observe that here the module is labeled as "name2"

Workaround:

The name property of plugins and their modules are stored in the ao_54c900_content_blueprint_ao table of the database. They can be changed with an update statement. Please shutdown your instance before running this query:

update ao_54c900_content_blueprint_ao set name = '<new_name>' where plugin_module_key = '<your_module_key>';