build eclipse mode

[Nicolas Boulay]

Is it cleaner to put the file to compile the plugin though eclipse and to
provide binaries somewhere else.

Binaries should not be inside git. lisaac.c is there to resolve "chikens and
eggs" problems.

If you want absolutely the binaries in git, maybe you could juste create a
git repository for binaries that correspond to tagged version of the primary
git repository of the plugin.

Nicolas

2009/9/14 Damien Bouvarel <damien.bouvarel at gmail.com>

>
>
>  On 09/14/2009 12:05 PM, Damien Bouvarel wrote:
>>
>> Hello,
>> I try to make the eclipse plugin compilable from command-line for the
>> 'install_lisaac' program, (far not so easy..).
>> It's called an headless build, i didn't succeed to make it work
>> properly... (despite the UI compilation is one click...)
>>
>> 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).
>> 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 install_lisaac.li. Maybe the plugin should be in an
>> extra lisaac package?
>>
>> Hi,
>>
>> Doesn't eclipse generate an ant file to compile the project using ant ?
>> I think that would be the best solution.
>>
>>
> Yes, it's exactly what it does, but executing the ant file outside eclipse
> from command-line require lots of xml
> files to configure, and there is very few documentation for that.. I'll try
> to find examples.
>
> > Ok theorically, put binary in the git is bad. But it's nightmare to compile
> > it.
> > It's a nightmare to install ant, and etc...
>
> > And it will nightmare about configuration file problems
>
> Yes i agree, if you use your own eclipse to compile the plugin project, it
> will configure and compile it for you.
>
>
>>  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.
>>
>>
> The .jar is a bit more than 512k  :)
> I think it is good to put it for the release (most people won't compile it
> (who did it? :-) ).
>
>
>>  But of course, if we make a release, we would provide the jar file.
>>
>>
> I'll update the editor/eclipse git with the jar for now :) at release time
> we'll make up the packages properly.
> Damien
>
>
>>  Mildred.
>>
>>
>> --
>> Mildred Ki'Lya
>> ╭───────── ｍｉｌｄｒｅｄ５９３＠ｏｎｌｉｎｅ．ｆｒ ──────────
>> │ Jabber, GoogleTalk: <mildred at jabber.fr> <mildred at jabber.fr>
>> │ Website: <http://ki.lya.online.fr> <http://ki.lya.online.fr>           GPG ID: 9A7D 2E2B
>> │ Fingerprint: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 9A7D 2E2B
>>
>>
>> _______________________________________________
>> Lisaac-devel mailing list
>> Lisaac-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/mailman/listinfo/lisaac-devel
>>
>>
>
> _______________________________________________
> Lisaac-devel mailing list
> Lisaac-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/lisaac-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/lisaac-devel/attachments/20090914/5d58c12c/attachment.htm>