UPDATE: This is no longer an issue if the user increases his heap size in the eclipse ini file to say 1024, also if a user updates their class scanner to only look in the packages that have steps then they will never see this issue...
When any change is made to my Page Objects or Steps, as I am typing, the rebuild method runs on every character entered by the keyboard... Causing eclipse to crash...
Just typing getDriverProvider().get() brings eclipse to its knees...
See Images...
UPDATE: This is no longer an issue if the user increases his heap size in the eclipse ini file to say 1024, also if a user updates their class scanner to only look in the packages that have steps then they will never see this issue...
When any change is made to my Page Objects or Steps, as I am typing, the rebuild method runs on every character entered by the keyboard... Causing eclipse to crash...
Just typing getDriverProvider().get() brings eclipse to its knees...
See Images...