On Mon, Dec 21, 2009 at 1:02 AM, Leo Soto M. <leo.soto@...> wrote:
> I just merged the master branch on my ongoing Django plugin and seems
> like the plugin won't compile anymore. AFAICS,
> broke it, or at least for me, since I'm using Eclipse 3.5.
> Am I (hopefully) talking nonsense? Is there a way to make the plugin
> compile on when using Eclipse 3.5? Or do I need to use Eclipse 3.6
Unfortunately, for compiling it, Eclipse 3.6 is needed now (but not
for running it -- it should run from Eclipse 3.2 onwards, as the code
that's dependent on newer versions is never executed or in some
situations is properly handled in a try..except to handle the cases
where the class is not defined).
What I do when I want to compile using a different version is just
commenting out the code that's not available for it (because from time
to time I do have to add compatibility for older versions). So, if you
want to stick to developing with Eclipse 3.5, simply comment out the
offending code (the only thing that may annoy a bit is that you have
to remove it when providing a patch / committing to your local git).
I've just changed the code so that you'll only need to change 1 file
(just update your local copy to get the changes).
If you have other suggestions or a different workflow to suggest, I'm
open to suggestions... Maybe providing a patch for each version with
that code code-commented out could work (but then again, it might
become outdated as the code evolves).
I know hg provides something as a set of patches applied that don't
actually work as if they are from the current development... maybe git
has something alike?