<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi Curtis,<div><br></div><div>I updated maven and at least now it appears my plugin which depends on TrackMate 2.5 successfully gets included/built into the final app. I still get the warning about TrackMate 2.3 but at least it doesn't appear to be getting in the way of my TrackMate 2.5 dependent plugin (if it ever was).</div><div><br></div><div>Thus, not an "emergency" for any of your assistance that you graciously offered, but this brings up a question... How does maven deal with reciprocally dependent jar's such as TrackMate and Fiji where the plugin depends on Fiji while it also seems that Fiji depends on the plugin. Is this all fine and dandy for maven in general or is it typically managed via "scope"? I didn't notice any specification for "scope" with respect to the TrackMate dependency. Can scope be specified elsewhere as a property of group of dependencies?</div><div><br></div><div>Cheers and thanks,</div><div><br></div><div>Jay</div><div><br></div><div><div><div>On Sep 14, 2014, at 8:11 AM, Curtis Rueden <<a href="mailto:ctrueden@wisc.edu">ctrueden@wisc.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr">If you still haven't solved in by tomorrow, I'll take a look when I'm in front of a computer tomorrow then.</p>
<div class="gmail_quote">On Sep 14, 2014 8:10 AM, "Jay Warrick" <<a href="mailto:jay.w.warrick@gmail.com">jay.w.warrick@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">I already mentioned that I did that. You pointed it out to me before and it has been extremely useful since then. However, in this case, it is showing that there are no TrackMate 2.3 dependencies yet when running maven from command line, I get an issue when, for some reason, it tries to pull it in.<div><br></div><div>Thanks,</div><div><br></div><div>Jay</div><div><br><div><div>On Sep 14, 2014, at 8:07 AM, Curtis Rueden <<a href="mailto:ctrueden@wisc.edu" target="_blank">ctrueden@wisc.edu</a>> wrote:</div><br><blockquote type="cite"><p dir="ltr">Hi Jay,</p><p dir="ltr">Eclipse has tools to understand where deps are coming from. Double click the pom.xml and see the Dependency Hierarchy tab. Much faster than guesswork and experimentation.</p><p dir="ltr">-Curtis</p>
<div class="gmail_quote">On Sep 14, 2014 6:52 AM, "Jay Warrick" <<a href="mailto:jay.w.warrick@gmail.com" target="_blank">jay.w.warrick@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Ok. So this makes more sense... TrackMate v 2.3 uses the <groupId>${jama.groupId}</groupId> which causes the error, which was fixed by TrackMate v2.5 which uses <groupId>gov.nist.math</groupId>.<div><br></div><div>So the whole issue boils down to, "Why is maven trying to do ANYTHING with v 2.3 when I can't find a single dependency on this version? If I can get Maven to stop looking for v 2.3 my issue will be solved.</div><div><br></div><div>Thoughts on where to search for hidden/residual links to v 2.3 given what I've checked already?</div><div><br></div><div>Thanks,</div><div><br></div><div>Jay</div><div><br></div><div><div><div>On Sep 14, 2014, at 6:45 AM, Jay Warrick <<a href="mailto:jay.w.warrick@gmail.com" target="_blank">jay.w.warrick@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div style="word-wrap:break-word">I think never mind. Still learning about Maven, but it looks like the groupID is assumed the same as the parent so you TrackMate doesn't need to define it. Should have guessed this based on how everything else seems to work in Maven.<div><br></div><div><div><div>On Sep 14, 2014, at 6:15 AM, Jay Warrick <<a href="mailto:jay.w.warrick@gmail.com" target="_blank">jay.w.warrick@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div style="word-wrap:break-word">If this might be on the right track, is there any way to test this on my end? Use offline mode and go into my .m2 repository and muck with poms or something?<br><div><div>On Sep 14, 2014, at 6:11 AM, Jay Warrick <<a href="mailto:jay.w.warrick@gmail.com" target="_blank">jay.w.warrick@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div style="word-wrap:break-word">Hi JY,<div><br></div><div>Could it be a problem with the TrackMate groupId? Searching the internet with the error string brought up this past issue with jama and SPIM...</div><div><br></div><div><a href="https://groups.google.com/forum/#!topic/fiji-devel/zEhBIf1bZEA" target="_blank">https://groups.google.com/forum/#!topic/fiji-devel/zEhBIf1bZEA</a></div><div><br></div><div>When I look at the TrackMate pom, I don't think I see a "groupId" defined for the TrackMate plugin. Hard for me to completely decipher in the issue discussion if this would cause the problem I'm seeing or if it would merely prevent the imageJ/Fiji folks from "seeing" that such a problem exists.</div><div><br></div><div>Stephan Preibisch, Curtis, and Dscho - Does that sound like the right track? Thoughts?</div><div><br></div><div>Thanks,</div><div><br></div><div>Jay</div><div><br><div><div>On Sep 13, 2014, at 9:20 AM, Jean-Yves Tinevez <<a href="mailto:tinevez@pasteur.fr" target="_blank">tinevez@pasteur.fr</a>> wrote:</div><br><blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000">
<div>On 13-Sep-14 16:01, Jay Warrick wrote:<br>
</div>
<blockquote type="cite">
Hi Jean-Yves,
<div><br>
</div>
<div>Thanks for the quick reply! Here are the poms for my multi
module project. I added to the default "pom.xml" names to make
things easier to follow. The Master pom is the parent pom for
each of my project modules. The parent of Master is scijava. The
JEX module has essentially one class, Main which calls the main
class in Core. Core contains essentially the whole program
including the dependency on TrackMate. Broken contains broken
code for one reason or another but doesn't really come into play
as the Broken module is not part of the build process. It is
"disabled" using a profile within the JEX module. Despite this,
I still confirmed it didn't depend on TrackMate 2.3 using the
Eclipse dependency hierarchy viewer, just in case.</div>
</blockquote>
<br>
Ok thank you for the crystal clear report. <br>
We are on the verge of what I know of maven. However I remember
having a similar issue that was fixed by making the parent of the
master pom the fiji plugin pom, like for TrackMate pom.<br>
<br>
Any chance you could just try that first?<br>
jy<br>
<br><br>
<hr style="border:none;color:#909090;background-color:#b0b0b0;min-height:1px;width:99%">
<table style="border-collapse:collapse;border:none">
<tbody><tr>
<td style="border:none;padding:0px 15px 0px 8px">
<a href="http://www.avast.com/" target="_blank">
<img border="0" src="http://static.avast.com/emails/avast-mail-stamp.png">
</a>
</td>
<td><p style="color:#3d4d5a;font-family:"Calibri","Verdana","Arial","Helvetica";font-size:12pt">
This email is free from viruses and malware because <a href="http://www.avast.com/" target="_blank">avast! Antivirus</a> protection is active.
</p>
</td>
</tr>
</tbody></table>
<br>
</div>
_______________________________________________<br>ImageJ-devel mailing list<br><a href="mailto:ImageJ-devel@imagej.net" target="_blank">ImageJ-devel@imagej.net</a><br><a href="http://imagej.net/mailman/listinfo/imagej-devel" target="_blank">http://imagej.net/mailman/listinfo/imagej-devel</a><br></blockquote></div><br></div></div>_______________________________________________<br>ImageJ-devel mailing list<br><a href="mailto:ImageJ-devel@imagej.net" target="_blank">ImageJ-devel@imagej.net</a><br><a href="http://imagej.net/mailman/listinfo/imagej-devel" target="_blank">http://imagej.net/mailman/listinfo/imagej-devel</a><br></blockquote></div><br></div>_______________________________________________<br>ImageJ-devel mailing list<br><a href="mailto:ImageJ-devel@imagej.net" target="_blank">ImageJ-devel@imagej.net</a><br><a href="http://imagej.net/mailman/listinfo/imagej-devel" target="_blank">http://imagej.net/mailman/listinfo/imagej-devel</a><br></blockquote></div><br></div></div>_______________________________________________<br>ImageJ-devel mailing list<br><a href="mailto:ImageJ-devel@imagej.net" target="_blank">ImageJ-devel@imagej.net</a><br><a href="http://imagej.net/mailman/listinfo/imagej-devel" target="_blank">http://imagej.net/mailman/listinfo/imagej-devel</a><br></blockquote></div><br></div></div><br>_______________________________________________<br>
ImageJ-devel mailing list<br>
<a href="mailto:ImageJ-devel@imagej.net" target="_blank">ImageJ-devel@imagej.net</a><br>
<a href="http://imagej.net/mailman/listinfo/imagej-devel" target="_blank">http://imagej.net/mailman/listinfo/imagej-devel</a><br>
<br></blockquote></div>
_______________________________________________<br>ImageJ-devel mailing list<br><a href="mailto:ImageJ-devel@imagej.net" target="_blank">ImageJ-devel@imagej.net</a><br><a href="http://imagej.net/mailman/listinfo/imagej-devel" target="_blank">http://imagej.net/mailman/listinfo/imagej-devel</a><br></blockquote></div><br></div></div></blockquote></div>
</blockquote></div><br></div></body></html>