Package.xml Generation

[jus...@dontpanic.consulting]

Does IlluminatedCloud support generating a Package.xml file from the metadata subscriptions? This would be very helpful if it does not. I could not find any reference to it in documentation.

Thanks!
Justin R. Donnaruma

[sc...@illuminatedcloud.com]

Justin, there's no specific feature to do so, but there are two ways that you can basically accomplish the same goal:

1. Change your subscription type to Package.xml, right-click on your src directory, and click Illuminated Cloud>Add to Metadata Subscription.  If no package.xml file exists, it'll create and populate one based on the contents of your src directory. If there's an existing package.xml it'll add entries based on the contents of your src directory though it won't remove anything that might already be in your package.xml.  Note that it only adds entries for top-level metadata types and not child metadata types, so you'll get entries for CustomObject but not CustomField, ValidationRule, etc.  Note that if the existing file contains wildcards, those will be respected; otherwise the entries will be blown out explicitly.  IC will not add a wildcard entry for you.
2. Perform a full project retrieve for merge and the directory diff will include the package.xml file that was used for the retrieval with any slight modifications made by the server.

I'd start with option #1 and see whether it gives you what you want, or at least a good starting point toward it.  Please let me know if you have any further questions or issues.

Regards,

Scott Wells

[Jeff May]

Hi Scott -

Using IC 2.0.5.2, I can't seem to get the package.xml to be created.

1) I have my IC project, retrieved from vcs, and the module is connected to a new dev org.

2) Deleted the package.xml from the project src directory

3) Changed the module subscription to package.xml (with no file specified)

4) On the src directory, selected IC/Add to Metadata Subscription

Nothing happens, no package.xml is created.

I'm sure I've done something stupid, but would appreciate any guidance.

[sc...@illuminatedcloud.com]

Jeff, if you're using a Package.xml metadata subscription, it must point at an existing package.xml, even if that package.xml is basically empty, i.e.:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<Package xmlns="http://soap.sforce.com/2006/04/metadata">

    <version>44.0</version>

</Package>

Then IC knows the file to populate when you use Add to Metadata Subscription.

Let me know if that doesn't resolve it for you.

Regards,

Scott

[Jeff May]

Worked like a charm. Knew it was something dumb.

Thanks as always for everything you do for all of us!