I noticed that, too. The 6/7/8 SE version contains: javax.annotation.Generated javax.annotation.PostConstruct javax.annotation.PreDestroy javax.annotation.Resource javax.annotation.Resources
whereas EE 7 (and Maintenance Final Release version (1.2) of JSR-250, which targets EE and 'future' versions of SE - https://jcp.org/aboutJava/communityprocess/mrel/jsr250/index2.html ) contains (and only these classes): javax.annotation.Generated javax.annotation.ManagedBean javax.annotation.security.PermitAll javax.annotation.PostConstruct javax.annotation.PreDestroy javax.annotation.Priority javax.annotation.Resource javax.annotation.Resource.AuthenticationType javax.annotation.Resources javax.annotation.security.DeclareRoles javax.annotation.security.DenyAll javax.annotation.security.RolesAllowed javax.annotation.security.RunAs javax.annotation.sql.DataSourceDefinition javax.annotation.sql.DataSourceDefinitions I'd argue that as EE type functionality is frequently required in an enterprise bundle and that the JSR is targeting future SE versions, the true inclusion 1.2 would be preferable to sticking with 1.0. Plus, from the perspective of our project, getting a Jersey 2.0 client (actually, all javax.ws.rs implementations) to work in a standard build of Karaf would be very nice! -- View this message in context: http://karaf.922171.n3.nabble.com/javax-annotation-1-2-0-and-KARAF-2660-tp4036056p4036062.html Sent from the Karaf - Dev mailing list archive at Nabble.com.
