Good point! I will think about if we can reach this with a single api module and Maven features (e.g. includes, excludes) or we keep it separated as is.
-- Stephan On 31.07.13 10:54, "V.A, Chandan" <[email protected]> wrote: >Hello Stephan, >There could be one advantage of having the annotation as a separate >module under api if the annotations (if at all) are to be used by some >design time tools. The design time tools need not have direct dependency >to core apis instead have dependency only to api-annotation only. The >design time tools can then generate JAVA annotated classes out of >api-annotation module. > >Thanks, >Kind Regards >Chandan VA > > >-----Original Message----- >From: Klevenz, Stephan [mailto:[email protected]] >Sent: Wednesday, July 31, 2013 12:41 PM >To: [email protected] >Subject: annotations api > >Hi, > >The annotations api is currently separated in its own maven module and >results also in a separate build artifact. I don't see a reason for that >and suggest to re-factor the annotation module and make is part of the >core api. > >Any thoughts on that? > >Stephan >
