- edited description
Error deploying static resource when multiple static resource with same name, but different namespace exist
I'm developing a resource-bundle called "jquery.resource" in one of my Developer Edition orgs that also happens to have a couple of managed packages installed that also happen to have a Static Resource called "jquery", but obviously with different values of Namespace Prefix. When I make a change to one of the source files in my jquery.resource bundle Illuminated Cloud tries to deploy it, but I get the following error: http://screencast.com/t/Kx6foPWD6. When I query my org for Static Resources with Name = 'jquery', I get the following: http://screencast.com/t/LWD1uDGr. I think perhaps IC is having trouble resolving the Static Resource name properly in this case.
Here's a repro case for this issue:
- Install the following managed-beta package into a Developer Edition org or sandbox that you've connected to Illuminated Cloud: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t41000000479y. This package contains a single static resource called "test", with the namespace prefix "a_package1".
- In your org, upload a zip file as a new static resource, also called "test" (this won't have a namespace).
- Pull the metadata for this non-namespaced static resource into your Illuminated Cloud project and convert it into a static resource bundle. This should create a test.resource directory in the resource-bundles directory.
- Make a simple change to one of the files contained within the resource-bundles/test.resource folder and save it. This should cause IC to attempt to deploy the "test" resource into your org. You will see an error on the "Problems" dialog indicating the static resource name is already in use.
Comments (12)
-
Account Deactivated reporter -
Account Deactivated reporter - changed component to Deployment and Retrieval
-
repo owner Thanks for logging the additional issue and for the extensive details. I'll take a look this evening and let you know what I find.
-
repo owner Easily reproduced with the provided instructions. I appreciate the beta package you created to facilitate it. Hopefully I'll have a fix submitted in a few minutes that can be included in the next build (perhaps tomorrow morning).
-
repo owner Submitting a fix now.
-
Account Deactivated reporter - edited description
-
repo owner -
assigned issue to
- changed version to 1.7.4.5
-
assigned issue to
-
repo owner - changed status to resolved
Delivered in 1.7.4.5.
-
repo owner - attached IlluminatedCloud-14.zip
Test build that reverts the SOQL query change for all but static resources for now.
-
repo owner - changed status to open
Reopening for a better fix that's coming in 1.7.4.6.
-
repo owner - changed status to resolved
Improved fix delivered in 1.7.4.6.
-
repo owner - changed component to Metadata Deployment/Retrieval/Removal
- Log in to comment