[jsr342-experts] Control over what is scanned, within a jar/module
- From: Pete Muir <pmuir@...>
- To: jsr342-experts@...
- Subject: [jsr342-experts] Control over what is scanned, within a jar/module
- Date: Wed, 12 Sep 2012 17:32:00 +0100
The CDI EG is considering standardizing fine-grained control over what
classes within a jar module.
The proposal today is to take the xml we defined in Weld as a starting point
and standardize it, making any improvements needed on the way.
A number of CDI EG members have suggested that it would be useful to
standardize this not only for CDI, but for all Java EE specs, allowing a user
to control, from one deployment descriptor (e.g. scan.xml) what is / isn't
scanned for all technologies in Java EE.
I know David Blevins has a similar proposal, somewhere, but not sure where.
I wanted to raise this issue here, before the CDI EG goes off and does this
on it's own.