Visualforce Error: Collection size 2,592 exceeds maximum size of 1,000

[alan-morey]

I'm getting Collection size 2,592 exceeds maximum size of 1,000 when trying to load the visualforce page. I've got about 500 Apex classes in my org and I've a number of managed packages installed including FinancialForce which puts me well over the 1000 size limit.

This affects v1.5 package.

I removed the package and manually deployed components from the Git repo and it seems the changes to ApexClassesSelector.selectAllVisible() in e4b842d fix my immediate problem, now that managed package classes are not included any more. However, I think the underlying problem may still arise in an org with more than 1000 visible Apex classes.

[ImJohnMDaniel]

@afawcett - There are two issues here:

1. the display of managed packaged classes in the list. This is related to Classes are not visible when running the tool in a packaging org #5 and Should ApexUML package classes show in the list? #7.
2. the error received where more than 1000 ApexClasses are found in the default namespace.

I propose we do the following:
A) split this ticket into 2 tickets. This ticket will be coupled with tickets #5 and #7 and be released on milestone 1.6. That solves @alan-morey's immediate issue.
B) setup a second enhancement ticket to deal with the 1000+ ApexClasses via SOQL Offset or some other mechanism and place this ticket into the #Backlog milestone as there is no immediate need for it.
C) Ticket #6 is pushed back to milestone 1.7 (or later) so that 1.6 can be released immediately.

Are you ok with this action?

[ImJohnMDaniel]

I have opened another ticket to deal with the issue where there are more than 1000 ApexClasses in the default namespace of the org. (See #12)

The other issue mentioned in this ticket about managed packaged classes included in the list has been resolved by issues #5 and #7.