Hello Jordan, The reason you got the compilation errors in the first place was, because I've renamed the IImageMetadata and IImageMetadataItem to ImageMetadata and ImageMetadataItem (I dropped the "I" prefix). It seems that your project now references the latest snapshot which has this changes. But it also seems to depend on a compiled library which itself was compiled against the "old" version of imaging.
There are two ways to resolve this issue: 1. Revert the dependency to Commons Imaging in your project to a version before the renaming 2. Recompile the dependency which was compiled against the old version. Using the github repo is _not_ a good idea. The repo does not reflect the current development state. There seems to be a problem with the synchronization between the svn repo (where the main development takes place) and the git mirror [1]. So you should better take the code from https://svn.apache.org/repos/asf/commons/proper/imaging/trunk. In any case, it is never a good idea to depend on SNAPSHOT versions of library, because of this kind of problems. If you really need Commons Imaging, you should checkout the code and build and deploy it to your company's artifact repository with artificial maven coords so you don't run into trouble when Commons Imaging is finally released. HTH and thank you for your interest in Commons Imaging, Benedikt [1] https://issues.apache.org/jira/browse/INFRA-8949 -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter 2015-01-02 21:48 GMT+01:00 Black, Jordan <jbl...@scrippsnetworks.com>: > I pulled the latest from git (https://github.com/apache/commons-imaging), > built it, and that works. Is there a process or any plans to create a > process for determining when a snapshot gets deployed to the apache repo? > Or should I plan to build it locally and deploy to my local shared > repository only after I see that it didn't break my other builds? > > Thanks, > Jordan > > -----Original Message----- > From: Gary Gregory [mailto:garydgreg...@gmail.com] > Sent: Friday, January 02, 2015 1:41 PM > To: Commons Developers List > Subject: Re: [imaging] Snapshot versions > > commons-imaging-1.0-20141227.232306-24 cause compilation error > > I would use the latest code from SVN and built it locally to get the > latest and greatest. SNAPSHOTs might be published more or less randomly. > > Gary > > On Fri, Jan 2, 2015 at 12:25 PM, Black, Jordan <jbl...@scrippsnetworks.com > > > wrote: > > > Hello, > > > > My project's compilation is now failing after a new snapshot of > > commons-imaging was published. On December 28, it succeeded using > > http://repository.apache.org/snapshots/org/apache/commons/commons-imag > > ing/1.0-SNAPSHOT/commons-imaging-1.0-20141227.232306-24.jar > > and on December 29, it failed after no code changes using > > > > http://repository.apache.org/snapshots/org/apache/commons/commons-imag > > ing/1.0-SNAPSHOT/commons-imaging-1.0-20141229.162315-32.jar > > . > > > > Here's the error: > > The type > > org.apache.commons.imaging.common.IImageMetadata$IImageMetadataItem > > cannot be resolved. It is indirectly referenced from required .class > > files > > > > Any suggestions on how to resolve this? > > > > Thanks, > > Jordan > > > > > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence > with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in > Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
