This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: why I think SWT should be built from eclipse
- From: Shaun Jackman <sjackman at gmail dot com>
- To: Michael Koch <konqueror at gmx dot de>, Joerg Jaspert <joerg at debian dot org>, Billy Biggs <vektor at dumbterm dot net>, java at gcc dot gnu dot org
- Date: Fri, 14 Oct 2005 15:21:49 -0600
- Subject: Re: why I think SWT should be built from eclipse
- References: <20051014205405.GC900@asterix.konqueror.de>
- Reply-to: Shaun Jackman <sjackman at gmail dot com>
Why I think SWT should be built from its own source package:
* SWT is a library in itself, and can and does exist outside of Eclipse.
* SWT is used by other applications besides Eclipse.
* If SWT were in the same source package as Eclipse,
a RC bug in Eclipse would hold up SWT.
* SWT is in main, whereas Eclipse is in contrib.
If Eclipse needs patches applied against the released version of SWT,
then they should be so applied. This does not require maintaining an
entirely separate copy of SWT in Eclipse. Likewise for the security
argument. Do not maintain a private copy of the library; rather, use
the shared copy.
* As we have SWT in the archive anyway having a second SWT in Eclipse
increases maintenance work when a critical/security bug gets found.
Then the Eclipse maintainer needs to update "their" SWT or in case
of a stable release the security team needs to update more than one
copy of SWT.
Cheers,
Shaun
2005/10/14, Michael Koch <konqueror@gmx.de>:
> Hi Shaun, hi Joerg, hi all others,
>
> Why do I think SWT (I mean the GTK port of SWT) should be built from
> the Eclipse source package
>
> - Upstream SWT exists only as part of Eclipse. There is nothing like a
> seperate SWT release.
> - Eclipse needs SWT with some additions to be able to use it. The pure
> SWT packaged as swt-gtk dont contains the things Eclipse needs.
> - SWT and Eclipse always needs to the the same version as they are tied
> together very much. Updating one or the other creates big problems
> when not simultaniously updating the other.
> - Eclipse SWT and Standalone SWT can be easily built from Eclipse source
> package
> - As we have SWT in Eclipse anyway having a second SWT in the archive
> increases maintenance work when a critical/security bug gets found.
> Then all Maintainers need to update "their" SWT or in case of a stable
> release the security team needs to update more then one copy of SWT.
>
> Cheers,
> Michael