On 8/21/07, Marshall Schor <[EMAIL PROTECTED]> wrote: > >> 2. Its build as RCP application (this requires an eclipse install) > >> and packaged for each > >> platform we want to support (win, linux and mac). > I also found this: http://vyzivus.host.sk/maven2-build-plugin-howto.html > It describes building an RCP app using maven. They have a bigger list > of targets, though: > > * carbon.macosx.ppc > * carbon.macosx.x86 > * gtk.linux.ia64 > * gtk.linux.ppc > * gtk.linux.x86 > * gtk.linux.x86_64 > * gtk.solaris.sparc > * motif.aix.ppc > * motif.hpux.ia64_32 > * motif.hpux.PA_RISC > * motif.linux.x86 > * motif.solaris.sparc > * photon.qnx.x86 > * win32.win32.x86 >
This is a bit scary... how many different platform-specific downloads do we need to worry about building and maintaining? Also would Apache have any problems with us redistributing the parts of Eclipse needed for the RCP runtime? With Marshall claiming success on the Eclipse update site, maybe that would make it easy enough to just do this as a separate feature? Not quite as convenient as an RCP, since users would have to download Eclipse first and then go to our update site, but it still seems manageable for the users and it might make our lives easier. -Adam
