jdaugherty opened a new pull request, #14324:
URL: https://github.com/apache/grails-core/pull/14324

   Per the decision[1], this merges the grails-geb repository into grails-core.
   
   Please note that after having these repositories fully merged, clean up was 
done, including: 
   1. significantly changing the build to make tasks lazy
   2. spinning up mongodb containers instead of relying on a local instance
   3. removing isolatedTest helper - it was configuring a secondary test task 
which meant the tests ran twice
   4. reviewing uses of @Ignore and fixing tests that were never updated since 
the groovy 4 introduction
   5. generating the grails-bom in the documentation from the dependencies (See 
ExtractDependenciesTask)
   6. fixing rate limiting of the grails-geb images by specifying an image pull 
policy to wait at least a day before pulling agian
   7. unifying the parallel approach across all repositories
   8. making several tasks cacheable (FindMainClass, Views Tasks, GSP Tasks)
   9. renames the GSP forked compiler to remove the word "task" since it's not 
a gradle task
   10. Add options to skip various tests
   11. Updates old ticket references to the apache tickets
   12. Updates various build files to remove gradle deprecations 
   13. Fixes the groovydoc so that external libraries are resolvable
   14. Prevents adding external classes to the classpath of groovydoc - so 
they're not documented
   15. Ensures ast / java / groovy sources are used for groovydoc
   16. Fixes the selenium version by including it in grails-bom
   17. removes .web from grails-web-boot package per previous discussion on 
grails-forge PR
   18. adds @Ignore on tests that seem to fail only on windows 
   19. exclude tests from groovydoc
   
   
   [1] https://lists.apache.org/thread/7trbthyv31tp2pkwpr3swn1pm80nd969
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to