Yeah. I was thinking something like @SPI where the bare annotation would create entries for all implemented interface or you could list explicit entries if you wanted. I guess I'll write that today.
On Sun, Aug 8, 2010 at 6:06 PM, Luke Patterson <[email protected]>wrote: > haven't seen one, but have thought about implementing it before, open > questions were: > > * source retention, and then mark dep as optional? > * annotation takes an optional class argument for when service type is > ambiguous? e.g. service type is distant ancestor class > * add osgi ds entries? > > > > -- sent from a device with a tiny keyboard, so message might be brief. > (and if you're like, "hey, that doesn't make any sense cause typing this > notice must have taken just as long as typing the original message", please > understand that this notice is my preconfigured email signature, so that > means I only had to type it once) -- > > > On Aug 8, 2010, at 12:47 PM, Justin Lee <[email protected]> wrote: > > Before I go and write one, has anyone seen a mavenized APT that will scan >> for annotated classes and build the appropriate SPI manifest for them? It >> wouldn't be hard to write but it'd save me some time... >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
