Hi Tobias, A workaround would be to define sezpoz.version to 1.9-imagej, a proper > solution would be to find out what is causing that dependency to be drawn > in and update it accordingly. >
I believe problem here is a leftover m2e profile hack<https://github.com/fiji/fiji/blob/master/pom.xml#L165>in pom-fiji. This causes the pom.xml to include a sezpoz dependency only in eclipse, at which point you got the observed failure that sezpoz.version is no longer defined. This effectively broke every project using pom-fiji in eclipse. Filed a PR <https://github.com/fiji/fiji/pull/65> with the fix. Since pom-fiji is purely snapshot based, as soon as the PR is merged, built and deployed, this issue should just go away. - Mark On Fri, Jan 17, 2014 at 9:46 AM, Curtis Rueden <ctrue...@wisc.edu> wrote: > Hi Tobias, Mark & everyone, > > > I like to use the dependency:tree plugin from the command line > > So do I, but I want to caution that I have had problems with it in Maven > 3.x. I have seen it produce obviously wrong results in some cases. Not sure > whether it is fixed with the latest versions of things, but be careful. I > have not noticed any errors in Eclipse's Dependency Hierarchy, but I have > also used it much less. > > Regards, > Curtis > > > On Fri, Jan 17, 2014 at 9:43 AM, Tobias Pietzsch <pietz...@mpi-cbg.de>wrote: > >> Hi Mark, >> >> thanks! I must be blind that I didn't notice the "Dependency Hierarchy" >> in Eclipse myself… Very cool. >> >> best regards, >> Tobias >> >> On Jan 17, 2014, at 4:08 PM, Mark Hiner <hin...@gmail.com> wrote: >> >> Hi Tobias, >> >> On Fri, Jan 17, 2014 at 8:32 AM, Tobias Pietzsch <pietz...@mpi-cbg.de>wrote: >> >>> Btw, can you recommend a good way to trace through the pom dependency >>> tree? >>> I used a combination of Eclipse's "Effective pom", grep-ing in >>> ~/.m2/repository, and pure luck… Are there better tools? >>> >> >> Personally, I like to use the >> dependency:tree<http://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html>plugin >> from the command line, and I prefer the "Dependency Hierarchy" in >> Eclipse (which is basically the same as dependency:tree, and perhaps easier >> to read). >> >> The Effective POM can be helpful, but I find it to be too much >> information when you're just trying to figure out dependencies. >> >> - Mark >> >> -- >> -- >> Please avoid top-posting, and please make sure to reply-to-all! >> >> Mailing list web interface: http://groups.google.com/group/fiji-devel >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Fiji-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to fiji-devel+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >
_______________________________________________ ImageJ-devel mailing list ImageJ-devel@imagej.net http://imagej.net/mailman/listinfo/imagej-devel
