[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[platform-ant-dev] Re: Antview 2.2.8
|
http://bugs.eclipse.org/bugs/show_bug.cgi?id=24580
I just released a new version of TargetInfo that provides the enclosing
project name and target dependencies. If there's anything else you need to
eliminate the Ant View's support on JDOM, let us know.
- Jared
On Tuesday 08 October 2002 04:31 pm, you wrote:
> no objection to the mailing list..
>
> comments:
> 1) on classpath, no problem I can clean up that up.
> 2) on JDOM, TargetInfo doesn't work for me, at this time I need the
following information:
> <project> tag:
> name
> default
> <target> tag:
> name
> depends
> description
> AntRunner/TargetInfo provides everything except project name and
target description.
> It would be great if you can expose the project tree. The latest
feature request I have is for
> large projects with many build files to be able to filter at the
project (build file) level. At this
> time I'm not sure how that will be implemented. (filename regex,
directory depth, manual selection,
> etc)
>
> In fact, what would be great is if I can instantiate an AntRunner
type class that exposes the underlying
> ant classes (in proxy with extended class path) that I can maintain
in the viewer. Currently, I have 2
> instances of the project, one to expose dependency information and
one to execute (AntRunner).
> I spent some time working on a proxy class to replace AntRunner, but
had too many chicken and egg
> problems with the extended classloader, so I took the DOM approach.
>
> Roscoe
>
>
> -----Original Message-----
> From: Jared Burns [mailto:jared-eclipse@xxxxxxxxx]
> Sent: Tue 10/8/2002 3:42 PM
> To: Roscoe M. Rush
> Cc:
> Subject: Re: Antview 2.2.8
>
>
>
> Hola.
>
> I have your latest release and while the buildnotes look promising, there
are
> some problems with the code.
>
> Your project contains a .classpath file which is too "specific". For
example,
> it contains references to the win32 swt.jar. When developing Eclipse
plugins,
> you never need to edit your .classpath file. The classpath is taken care of
> by PDE based on your project dependencies. To fix the problem, I just
loaded
> your project into Eclipse, right clicked on the plugin.xml and choose
"Update
> Classpath." It magically takes care of everything for you.
>
> Also, you don't need to include the jdom libraries. Eclipse provides this
> functionality. In the HEAD branch (which isn't currently being submitted to
> builds), AntUtil defines the following method:
> public static TargetInfo[] getTargets(String path) throws CoreException {
> AntRunner runner = new AntRunner();
> runner.setBuildFileLocation(path);
> return runner.getAvailableTargets();
> }
>
> Basically, you should be able to write your view using only Eclipse code.
If
> you need more support, ask for it and we'll see what we can do.
>
> Unless you object, I plan to send this email to the platform-ant-dev
mailing
> list. I like to have discussions in public as often as possible. :)
>
> Thanks,
> - Jared
>
> On Tuesday 08 October 2002 02:55 pm, you wrote:
> > Jared,
> >
> > This release is a little earlier than I planned, I was getting enough
> > activity that I felt I needed to release this version to help
> out the
> > people waiting.
> >
> > The remaining features that I am working on are:
> > 1) ANT user properties (via view tree)
> > 2) Open build file in editor (via double-click or open policy)
> > 3) Relocate resource strings file to language based directory
> > 4) some type of filter on visible build files (considering, new
> > request)
>
> > When I release these features I will be at a point to talk some more
about
> > inclusion in the eclipse base.
>
> > Roscoe Rush
> > roscoerush@xxxxxxxxx
> >
>
>
>
>
>
