Java Enterprise Edition Projects
I have successfully connected to a Team Concert Server from RAD 7.5 Beta. I am attempting to define processes for many, small, teams that are creating Java Enterprise Edition applications. Here are a few questions:
- Team A creates an EJB with an EJB Client .jar file. Team B would like to reuse Team A's EJB Client .jar file in binary form. How to accomplish this with Jazz? This seems to be a use case for a broader discussion on .jar file repositories and versioning of binary artifacts? - Team A owns a Java Enterprise Edition application (.ear file). How to define a build that builds all projects that constitute the .ear file (.war file, EJB .jar file). - How to apply a common process to all Java Enterprise Edition applications (all Java source must be unit tested with some %age of code coverage and pass static analysis from a set of common rules). This seems to be a use case for a broader discussion on governance across many teams and projects? - The sample provided in Team Concert is basically a single Java project/application with zero dependencies. I cannot think of an Enterprise effort that doesn't have one or more project dependencies on other teams' projects nor isn't packaged as an .ear file. Would appreciate a JEE sample? Thanks in advance, -Naresh Sikha |
One answer
I might be able to help a little.
nsikha wrote: I have successfully connected to a Team Concert Server from RAD 7.5 I have run into this a few times recently with clients. The best solution for consuming 3rd party binaries (from inside or outside your company) is to create a stream to contain the 3rd party binaries. You would update the binaries as needed to new versions. In this case Team B would have a stream where they would periodically update to a new version of Team A's jar. Another possibility I have discussed but not seen implemented yet is to have Team A to own the 3rd party binary stream (their own output) for use by other teams in the same company. They could use the Jazz SCM command line from their build (probably only selected builds, not all of them) to push new versions to the stream.
I think you would build it the same way you do today. I am making an assumption that you already have a build for the work you have done in RAD in the past. The change would be to add usage of the Jazz Build Toolkit ANT tasks to your build scripts to get the source from the Jazz repository and publish results back. Perhaps someone from the RAD development team can add more insight here.
You might want to take a look at the Code Coverage and Static Analysis incubators available on jazz.net. Also, if you have some testing already integrated into your build, you should be able to report those results back as discussed above.
Thanks, Steve Wasleski Jazz Jumpstart |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.