When having a large set of interacting applications that have to be deployed together on a "system" which in itself is build from different components (pc hardware and others), it was crucial for us to ensure that all these applications communicate (RMI with httpinvoker from spring) using the same version of the library (also a maven project) that represents the interfaces and "value types" used in the communication. I know that by consistently using serialVersionUIDs we could make this requirement of using the same interface library versions everywhere less strict, but this was not worth the effort in our situation.
The maven plugin I wrote was used to generate dependency diagrams of all our applications and the interfaces between them, such that when releasing one of the interface projects, we could easily see which other projects where impacted and had to be released (depending on a new interface version) as well. Having this diagram visualized, printed out and put on the whiteboard helped preventing mistakes in the release process (because if you forget to release a project, you might have to start all over again). Releasing in itself was done using the maven release plugin (which steps the version number in all the pom files of the project, tags it in our VCS and uploads to the maven repository). Jan On May 5, 1:14 pm, d...@happygiraffe.net (Dominic Mitchell) wrote: > On Mon, May 04, 2009 at 02:20:32AM -0700, jvb wrote: > > > I once wrote a maven plugin which represents the dependencies as a UML > > diagram, exported to <a href="http://en.wikipedia.org/wiki/ > > XML_Metadata_Interchange">XMI</a>. XMI was nice for me because I could > > then analyze the dependencies in UML tools that can read XMI (I used > > magic draw). > > > Don't know if this plugin still works with today's maven release > > though, haven't used it for a while now. > > >http://janvanbesien.blogspot.com/2008/04/maven-dependency-viewer.html > > Both m2eclipse and the NetBeans maven support can create graphs from > POMs. Frankly I don't find it all that useful. mvn dependency:tree > (and the m2eclipse "Dependency Hierarchy" view) seem more useful to me. > In that they've actually helped me to solve problems. :) > > -Dom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
