Re: [ajdt-dev] Convert to AspectJ project

[Andy Clement <andrew.clement@xxxxxxxxx>]

The code for determining the set of source files from a set of source
folders is in:

org.aspectj.org.eclipse.jdt.internal.core.builder.BatchImageBuilder

this is a class that sits very much on the join between AJDT and
AspectJ - currently being an AspectJ thing, so fixing multiple source
folders is an AspectJ bug.  At the moment we skip all the eclipse
logic in that image builder (and the associated
IncrementalImageBuilder) and have our own for driving the compiler
(AjBuildManager).  To properly solve many of our inter-project
dependency problems and support multiple source input folders we need
to rebase on the eclipse types.

Just because it is in these imagebuilders, doesnt mean it is exposed
to command line users.

Andy.

On 27/10/05, Alexandru Popescu <the.mindstorm.mailinglist@xxxxxxxxx> wrote:
> #: Matt Chapman changed the world a bit at a time by saying on  10/27/2005 1:47 PM :#
> > Yes, unfortunately separate output folders are simply not supported by
> > AspectJ and AJDT. There is a bug (101983) for the AspectJ side, and
> > another (46665) for the AJDT side. I'm fairly sure the work required
> > to implement the AspectJ side of this will be significant. Until then
> > I'd suggest the best alternative would be to move the tests into a
> > separate project.
> >
> > Regards,
> >
> > Matt.
> >
>
> Thanks Matt. I've been reading through the both mails. What I was asking myself is why this is
> considered an AspectJ bug: as far as I know f.e. javac doesn't allow multiple output directories. I
> don't know about the JDT compiler but to me it would look rather weird to have this option into the
> compiler (how are you giving the source dirs per output dir).
>
> Can you detail a little the rationale behind this?
>
> ./alex
> --
> .w( the_mindstorm )p.
>
>
>
> > On 27/10/05, Alexandru Popescu <the.mindstorm.mailinglist@xxxxxxxxx> wrote:
> >> #: Rafal Krzewski changed the world a bit at a time by saying on  10/27/2005 12:27 PM :#
> >> > Alexandru Popescu wrote:
> >> >
> >> >> Is this coming from the fact that the project uses 2 source folders: one
> >> >> for code, and one for tests and is separating the output in 2 build
> >> >> directories?
> >> >>
> >> >> If yes, is there any workaround for this?
> >> >>
> >> >> your answers are highly appreciated,
> >> >
> >> > AFAICT 2 solutions are possible:
> >> >
> >> > 1. let the comiler put all the classes in a single output directory. If
> >> > you are using the eclipse comiled files to build a jar, you will need to
> >> > filter the test classes out (should be straightforward if you have
> >> > consistent naming conventions)
> >> >
> >> > 2) if filtering out the test classes is too cubmersome, you may move
> >> > them to a separate project.
> >> >
> >> > R.
> >>
> >> Unfortunately, this doesn't look like a workaround :-(.
> >>
> >> Is this gonna change? I don't see any valid reason for doing one of the suggested ways.
> >>
> >> ./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
>