New Visualforce page not deployed to org until added to package.xml

[Tom Fuda]

My project has a package.xml file that explicitly specifies a bunch of Visualforce pages by name (it does NOT specify <members>*</members> for the ApexPage type). When use IlluminatedCloud's New -> Visualforce Page menu to create a new VF page, it creates an empty page and an associated page-meta.xml file. Then the following dialog appears: http://screencast.com/t/HemS4WufWuc. If I click "Yes", I expect the page to be deployed into my org, however, that is not happening. Note that I have not added this new page to the package.xml file yet. If I add the new file to my package.xml file, I can deploy it successfully.

[Scott Wells]

Thanks for filing. There's another enhancement request (#239) to update the package.xml file (and the subscription in general) when new metadata is created. I'm still on the fence as to whether I should be doing that, but I think if I prompt the user first, it's okay. That would also address this issue as long as I do the update before the post-creation deployment occurs.

I'm also going to be adding tooling API-based creation of Apex and Visualforce over the next few days which I believe will coincidentally address this as a side-effect of not using package.xml as a filter for deployment. As a result, I think you'll be getting a solution to this sooner than #239.

[Scott Wells]

I believe this should have been resolved some time back when I implemented automatic updates to the metadata subscription when metadata is added or removed locally. Please let me know if it's still happening to you.