Esug java
0 likes244 views
The document discusses various topics around software development including JMX, OSGi, Maven, and build systems. It notes that Maven provides standardized ways to define projects including dependencies, licenses, and contributors. Maven can also generate reports on code quality and test coverage. The document advocates using object-oriented approaches like prototypes rather than scripting for builds.
1 of 29
Download to read offline
Esug java
- 2. ESUG 2009
- 3. Dude, it would be so simple to build something better than this. DO IT!
- 4. JMX
- 5. I don’t need it
- 6. I just use a workspace
- 7. I write my own
- 8. offers •query values •perform operations •receive notifications
- 9. 2 APIs •inside the image to expose •outside the image to consume
- 10. Demo
- 11. OSGi
- 12. features are bad they make stuff more complicated and bloated
- 13. features are good they get stuff done and sell your software
- 14. plugins are cool as long as they work together
- 15. module systems would help but nobody uses them
- 17. Users •Eclipse RCP •GlassFish v3 •“smaller ones”, e.g. Sling
- 18. Maven 2
- 19. We don’t need build systems in Smallalk! Have you ever tried to release more than a dozen Seaside subprojects on SqueakMap and Universes?
- 20. make an object of your project don’t script
- 21. POM •Single inheritance for common stuff between similar projects •like a prototype
- 22. License Developers InceptionYear Mailing Lists SCM Issue Tracker Homepage Continuous Integration Dependencies Version Contributors “Modules”
- 24. Dependencies • transitive • optional • only for tests • only for development • only for deployment
- 26. • validate • initialize • generate-sources • process-sources • generate-resources • process-resources • compile • process-classes • generate-test-sources • process-test-sources • generate-test-resources • process-test-resources • test-compile • test • package • pre-integration-test • integration-test • post-integration • verify • install • deploy
- 28. Reports, Reports, Reports • Code coverage • Code analysis (SLint3) • Duplication • l10n • API compatibility
- 29. flame on!