Re: [cdt-debug-dev] Static linking, Java and CDT

[Doug Schaefer <dschaefer@xxxxxxxxxx>]

Chris is right. Your best best is to up version the CDT plugins you've 
changed and the CDT feature. Do something like 3.0.0.1. We've generally 
left the 4'th digit of the version number for this purpose.

Cheers,
Doug

Recoskie, Chris wrote:

> A bit offtopic for a CDT debug list but...
>
> In short, no.
>
> The best you can do is hack the features to point the update functionality to a server other than eclipse.org.  Either that or hack out the update functionality all together.
>
> Even if you do this though, some enterprising user can still manually download and unzip newer plugins overtop of your product and ruin everything.
>
> ___________________________________________
>
> Chris Recoskie
> Software Designer
> IDE Frameworks Group
> Texas Instruments, Toronto
>
>
>  
>
> > -----Original Message-----
> > From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto:cdt-debug-dev-
> > bounces@xxxxxxxxxxx] On Behalf Of Øyvind Harboe
> > Sent: Sunday, June 26, 2005 7:22 AM
> > To: cdt-debug-dev@xxxxxxxxxxx
> > Subject: [cdt-debug-dev] Static linking, Java and CDT
> >
> > Problem: our plugin ships with a hacked CDT. This is slightly annoying
> > since other CDT plugins may be incompatible with our plugin.
> >
> > In C/C++ the solution would have been to statically link CDT with our
> > executable.
> >
> > Does an equivalent of "static linking" exist in the Java/Eclipse/CDT
> > case?
> >
> >
> >
> > --
> > Øyvind Harboe
> > http://www.zylin.com
> >
> > _______________________________________________
> > cdt-debug-dev mailing list
> > cdt-debug-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
> >    
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
>
>  


--
Doug Schaefer, Senior Software Developer
IBM Rational Software, Ottawa Lab
Kanata, Ontario, Canada