[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [aspectj-dev] eclipse 3.1m6 has rudimentary API enforcement

Good question.  I imagine that to consider pushing this into Eclipse first
someone from our user base would need to request this as a feature and
describe how it's better than using declare error/warning, then AJDT would
need to implement the prototype, and finally we could suggest it as an
Eclipse feature.  I'm not sure about the utility of using pointcuts for this
yet, and worry about it feeling like yet another complicated project setting
being buried deep in a preference page.

But in general I like the idea of the pointcut language percolating out into
other tools such as access static checkers, profilers, and debuggers.  Those
tools rely on expressing static and dynamic conditions, and using pointcuts
for that should be a lot easier than having a whole bunch of patterns and
wildcards.  

Mik

> -----Original Message-----
> From: aspectj-dev-bounces@xxxxxxxxxxx [mailto:aspectj-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Jim Bethancourt
> Sent: Tuesday, April 05, 2005 1:41 PM
> To: AspectJ developer discussions
> Subject: Re: [aspectj-dev] eclipse 3.1m6 has rudimentary API enforcement
> 
> Might it be possible to suggest to the Eclipse team that they could
> make use of the AspectJ libraries, or would that not be a good idea?
> 
> Cheers,
> Jim
> 
> On Apr 5, 2005 3:36 PM, Oli B. <boehm@xxxxxxxxxx> wrote:
> > Hello,
> >
> > one question to 3.1M6: does the actual AJDT build works with it? On the
> > download page is mentioned "3.1M5a only"?
> >
> > regards
> > Oliver
> >
> > Mik Kersten wrote:
> > > Note that Eclipse 3.1m6 has added some rudimentary support for access
> > > rules that let you do a similar thing to declare error/warning.  This
> > > sort of IDE feature could work better with the pointcut language than
> > > with the wildcard patterns they support.
> > >
> > >
> > >
> > > *Access rules on libraries and projects*
> > >
> > >
> > >
> > > Access rules can be defined on referenced libraries and projects so as
> > > to explicitly allow/disallow/discourage access to specific types.
> > >
> > > picture of Build path wizard with access rules
> > >
> > >
> > >
> > > From:
> > > http://download.eclipse.org/eclipse/downloads/drops/S-3.1M6-
> 200504011645/eclipse-news-all-M6.html
> > >
> > >
> > >
> > >
> > > Mik
> > >
> > >
> > >
> > > --
> > >
> > > http://kerstens.org/mik
> > >
> > >
> > >
> > >
> > >
> > >
> > > ----------------------------------------------------------------------
> --
> > >
> > > _______________________________________________
> > > aspectj-dev mailing list
> > > aspectj-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/aspectj-dev
> >
> > --
> > Oliver Böhm
> > http://www.javatux.de
> >
> > _______________________________________________
> > aspectj-dev mailing list
> > aspectj-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/aspectj-dev
> >
> _______________________________________________
> aspectj-dev mailing list
> aspectj-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-dev