You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by Brent Atkinson <br...@gmail.com> on 2015/05/11 16:34:52 UTC
Continue to use redback?
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?
* How difficult would this re-integration be in terms of required changes
or level or effort?
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)?
Regards,
Brent
Re: Continue to use redback?
Posted by dr...@gmail.com.
Brent:
IIRC, we had an issue with the early 1.3 red back and oracle OID; I think we had to do a patch at our client and manually replace jars in continuum under tomcat/ Geronimo. I might have that source still somewhere...
As long as we maintain LDAP integration as easily as it is to configure now (sarc) as I have several hundred users on 422 projects...
And I need 1.5 as we moved to Java 8 on our boxes...
Louis
Sent from my iPad
> On May 11, 2015, at 10:34 AM, Brent Atkinson <br...@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?
> * How difficult would this re-integration be in terms of required changes
> or level or effort?
>
> 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)?
>
> Regards,
> Brent
Re: Continue to use redback?
Posted by Brent Atkinson <br...@gmail.com>.
Thank you for chiming in, and you are completely right.
I actually just had confirmed exactly this and updated CONTINUUM-2757
<https://issues.apache.org/jira/browse/CONTINUUM-2757> with a screenshot of
continuum running under Java8. The real culprit was the older version of
Spring. The other details were related to *building* under Java 8 rather
than *running* under Java 8.
I may have conflated the issues because of the recent servlet 3 work I had
done. There were problems running the pre-compiled JSPs due to differences
in the class runtimes (java.util.Map for example).
Thanks again,
Brent
On Wed, May 13, 2015 at 11:40 PM, Olivier Lamy <ol...@apache.org> wrote:
> 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 <br...@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 <br...@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
>
Re: Continue to use redback?
Posted by Olivier Lamy <ol...@apache.org>.
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 <br...@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 <br...@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
Re: Continue to use redback?
Posted by Olivier Lamy <ol...@apache.org>.
Hey
On 14 May 2015 at 01:18, Brent Atkinson <br...@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 <br...@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
Re: Continue to use redback?
Posted by Brent Atkinson <br...@gmail.com>.
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.
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 <br...@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
>
Re: Continue to use redback?
Posted by Olivier Lamy <ol...@apache.org>.
Hi,
On 12 May 2015 at 00:34, Brent Atkinson <br...@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