I think putting the jar file is the better solution. It's too complicated to compile it, it requires too strict conditions to compile it.<br>And force anyone to compile it itself is to error prone : with eclipse you have mistake with JRE versions, eclipse versions, configuration settings, etc...<br>
By experience, it's too erreor prone. It isn't like C code or other with a makefile.<br>So put the jar file as we have C code. in the trunk ;)<br><br><div class="gmail_quote">2009/9/14 Damien Bouvarel <span dir="ltr"><<a href="mailto:damien.bouvarel@gmail.com">damien.bouvarel@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello,<br>I try to make the eclipse plugin compilable from command-line for the 'install_lisaac' program, (far not so easy..). <br>
It's called an headless build, i didn't succeed to make it work properly... (despite the UI compilation is one click...)<br>
<br>I had a solution where the .class files (in eclisaac/bin/) must be included in the git and also a part of the .metadata (workspace projects info).<br>But i think it's much easier to include only the plugin source and the exported .jar file, or only the sources and remove the command-line eclipse installation from the <a href="http://install_lisaac.li" target="_blank">install_lisaac.li</a>. Maybe the plugin should be in an extra lisaac package?<br>
<font color="#888888">
<br>Damien<br>
</font><br>_______________________________________________<br>
Lisaac-devel mailing list<br>
<a href="mailto:Lisaac-devel@lists.alioth.debian.org">Lisaac-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/lisaac-devel" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/lisaac-devel</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>---------------------<br>Isaac Project - <a href="http://isaacproject.u-strasbg.fr/">http://isaacproject.u-strasbg.fr/</a><br>