[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-ant-dev] Fixing Ant bug in a plugin?
|
Darin,
The one line fix for the Ant bug was included in the bug report that we made:
https://issues.apache.org/bugzilla/show_bug.cgi?id=45010
Steve Goetze, also of Dovetailed Technologies, found a slick way to patch the global
Ant classpath using a plugin that implements a plugin lifecycle class.
He built this into a plugin that's available from here:
http://dovetail.com/downloads/misc/index.htmlIt includes the source code for the Eclipse lifecycle class that does the job.
You can use this plugin to fix the broken Ant 1.7.0 <modified/> selector, which hopefully
they will fix in the next release of Ant. It also demonstrates the technique for patching/overriding
other Ant classes by prepending an arbitrary jar to the Ant global classpath.
Hopefully this will help someone else who needs to fix an Ant bug in a way that is convenient to
distribute to a bunch of Eclipse users.
Kirk Wolf
Dovetailed Technologies
----- Original Message -----
From: "Darin Swanson" <
darinrs@xxxxxxxxxxx>
To: <
platform-ant-dev@eclipse.org>
Sent: Fri, 16 May 2008 11:28:23 -0700
Subject: Re: [platform-
ant-dev] Fixing
Ant bug in a plugin?
There is an extension point (org.
eclipse.
ant.core.extraClasspathEntries) to add extra JARs to the
Ant runtime classpath, but these JARs are added to the classpath after the
Ant Home JARs.
I would encourage you to attach your fix to the
Ant bug for inclusion in the next version of
Ant.
Darins
http://runnerwhocodes.blogspot.com ----- Original Message -----
From: Kirk Wolf
To:
platform-ant-dev@eclipse.org
Sent: Friday, May 16, 2008 7:20 AM
Subject: [platform-
ant-dev] Fixing
Ant bug in a plugin?
There's a nasty bug in
Ant 1.7 that prevents the <ftp> <modified> tag from working properly.
See:
https://issues.apache.org/bugzilla/show_bug.cgi?id=45010
The fix to this is very simple (changing one line in an
Ant class).
I'd like to package a patched
Ant class into a jar and include that jar into a plugin that my users can use with
Eclipse to simplify fixing this problem.
- Can I do this with an extension point that adds the jar to the beginning of the
Ant classpath?
- Can I make the extension conditional on having the
Ant 1.7 plugin?
I'm a newbie to writing plugins, can anyone help me with the plugin.xml to do this?
Thanks,
Kirk Wolf
Dovetailed Technologies