Re: [ajdt-dev] build.ajproperties editor

["Alexandru Popescu" <the.mindstorm.mailinglist@xxxxxxxxx>]

Ohh... probably I have badly described the problem. You don't have to
tell TestNG which files have javadoc annotations. It is able to
autodiscover this (caching is not much of an option, because I will
have than to deal with model updates events - if Eclipse offers such
events.).

The real problem is the TestNG needs the source code for the tests, so
that it can extract these javadoc annotations (this is an independent
API - not based on Eclipse). And when your project is growing bigger
with many many sources, it is a pitty to force TestNG to parse
thousands of source files, instead of limitting it to a couple of
them. So, in fact this file will tell TestNG: don't use the whole
source directories defined in Eclipse and limit yourself to the ones I
have specified in the properties file.

Thanks a lot for your suggestions so far,

./alex
--
.w( the_mindstorm )p.


On 4/21/06, Wes <wes@xxxxxxxxxxxxxx> wrote:
> Try http://www.eclipse.org/articles/ and search for "properties".
> You might be better off following the detailed articles and using any sample code.
>
> But instead of having the user specify files, why doesn't TestNG just cache
> the filenames that have (and don't have) javadoc annotations and then do a
> quick up-to-date check?  The properties file and javadoc annotations
> will get out of sync if you rely on a user to manually update it.
>
> Wes
>
> > ------------Original Message------------
> > From: "Alexandru Popescu" <the.mindstorm.mailinglist@xxxxxxxxx>
> > To: "AspectJ Development Tools developer discussions" <ajdt-dev@xxxxxxxxxxx>
> > Date: Fri, Apr-21-2006 11:31 AM
> > Subject: Re: [ajdt-dev] build.ajproperties editor
> >
> > I am not sure how to read the part about "uses eclipse internal api".
> > Because I am talking about an Eclipse plugin, I am expecting to use
> > the Eclipse API, so what is the real bad part of it? I know this kind
> > of editor is used in some places (for example for displaying
> > build.properties), so I would expect to have quite a clean solution.
> > Unfortunately, I don't have enough time to create a custom solution,
> > and that is the main reason I am looking to reuse something.
> >
> > thanks for any help,
> >
> > ./alex
> > --
> > .w( the_mindstorm )p.
> >
> >
> > On 4/21/06, Matt Chapman <mpchapman@xxxxxxxxx> wrote:
> > > Alex,
> > >
> > > The properties editor can be found in the ajdt1_3 branch in
> > > BuildEditor.java in the org.eclipse.ajdt.ui plugin. BUT it uses
> > > eclipse internal api, and is therefore hard to maintain. It might be
> > > better to consider some other mechanism, such as direct manipulation
> > > in the package explorer, for example like including and excluding
> > > source files from the classpath.
> > >
> > > Regards,
> > >
> > > Matt.
> > >
> > > On 19/04/06, Alexandru Popescu <the.mindstorm.mailinglist@xxxxxxxxx>
> > wrote:
> > > > Hi guys!
> > > >
> > > > I would like to kindly ask your help in the following matter:
> > lately our TestNG users have had
> > > > reported performance problems with the Eclipse plugin when using
> > JDK1.4. This is mainly due to the
> > > > fact that TestNG has to scan the whole set of source dirs for
> > javadoc annotations, prior to start.
> > > > With bigger and bigger projects, you can imagine this is taking a
> > while.
> > > >
> > > > A new TestNG user had suggested a small hack that will allow users
> > to restrict the sources to be
> > > > scanned: a properties file. At this point, I had remembered about
> > the build.ajproperties used by
> > > > AJDT and its quite nice editor. I am wondering if you can point me
> > to the right direction to check
> > > > its code. Also, in case this editor can be easily reused in TestNG
> > Eclipse plugin, I would like to
> > > > kindly ask for your permission to incorporate it in the TestNG
> > Eclipse plugin. I would probably have
> > > > to mention that, as you may expect, TestNG is an open source
> > project and so it is the plugin.
> > > >
> > > > Many thanks in advance,
> > > >
> > > > ./alex
> > > > --
> > > > .w( the_mindstorm )p.
> > > > _______________________________________________
> > > > ajdt-dev mailing list
> > > > ajdt-dev@xxxxxxxxxxx
> > > > https://dev.eclipse.org/mailman/listinfo/ajdt-dev
> > > >
> > > _______________________________________________
> > > ajdt-dev mailing list
> > > ajdt-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/ajdt-dev
> > >
> > _______________________________________________
> > ajdt-dev mailing list
> > ajdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/ajdt-dev
> >
>
> _______________________________________________
> ajdt-dev mailing list
> ajdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ajdt-dev
>