Hi Ghislain,<br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote"><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">When
using Eclipse EGit and importing the project in eclipse, I am not quite
sure that M2E plugin is actually used to load the project.</span></p></blockquote><div><br>If you use the "Import Existing Maven Projects" or "Check out Maven Projects from SCM" import source, it will use M2E by default.<br>
<br></div><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote"><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">However, once
the project is imported in Eclipse using EGit plugin, I was able to run
the “Maven >Enable Dependency Management” after a right click on the
folder which seem to run properly.</span></p></blockquote><p class="MsoNormal"><br></p><p class="MsoNormal">I have not tried doing things that way, but it makes sense.<br></p><p class="MsoNormal"><br>
</p><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote"><span style="font-size:11.0pt;color:#1F497D">Everything
seem to have been configured correctly, except for the fact that the
projects are not flagged as team projects and also I did not seem to see
that: “it automatically switches between Project and Library (JAR)
build path entries when dependent projects are opened and closed”,
although perhaps something is perhaps not configured perfectly on my
end.</span><span style="font-size:11.0pt;color:#1F497D"></span><br></blockquote><br>Perhaps if you import the projects as Maven in the first place, it will work. You will know M2E is managing your dependencies if you have a "Maven dependencies" node in the project tree in the Package Explorer.<br>
<br>Also, with the current state of affairs, you have to be very careful to avoid the .classpath and .project files (which were generated by M2E) being overwritten by the copies from the Git repository. If Git is allowed to touch them, Eclipse and M2E will subsequently get very confused. This is why I proposed removing them from the repository in my initial email.<br>
<br>Regards,<br>Curtis<br><br><div class="gmail_quote">On Wed, Aug 10, 2011 at 1:26 PM, Ghislain Bonamy <span dir="ltr"><<a href="mailto:GBonamy@gnf.org">GBonamy@gnf.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal"><a name="131b4f21162b16f6__MailEndCompose"><span style="font-size:11.0pt;color:#1F497D">Hi Curtis,<u></u><u></u></span></a></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">This email was sent a little while ago and I am only getting around responding.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">When using Eclipse EGit and importing the project in eclipse, I am not quite sure that M2E plugin is actually used to load the project. However, once the project is imported in Eclipse using EGit plugin, I was able to run the “Maven >Enable Dependency Management” after a right click on the folder which seem to run properly.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Everything seem to have been configured correctly, except for the fact that the projects are not flagged as team projects and also I did not seem to see that: “it automatically switches between Project and Library (JAR) build path entries when dependent projects are opened and closed”, although perhaps something is perhaps not configured perfectly on my end.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Best,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Ghislain Bonamy, PhD<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">__________________________________________<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Research Investigator<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal">
<b><span style="font-size:11.0pt;color:#1F497D">G</span></b><span style="font-size:11.0pt;color:#1F497D">enomic Institute of the<u></u><u></u></span></p><p class="MsoNormal"><b><span style="font-size:11.0pt;color:#1F497D">N</span></b><span style="font-size:11.0pt;color:#1F497D">ovartis Research<u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;color:#1F497D">F</span></b><span style="font-size:11.0pt;color:#1F497D">oundation<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Department of Informatics, room C117<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">10675 John Jay Hopkins Drive<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">San Diego CA 92121<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">USA<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><a href="tel:%2B1%20%28858%29%20812-1534" value="+18588121534" target="_blank">+1 (858) 812-1534</a> (Work & Fax)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><a href="tel:%2B1%20%28757%29%20941-4194" value="+17579414194" target="_blank">+1 (757) 941-4194</a> (Home)<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><a href="tel:%2B1%20%28858%29%20354-7388" value="+18583547388" target="_blank">+1 (858) 354-7388</a> (Cell)<u></u><u></u></span></p>
<p class="MsoNormal"><a href="http://www.gnf.org" target="_blank"><span style="font-size:11.0pt">www.gnf.org</span></a><span style="font-size:11.0pt;color:#1F497D"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> <a href="mailto:ome-devel-bounces@lists.openmicroscopy.org.uk" target="_blank">ome-devel-bounces@lists.openmicroscopy.org.uk</a> [mailto:<a href="mailto:ome-devel-bounces@lists.openmicroscopy.org.uk" target="_blank">ome-devel-bounces@lists.openmicroscopy.org.uk</a>] <b>On Behalf Of </b>Curtis Rueden<br>
<b>Sent:</b> Tuesday, May 31, 2011 11:55 PM<br><b>To:</b> OME-devel mailing list<br><b>Subject:</b> [ome-devel] Eclipse metadata in bio-formats.git<u></u><u></u></span></p><div><div></div><div class="h5"><p class="MsoNormal">
<u></u> <u></u></p><p class="MsoNormal">Hi everyone,<br><br>This is a question for those who use Eclipse to develop Bio-Formats code.<br><br>Recently, I added pom.xml files to the Bio-Formats source tree, so that Maven can function as a parallel build system. This has the nice side effect that it is very easy to import those projects into Eclipse, using the m2eclipse plugin. This plugin takes care of generating Eclipse metadata files (.classpath, .project, and .settings/*) to match the POM's metadata, and keeps it up to date as project dependencies change. In particular, it automatically switches between Project and Library (JAR) build path entries when dependent projects are opened and closed, which is a very nice feature.<br>
<br>Unfortunately, bio-formats.git already has Eclipse metadata committed to the repository. When using m2eclipse with Bio-Formats, these metadata files are overwritten, and Git sees a slew of changes in the working copy. While it is possible locally to instruct Git to ignore such changes (see <a href="http://www.pagebakers.nl/2009/01/29/git-ignoring-changes-in-tracked-files/" target="_blank">http://www.pagebakers.nl/2009/01/29/git-ignoring-changes-in-tracked-files/</a>), my preference would be to remove the Eclipse metadata files from Git altogether, and suggest that people use the m2eclipse plugin to develop Bio-Formats from within Eclipse. This solution has the added benefit that we no longer need to keep our dependencies in sync between the Ant build.properties files, the Maven pom.xml files, and the Eclipse .classpath files, but rather only between Ant and Maven.<br>
<br>What do you think?<br><br>Thanks,<br>Curtis<u></u><u></u></p></div></div></div></div></blockquote></div><br>