Hi everyone,<br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">imglib used to work without maven. So before writing code for imglib I<br>
have to learn how to use eclipse and before that, how to use maven?<br></blockquote>
<br>Regarding the issues with Eclipse and Maven, you do not need either of these tools, but they both make things much easier and are well worth the relatively minor time investment.<br><br>Stephan is correct that you do not need to use Maven at all. You could import each subproject as its own Eclipse project manually. File > Import > File System and then choose e.g. "imglib2/core" as the root folder. As Stephan says, you will then need to set src/main/java and src/test/java as source folders. Further, for projects with dependencies—e.g., imglib2-io depends on imglib2 and bio-formats—you would need to manually link up those dependencies, either as JAR files or Eclipse project dependencies.<br>
<br>I will emphasize that doing all of the above is a LOT more work than just installing the m2eclipse plugin and using "import existing Maven projects." If you do it the Maven way, it takes care of all the dependencies automatically. You can have any combination of projects open in Eclipse and they will work just fine.<br>
<br>There isn't really much to "learn" about Maven. If your project gets messed up somehow, you can reset it by right-clicking and choosing "Maven > Update Project Configuration" and then Project > Clean > Clean all projects. Those two steps will almost always fix puzzling issues.<br>
<br>The same goes for NetBeans and IDEA, which both also feature Maven support out of the box. We have directions on the ImageJDev web site (<a href="http://imagejdev.org/ides">http://imagejdev.org/ides</a>) for setting up Eclipse, NetBeans, IDEA, or the command line. They are tailored for ImageJ2 but the same concepts apply to ImgLib.<br>
<br>If you don't want to use an IDE, you can develop the code using Maven on the command line. If you don't want to use Maven either, you can do that too. Simply run the "mvn dependency:copy-dependencies" target one time, and you will notice a new folder "target/dependencies" containing all the dependent JARs. You can then set your CLASSPATH to point to all of those, as well as src/main/java, and hack away as usual in vim or Emacs or whatever. Of course, these JAR files will not be automatically updated as those projects evolve, and for inter-project dependencies within imglib (e.g., imglib-io depending on imglib) you may want your CLASSPATH pointing to multiple src/main/java folders, but it is all doable.<br>
<br>Please ask if you have any further questions or issues relating to the build system—I would be happy to help!<br><br>-Curtis<br><br><div class="gmail_quote">On Thu, Apr 21, 2011 at 8:10 AM, Stephan Saalfeld <span dir="ltr"><<a href="mailto:saalfeld@mpi-cbg.de">saalfeld@mpi-cbg.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Albert,<br>
<div class="im"><br>
> imglib used to work without maven. So before writing code for imglib I<br>
> have to learn how to use eclipse and before that, how to use maven?<br>
<br>
</div>No---but it makes life easier. You are free to import each project<br>
independently and care about the editor, builder/dependencies yourself<br>
like in any other project. E.g. imglib2-core has no dependencies which<br>
makes that extremely easy.<br>
<div class="im"><br>
> I imported the project by creating a new java project and telling it<br>
> to use the imglib folder.<br>
<br>
</div>You have to use the src/main/java folder and, if you like the<br>
src/test/java folder as well. Eclipse lets you add/edit/remove source<br>
folders later easily.<br>
<font color="#888888"><br>
Stephan<br>
</font><div><div></div><div class="h5"><br>
--<br>
You received this message because you are subscribed to the Google Groups "Fiji-devel" group.<br>
To post to this group, send email to <a href="mailto:fiji-devel@googlegroups.com">fiji-devel@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href="mailto:fiji-devel%2Bunsubscribe@googlegroups.com">fiji-devel+unsubscribe@googlegroups.com</a>.<br>
For more options, visit this group at <a href="http://groups.google.com/group/fiji-devel?hl=en" target="_blank">http://groups.google.com/group/fiji-devel?hl=en</a>.<br>
<br>
</div></div></blockquote></div><br>