http://mojo.codehaus.org/animal-sniffer-maven-plugin/
This is supposed to be able to build signatures of APIs and check your project against them. I have not used it myself. -- Erlend On Thu, Feb 18, 2010 at 5:39 PM, Luis Miranda <[email protected]> wrote: > Hi Fabrizio, > > You could try Clirr, which has a Maven plugin > http://mojo.codehaus.org/clirr-maven-plugin/usage.html. I don't have > any experience with it myself. > > On Feb 18, 1:12 pm, Fabrizio Giudici <[email protected]> > wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On 2/18/10 13:43 , Wildam Martin wrote:> On Thu, Feb 18, 2010 at 13:28, > Fabrizio Giudici > > > <[email protected]> wrote: > > >> But the point is that now I'd like to extend API compatibiltity > > >> checks to a large number of my projects, and before escalating > > >> I'd like to check whether there are other tools for the same job, > > >> just to have a better awareness. > > > > > Since on Java I read more about such compatibility issues. While > > > on Windows development the COM components could be compiled with > > > binary compatibility basically meaning that compiler threw an error > > > if public interfaces were changed. > > > > Well, basically the sigtest tool, properly called by a build script, > > flags you the error. I mean, it's not the compiler to warn you, but > > another piece of the software factory, but the result is the same. > > > > > I think, if refactoring wouldn't be so easy (thanks to the > > > powerful IDEs) and people would think more first before designing > > > and changing APIs, that would not be such an issue. > > > > It's not that IDEs provide refactoring so we do refactoring; it's that > > people discovered that continuous refactoring gives many advantages, > > thus IDEs provide it. So, the problem is to be investigated in the > > process, but the process hasn't been invented by chance: it's a > > consequence of continuously evolving requirements. I wouldn't step > > back. Of course, there are the best practices for keeping an API > > backward compatible, but the point is that you might always make a > > minor mistake, and you still need a tool to check the stuff. > > > > - -- > > Fabrizio Giudici - Java Architect, Project Manager > > Tidalwave s.a.s. - "We make Java work. Everywhere." > > java.net/blog/fabriziogiudici -www.tidalwave.it/people > > [email protected] > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG/MacGPG2 v2.0.14 (Darwin) > > Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/ > > > > iEYEARECAAYFAkt9PMgACgkQeDweFqgUGxfy/gCfX7TymIizmizjoXwbRreU4R63 > > BvoAn2KmwvHbQ7EKm2csFowz4lfmmjDU > > =/buc > > -----END PGP SIGNATURE----- > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<javaposse%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
