I don't understand your issue with 1.8? You can configure compiler target 1.6 for classes generated with jpox plugin. The compiled classes will work on a 1.8 java runtime (that's what we did for Archiva)
On 14 May 2015 at 13:07, Olivier Lamy <ol...@apache.org> wrote: > Hey > > On 14 May 2015 at 01:18, Brent Atkinson <brent.atkin...@gmail.com> wrote: > >> Thanks Olivier, this was extremely helpful. >> >> At the moment, I'm not sure which strategy makes the most sense, but >> getting the source code should at least help determine how to move >> forward. >> The immediate goal is to get Continuum running under Java 8, and if >> possible, servlet 3 to speed up deployment by disabling jar scanning. >> >> I have migrated the subversion repo to a local git clone, but (from >> http://www.codehaus.org) it appears that the source will be migrated to >> github. Do you know if this will include redback? If so, the history >> should >> be available at github after the shutdown. >> > > I believe all svn repos from codehaus will be migrated as read only to a > github account. > > >> >> Source Code: Will all be migrated to Github - SVN repos will be migrated >> to >> > Git and transferred into the "codehaus" Github account. This is a >> readonly >> > account. Inactive projects may be migrated ahead of the shutdown. >> >> >> Thanks again for your help, >> >> Brent >> >> On Wed, May 13, 2015 at 7:18 AM, Olivier Lamy <ol...@apache.org> wrote: >> >> > Hi, >> > >> > On 12 May 2015 at 00:34, Brent Atkinson <brent.atkin...@gmail.com> >> wrote: >> > >> > > Greetings, >> > > >> > > On multiple fronts I discovered that the project's dependency on >> Redback >> > is >> > > a blocker for using Java 8 and configuring the application for the >> > Servlet >> > > 3 spec. There are also larger issues with authentication, >> authorization >> > and >> > > user/role management that will need to be addressed to improve the >> > overall >> > > quality of Continuum going forward. >> > > >> > > It is not clear what the best strategy is for continuing: >> > > >> > > * Is it feasible to continue to use redback since its migration to a >> > > sub-component of Archiva? >> > > >> > >> > Note the redback version as archiva subcomponent is now without any jsp >> > related technologies. >> > >> > >> > > * How difficult would this re-integration be in terms of required >> > changes >> > > or level or effort? >> > > >> > >> > need to add back jsp/tags >> > >> > >> > > >> > > If this is a considerable task, it may make more sense to patch (or >> > > recompile) the old version to unblock forward progress in the short >> term, >> > > while working to migrate to something like Spring Security in later >> > > releases. However, while trying to evaluate this as a possibility I >> had >> > > trouble locating the historical versions. >> > > >> > > * Where is the source code for the older versions (specifically, >> 1.3-M3)? >> > > >> > >> > Here http://svn.codehaus.org/redback/redback/ >> > >> > Take care as codehaus will be soon shutdown. >> > I guess it's in branches as redback-1.3-Mx >> > >> > Maybe this can be hosted as a branch in archiva redback git repo? >> > >> > >> > >> > > >> > > Regards, >> > > Brent >> > > >> > >> > >> > >> > -- >> > Olivier Lamy >> > http://twitter.com/olamy | http://linkedin.com/in/olamy >> > >> > > > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
