This document discusses the Java development ecosystem. It describes common development tools like Jenkins, source control systems, Maven, Nexus, code analysis tools, and Sonar. These tools help with tasks like continuous integration, dependency management, code quality analysis, and monitoring project metrics over time. Sonar in particular collects results from analysis tools and provides visual dashboards to track metrics and summarize projects' test coverage, lines of code, and other indicators.

1. Java Development EcoSystem Andrey Khaisin, Ciklum Java User Group, June 2011

3. Project quality analyzing

4. UI, persistence, business logic development

5. Development for non Ukrainian BanksAnd always 20% of all activities are in development ecosystem www.ciklum.net 2

6. What is it all about?.. www.ciklum.net 3 “I can remember when the air was clean …” George Burns, comedian After some development

8. No JAR hell

9. Keep it stable

10. One click deploy

11. Look to the futurewww.ciklum.net 4

12. Part 1. Ecosystem components www.ciklum.net 5

13. Development tools www.ciklum.net 6

15. Distribute build process across a set of build servers

16. Build result statistic

17. Notification about build results

18. Executing post-build processes (e.g. deploying to testing server)Alternatives: Apache Continuum, JetBrainsTeamCity, Atlassian Bamboo, CruiseControl, Team Foundation Server, … thousands of them www.ciklum.net 7

20. Store all states of application code base

21. Know who and when made that change which crash the buildwww.ciklum.net 8

23. Standard project building life circle

24. Dependency management

25. Configuration and environment profiles

27. IDE custom build and dependencies managementwww.ciklum.net 9

29. Cache all dependencies from different remote repositories

30. Manage rules for main source of certain artifact

31. Control security side – no untrusted dependencies must be used for project build

33. Apache Archivawww.ciklum.net 10

35. PMD – static code analyzing

36. FindBugs – static code analyzing

37. Checkstyle – check code style ruleswww.ciklum.net 11

39. Track project metrics changes for a period of time

40. Visualizing project metrics

41. Flexible configurable dashboards for users with different project roleswww.ciklum.net 12

43. Analyze

44. Visualizewww.ciklum.net 13 Sonarize you project!

45. Part 2. Project metrics www.ciklum.net 14 Each metric is an answer to: How many tests? How big your code? What is code test coverage? How nice style of your code?

46. LOC and Test Coverage www.ciklum.net 15

47. Radar - Sonar www.ciklum.net 16 The rounder shape the better metrics

48. Thank you! www.ciklum.net 17 Andrey Khaisin kha@ciklum.net Ciklum