[eclipse-maintainers] Initial project questions

[Jerry Haltom]

http://jack.feedbackplusinc.com/~jhaltom/ubuntu/warty

That is good enough for experimental as it is right now. I've been
working on it for a week or so. I need people to build and test it.

(you will need to change dist to unstable from warty)

On Fri, 2005-01-14 at 13:40 +0100, Joerg Wendland wrote:
>  - Do we need to maintain eclipse 2? There are still many commercial
>    tools based on it.

If you mean user plugins, sure. If not, I would really doubt any
commercial product "integrated" with the 2.1 packages Debian had before.

>  - Should we support packaged plugins? I think yes, but then how do we
>    handle plugins installed as Debian package? Should we disable their
>    updating through the update manager?

Sounds fine.

>  - Should we support multiple installed versions? One may want to have
>    both eclipse 3 and 3.1 installed.

I don't think we need to. I think we offer value to our users simply by
having the latest stable version "Just Work". We can put 3.1 in
experimental... or some combination there of.

>  - Should we build one big package or some small ones divided up by
>    functionality and usefulness as standalone packages: 
>    o swt (which is already packaged)
>    o rcp (which one may want to use for applications)
>    o pde
>    o jdt (tomcat5 can use the jdt compiler for jsps)

I built one big package. I think this is fine, for now anyways. From
what I can tell the current swt-gtk packages aren't suitable. The
swt-gtk source packages have precompiled Jars and .so's. The ones my
Eclipse packages build are totally from source.

My Eclipse packages, excluding Lucene in contrib and some Kaffe
instability, are about suitable for main at this point. Please check
them out. Oh yes, and the crazy Kaffe legal thread on debian-java.

> Cheers,
>   Joerg
> 
-- 
Jerry Haltom <wasabi@larvalstage.net>