[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [aspectj-dev] -inpath ??
|
There's one more option: keep injars and inpath(s) separate. They might
feel sufficiently different to warrant adding an option and making the
distinction explicit.
I'm not the best person to go to for command-line aesthetics, but I know
that in the Ant task and in the GUI I would want these to be separate lists,
since the contain different kinds of items. I've been working on the AJDT
project configuration UI some and think that we should have an "In" tab on
the "AspectJ Build Path" page that lets us *separately* specify and inspect
the 3 itemized lists of additional compiler inputs (aspect JARs, class JARs,
and class directories).
Mik
> -----Original Message-----
> From: aspectj-dev-admin@xxxxxxxxxxx [mailto:aspectj-dev-admin@xxxxxxxxxxx]
> On Behalf Of Dean Wampler
> Sent: Thursday, November 06, 2003 8:23 PM
> To: aspectj-dev@xxxxxxxxxxx
> Subject: Re: [aspectj-dev] -inpath ??
>
> Should -inpath weave into any jar files it finds, as well as class
> files? That would be convenient, but different than the normal behavior
> of CLASSPATH, where jar file names have to be specified explicitly. I
> guess consistency w/ CLASSPATH is better.
>
> dean
>
> Andrew Clement wrote:
>
> >
> > Hi,
> >
> > As some of you know, I am looking at this feature. The idea
> > is that we want to remove the requirement that users package
> > up class files into a jar in order to do binary weaving.
> > (Today, once they are packaged they are passed in on
> > the -injars parameter)
> >
> > I just prototyped the support for allowing directories to be
> > passed in, in addition to jars. This means the compiler
> > will weave into any class files it finds in the directory
> > tree specified.
> >
> > I just can't decide on the externals and am after
> > some opinions.
> >
> > My prototype extended -injars so that it allowed directories
> > as well as zips/jars - so in fact -injars supports something
> > like the classpath format now "a.zip;c:\mydir;b.jar". It
> > runs like this:
> >
> > ajc -injars c:\MyEclipseJavaProjectBinDir TracingAspect.java
> >
> > Now, if only it was -inpath ...
> >
> > So these are the options I see:
> > - Add a brand new -inpath option that supercedes -injars
> > - Rename -injars to -inpath
> > - Just leave it as prototyped where -injars has a 'looser'
> > (misleading!) meaning.
> >
> > I'm worried about the impact on:
> > - migration of stuff already out there using the old option.
> > - documentation of the option
> > - amount of extra work I have to do !!! :)
> >
> > thanks,
> > Andy.
> > AJDT Development
>
>
> --
> Dean Wampler, Ph.D.
> Aspect Programming
> dean@xxxxxxxxxxxxxxxxxxxxx <mailto:dean@xxxxxxxxxxxxxxxxxxxxx>
> http://www.aspectprogramming.com
>
>
> _______________________________________________
> aspectj-dev mailing list
> aspectj-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/aspectj-dev
