<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 09/14/2009 12:05 PM, Damien Bouvarel wrote:
<blockquote
cite="mid:72655fe30909140305l1aa1c3b9hca46ce06c5318616@mail.gmail.com"
type="cite">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 moz-do-not-send="true"
href="http://install_lisaac.li">install_lisaac.li</a>. Maybe the
plugin should be in an extra lisaac package?<br>
</blockquote>
Hi,<br>
<br>
Doesn't eclipse generate an ant file to compile the project using ant ?<br>
I think that would be the best solution.<br>
<br>
About including .class files or .jar files in the git repository, I
don't really like this idea since it means there would be another big
binary file in the repository, and that would make it even larger. We
have enough of lisaac.c I think.<br>
<br>
But of course, if we make a release, we would provide the jar file.<br>
<br>
Mildred.<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Mildred Ki'Lya
╭───────── ｍｉｌｄｒｅｄ５９３＠ｏｎｌｉｎｅ．ｆｒ ──────────
│ Jabber, GoogleTalk: <a class="moz-txt-link-rfc2396E" href="mailto:mildred@jabber.fr"><mildred@jabber.fr></a>
│ Website: <a class="moz-txt-link-rfc2396E" href="http://ki.lya.online.fr"><http://ki.lya.online.fr></a> GPG ID: 9A7D 2E2B
│ Fingerprint: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 9A7D 2E2B
</pre>
</body>
</html>