On Jun 5, 2012, at 4:59 AM, Felix Meschberger (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/FELIX-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289358#comment-13289358 > ] > > Felix Meschberger commented on FELIX-3535: > ------------------------------------------ > > Deprecation is marked as: > >> @deprecated since 7.0 > > This sounds wrong, somehow ;-)
not sure how it didn't end up 1.7.0 :-) > > How about upgrading the export micro version, thus export 1.7.1 and document > >> This transient state is not used since bundle version 1.8.0 >> therefore this code is deprecated. >> @deprecated since 1.7.1 I'm not sure why. IIUC you recently changed the export version to 1.7 due to the new method, and we haven't done a release since then. Why would we increment the version again since there hasn't been a release? Maybe I don't understand felix policies? Also IIUC the released bundle version and maven version are going to be 1.8 (skipping odd numbers), is the export package version also going to skip like this? thanks david jencks > >> Minor DS cleanup fixes >> ---------------------- >> >> Key: FELIX-3535 >> URL: https://issues.apache.org/jira/browse/FELIX-3535 >> Project: Felix >> Issue Type: Bug >> Components: Declarative Services (SCR) >> Affects Versions: scr-1.8.0 >> Reporter: David Jencks >> Assignee: David Jencks >> Fix For: scr-1.8.0 >> >> >> I'm opening this to attach to various small cleanup actions. I may add more >> as I find them. >> - fix up javadoc >> - remove or deprecate use of unused state constants >> - finish ServiceMetadata validation >> - use Servicemix junit bundle instead of springsource > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators: > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa > For more information on JIRA, see: http://www.atlassian.com/software/jira > >
