Bug 281342 - [aspects] use regex to identify/register an aspect
Summary: [aspects] use regex to identify/register an aspect
Status: NEW
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Weaving (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: equinox.incubator-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 281452
Blocks:
  Show dependency tree
 
Reported: 2009-06-24 08:27 EDT by Erdal Karaca CLA
Modified: 2019-09-06 15:35 EDT (History)
0 users

See Also:


Attachments
Enables aspects registration by regex (16.49 KB, patch)
2009-06-25 02:50 EDT, Erdal Karaca CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Erdal Karaca CLA 2009-06-24 08:27:53 EDT
currently, this is possible:

Export-Package: com.example.aspects;aspects:="MyAspect1,MyAspect2,MyAspect3"

It there are just few aspects in the exported package, this is good for registering aspects.
Unfortunately, if you have a lot of aspects to register, this would become unhandy.

A more flexible solution could use a regex to identify aspects in the exported package:

Export-Package: com.example.aspects;aspects:=".*Aspect\d+"

This should identify/register any aspects whose name match the given regex.
Comment 1 Erdal Karaca CLA 2009-06-25 02:50:00 EDT
Created attachment 140066 [details]
Enables aspects registration by regex

Usage example:

Export-Package: com.example.aspects;aspects="^.*TestUnit"

Note: the ^ at the beginning of the regex denotes the matching text (aspect name).
In general, this is not mandatory for a regex to be compiled, but this patch uses the starting ^ to check whether to search by regex or not, i.e. if you omit ^ at the beginning, the patch will do nothing.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:35:56 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.