RE: [aspectj-users] An idea to improve AJDT build configuration UI

["Mik Kersten" <beatmik@xxxxxxxxx>]

Copied from Bugzilla comment:
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=67332#c3

That sounds right Ramnivas. I now understand the XPath use case better, and
wonder if we could support both. The following assumes a single .properties
file, but could be extended to the one config per file mode.

- Canonical representation of build configurations is the ajbuild.properties
file.
- For large existing build.xml files, you have an Ant script run your XPath
expressions, and generate the ajbuild.properties file. 

You probably set that Ant task to always run pre-build. The idea is that the
Ant properties files are easy enough to generate to enable other front-ends
to manipulating build configurations (e.g. the XPath thing). And AJDT always
picks up changes to the properties file and represents them in build button
menu. The ajbuild.properties file could also be the place that the "active"
build configuration is specified. 

I also think that switching between IDE, Ant, and command line compiles
should be more transparent and seamless than it currently is. Moving from
the cumbersome command-line syntax of ".lst" files and onto the simple
.properties syntax could address that. Here's an addition to the proposal
that describes how to extend the command line compiler to understand the
ajbuild.properties files:

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=50454#c14

Mik

> -----Original Message-----
> From: aspectj-users-admin@xxxxxxxxxxx [mailto:aspectj-users-
> admin@xxxxxxxxxxx] On Behalf Of Ramnivas Laddad
> Sent: Tuesday, June 15, 2004 7:59 PM
> To: aspectj-users@xxxxxxxxxxx
> Subject: RE: [aspectj-users] An idea to improve AJDT build configuration
> UI
> 
> The proposal in comments 12 and 13 would allows me to
> do what I want: reuse of configuration info between ANT
> and AJDT.
> 
> I think the build.xml/XPath expresssion implementation
> supports the "write build.xml first or use an existing
> build.xml" use case better. While the .properties proposal
> supports the "create configuration first" use case better.
> 
> I do think, however, that if only one style is to be
> supported, it should be .properties (in comments 12 and 13).
> This way configurations can be edited graphically much
> better and ANT build files can still use them without
> much problem.
> 
> -Ramnivas
> 
> 
> --- Mik Kersten <beatmik@xxxxxxxxx> wrote:
> > Also note related posts #12 and #13 on the long-running "Improve
> > build
> > configuration mechanism and UI" discussion.  They suggests an Ant and
> > Eclipse PDE style syntax for build configurations.  Comments would be
> > appreciated as we are in the process of designing the improved build
> > configuration support.
> >
> >   https://bugs.eclipse.org/bugs/show_bug.cgi?id=50454#c12
> >
> > Mik
> >
> > > -----Original Message-----
> > > From: aspectj-users-admin@xxxxxxxxxxx [mailto:aspectj-users-
> > > admin@xxxxxxxxxxx] On Behalf Of Ramnivas Laddad
> > > Sent: Tuesday, June 15, 2004 11:41 AM
> > > To: aspectj-users@xxxxxxxxxxx
> > > Subject: [aspectj-users] An idea to improve AJDT build
> > configuration UI
> > >
> > > The current poll regarding .lst file use in AJDT and the
> > > way I use ANT got me thinking on how it could be improved:
> > >
> > > (Filed as a enhancemewnt request
> > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=67332).
> > >
> > > Enhancement:
> > > Allow AJDT to refer to elements in build.xml to select
> > > source/class/jar elements.
> > >
> > > This would allow me to reuse information in ANT build files,
> > > I can now define my configurations in build.xml
> > > and refer to elements in it from AJDT. For example, AJDT
> > > could allow specifying XPath expression to point to
> > > a "path-like" element in the build.xml such as
> > > "project/target[@name="policy-build"]/iajc/sourceroots"
> > >
> > > -Ramnivas
> > > _______________________________________________
> > > aspectj-users mailing list
> > > aspectj-users@xxxxxxxxxxx
> > > http://dev.eclipse.org/mailman/listinfo/aspectj-users
> >
> > _______________________________________________
> > aspectj-users mailing list
> > aspectj-users@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/aspectj-users
> >
> 
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/aspectj-users