As a little follow-up, it looks like the only consumer of the org.apache.sling.jcr.js.nodetypes artifact is the org.apache.sling.resource-editor in contrib/explorers/resourceeditor. It almost looks like if we retire the nodetypes we might have to retire the resource-editor as well.
Again, if somebody thinks these are still used and/or is willing to maintain them (which would include redoing the nodetypes without commons.json) thats perfectly fine - but if not, I would call a vote for retiring them. regards, Karl On Sat, Jun 3, 2017 at 12:12 AM, Karl Pauls <karlpa...@gmail.com> wrote: > Hi, > > as part of SLING-6887 I'm almost done with removing all usage of > org.json and commons.json from trunk. In a nutshell, the last artifact > that would need to be migrated is: > > org.apache.sling.jcr.js.nodetypes in contrib/jcr/js/nodetypes > > However, it doesn't look like there has been much development around > it in the last couple of years - hence I was thinking, can we retire > it maybe? > > regards, > > Karl > > -- > Karl Pauls > karlpa...@gmail.com -- Karl Pauls karlpa...@gmail.com
