Sure, I think we should release the plugin as 2.1.0. I'm also fine with changing the artifact id now to fit the maven rules. If people want to use the new version, they have to change their dependency and instead of just bumping the version number, it needs a change in the artifact id as well.
What about SLING-6936 ? Regards Carsten Tobias Bocanegra wrote > Hi, > > With the fix of [0] the jspc plugin uses the latest sling jsp scripting > backend and supports java 1.8. > Would it be possible to release it? > > thanks. > regards, toby > > ps: the plugin violates the maven plugin convention, as it starts with > "maven-": > > --- > [INFO] --- maven-plugin-plugin:3.4:helpmojo (help-goal) @ maven-jspc-plugin > --- > [ERROR] > > Artifact Ids of the format maven-___-plugin are reserved for > plugins in the Group Id org.apache.maven.plugins > Please change your artifactId to the format ___-maven-plugin > In the future this error will break the build. > --- > > So it probably should be renamed some time soon.... > I created an issue [1] > > > [0] https://issues.apache.org/jira/browse/SLING-6923 > [1] https://issues.apache.org/jira/browse/SLING-6940 > -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
