You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by Olivier Lamy <ol...@apache.org> on 2011/05/02 17:18:35 UTC
Some refactoring [was Re: [DISCUSS] Archiva as an OSGi OBR/EBR ]
Hello,
Looks to be a nice feature.
But more generally could we think about some other refactoring ?
I have some ideas :
* ui , move to an other framework I have in mind : gwt, vaadin ....
(it looks ace use vaadin ?)
* removing all the current plexus(-spring) old components to real/only
spring components (this could be already done in trunk ? ) (or an
other container ?)
* remove redback and use something else for authz and role management (shiro ? )
WDYT ?
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
2011/5/2 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> Hi Wendy,
>
> thanks for the update.
>
> So it seems that the need is there :)
>
> I have checkout the sources but didn't see anything looking like OBR
> (repository.xml management, etc).
> So maybe the work didn't start yet.
>
> I'm quite sure that Archiva could be a great EBR, which can be very helpful
> for Apache projects such as ServiceMix, Karaf, and the other ones powered by
> Karaf (like Geronimo).
>
> Regards
> JB
>
> On 05/02/2011 03:26 PM, Wendy Smoak wrote:
>>
>> On Mon, May 2, 2011 at 9:15 AM, Jean-Baptiste Onofré<jb...@nanthrax.net>
>> wrote:
>>
>>> I wonder what do you think about enhancing Archiva to act as an EBR
>>> (Enterprise Bundle Repository).
>>
>> Sounds like fun. :) I know it (or something similar, I'm not familiar
>> with the details of OSGi) has come up for discussion before and there
>> was interest, [1] but I don't think the work was ever finished.
>>
>> [1]
>> http://mail-archives.apache.org/mod_mbox/archiva-dev/200812.mbox/%3C4949EF39.3020807@atlassian.com%3E
>>
>
Re: Some refactoring [was Re: [DISCUSS] Archiva as an OSGi OBR/EBR
]
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
FYI, ACE currently uses Vaadin for UI. We have to work on the UI on ACE
but it's fully OSGi and works fine.
Regards
JB
On 05/02/2011 10:52 PM, Brett Porter wrote:
>
> On 03/05/2011, at 1:18 AM, Olivier Lamy wrote:
>
>> Hello,
>> Looks to be a nice feature.
>>
>> But more generally could we think about some other refactoring ?
>> I have some ideas :
>> * ui , move to an other framework I have in mind : gwt, vaadin ....
>> (it looks ace use vaadin ?)
>
> I think this is a good idea - though the more important prerequisite is to pull any functional code that's embedded in the current UI out so you can deploy a working Archiva without the webapp (if it were a set of OSGi bundles, or a thinner webapp that just has the REST/WS layer). One of the important changes that is still in progress is to be able to run Archiva with less of it's stuff enabled - e.g. just a thin proxy on your localhost, but the full app somewhere else.
>
> If we can do that split, then you can keep the current UI working through releases while a new one is built up.
>
> I'm open to either Vaadin or GWT. Haven't evaluated them myself. They seem the two best choices. I'm also interested in Sling (which may be complementary), since it's very REST oriented and could make it very easy to deal with custom content.
>
>> * removing all the current plexus(-spring) old components to real/only
>> spring components (this could be already done in trunk ? ) (or an
>> other container ?)
>
> Been meaning to do that for a while. The sooner the better...
>
> I tend to prefer Guice more, but Spring is what we have now, but all the programming is in Plexus :)
>
>> * remove redback and use something else for authz and role management (shiro ? )
>
> That's also been on the TODO list for some time, though I think we want to make sure we don't lose any functionality along the way. Maybe one option is for Redback to be layered as well - remove large bits of it's internals and replace with Shiro, then split the "content" part up so that it's not so dependant on Struts. It could again keep working while an alternative was built...
>
>>
>> WDYT ?
>
> Glad to see all the interest! Let me know how I can help you get started :)
>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
Re: Some refactoring [was Re: [DISCUSS] Archiva as an OSGi OBR/EBR ]
Posted by Brett Porter <br...@apache.org>.
On 03/05/2011, at 6:38 PM, Olivier Lamy wrote:
> An other idea I have : it's a plugin mechanism (with some "extension
> points") to easily enhance archiva.
> And if we use an osgi "infra", this plugin mechanism will be easier to
> integrate (hot reload etc...)
Absolutely. The revised APIs are built with extension points in mind - just at the moment you have to drop them into WEB-INF/lib (And sometimes wire in spring) - more dynamic would be great. Ideally we could just use something like Felix Web Console as a basic administration.
That's a consideration for the UI framework selected though - need to be possible to contribute UI content through a plugin.
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: Some refactoring [was Re: [DISCUSS] Archiva as an OSGi OBR/EBR ]
Posted by Olivier Lamy <ol...@apache.org>.
Hello
2011/5/2 Brett Porter <br...@apache.org>:
>
> On 03/05/2011, at 1:18 AM, Olivier Lamy wrote:
>
>> Hello,
>> Looks to be a nice feature.
>>
>> But more generally could we think about some other refactoring ?
>> I have some ideas :
>> * ui , move to an other framework I have in mind : gwt, vaadin ....
>> (it looks ace use vaadin ?)
>
> I think this is a good idea - though the more important prerequisite is to pull any functional code that's embedded in the current UI out so you can deploy a working Archiva without the webapp (if it were a set of OSGi bundles, or a thinner webapp that just has the REST/WS layer). One of the important changes that is still in progress is to be able to run Archiva with less of it's stuff enabled - e.g. just a thin proxy on your localhost, but the full app somewhere else.
>
> If we can do that split, then you can keep the current UI working through releases while a new one is built up.
>
> I'm open to either Vaadin or GWT. Haven't evaluated them myself. They seem the two best choices. I'm also interested in Sling (which may be complementary), since it's very REST oriented and could make it very easy to deal with custom content.
>
Vaadin looks fine for me too (and as ACE use it it will be probably
easier for integration)
>> * removing all the current plexus(-spring) old components to real/only
>> spring components (this could be already done in trunk ? ) (or an
>> other container ?)
>
> Been meaning to do that for a while. The sooner the better...
>
> I tend to prefer Guice more, but Spring is what we have now, but all the programming is in Plexus :)
Agree too for Guice. And IMHO will probably easier to integrate maven3
and indexer apis.
And if we need some spring components (there is a guice-spring integration).
Sure we can certainly remove all the old plexus "goodies" :-).
Using @inject for "smooth" move to an other container (we need at
least upgrade to Spring 3.x )
I can definitely start (as I have some karma in redback scm) with
redback and the old plexus components we are still using.
An other idea I have : it's a plugin mechanism (with some "extension
points") to easily enhance archiva.
And if we use an osgi "infra", this plugin mechanism will be easier to
integrate (hot reload etc...)
>
>> * remove redback and use something else for authz and role management (shiro ? )
>
> That's also been on the TODO list for some time, though I think we want to make sure we don't lose any functionality along the way. Maybe one option is for Redback to be layered as well - remove large bits of it's internals and replace with Shiro, then split the "content" part up so that it's not so dependant on Struts. It could again keep working while an alternative was built...
>
>>
>> WDYT ?
>
> Glad to see all the interest! Let me know how I can help you get started :)
>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
>
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
Re: Some refactoring [was Re: [DISCUSS] Archiva as an OSGi OBR/EBR ]
Posted by Brett Porter <br...@apache.org>.
On 03/05/2011, at 1:18 AM, Olivier Lamy wrote:
> Hello,
> Looks to be a nice feature.
>
> But more generally could we think about some other refactoring ?
> I have some ideas :
> * ui , move to an other framework I have in mind : gwt, vaadin ....
> (it looks ace use vaadin ?)
I think this is a good idea - though the more important prerequisite is to pull any functional code that's embedded in the current UI out so you can deploy a working Archiva without the webapp (if it were a set of OSGi bundles, or a thinner webapp that just has the REST/WS layer). One of the important changes that is still in progress is to be able to run Archiva with less of it's stuff enabled - e.g. just a thin proxy on your localhost, but the full app somewhere else.
If we can do that split, then you can keep the current UI working through releases while a new one is built up.
I'm open to either Vaadin or GWT. Haven't evaluated them myself. They seem the two best choices. I'm also interested in Sling (which may be complementary), since it's very REST oriented and could make it very easy to deal with custom content.
> * removing all the current plexus(-spring) old components to real/only
> spring components (this could be already done in trunk ? ) (or an
> other container ?)
Been meaning to do that for a while. The sooner the better...
I tend to prefer Guice more, but Spring is what we have now, but all the programming is in Plexus :)
> * remove redback and use something else for authz and role management (shiro ? )
That's also been on the TODO list for some time, though I think we want to make sure we don't lose any functionality along the way. Maybe one option is for Redback to be layered as well - remove large bits of it's internals and replace with Shiro, then split the "content" part up so that it's not so dependant on Struts. It could again keep working while an alternative was built...
>
> WDYT ?
Glad to see all the interest! Let me know how I can help you get started :)
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: Some refactoring [was Re: [DISCUSS] Archiva as an OSGi OBR/EBR ]
Posted by Emmanuel Venisse <em...@gmail.com>.
On Mon, May 2, 2011 at 5:18 PM, Olivier Lamy <ol...@apache.org> wrote:
> Hello,
> Looks to be a nice feature.
>
> But more generally could we think about some other refactoring ?
> I have some ideas :
> * ui , move to an other framework I have in mind : gwt, vaadin ....
> (it looks ace use vaadin ?)
> * removing all the current plexus(-spring) old components to real/only
> spring components (this could be already done in trunk ? ) (or an
> other container ?)
> * remove redback and use something else for authz and role management
> (shiro ? )
>
> WDYT ?
>
Great idea.
I'm in favor of GWT instead of Vaadin.
With GWT, it is easy to develop UI with the uibinder with html templates
Vaadin send lot od data and presentation over the network for each user
actions.
Emmanuel
>
> --
> Olivier Lamy
> http://twitter.com/olamy
> http://www.linkedin.com/in/olamy
>
> 2011/5/2 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> > Hi Wendy,
> >
> > thanks for the update.
> >
> > So it seems that the need is there :)
> >
> > I have checkout the sources but didn't see anything looking like OBR
> > (repository.xml management, etc).
> > So maybe the work didn't start yet.
> >
> > I'm quite sure that Archiva could be a great EBR, which can be very
> helpful
> > for Apache projects such as ServiceMix, Karaf, and the other ones powered
> by
> > Karaf (like Geronimo).
> >
> > Regards
> > JB
> >
> > On 05/02/2011 03:26 PM, Wendy Smoak wrote:
> >>
> >> On Mon, May 2, 2011 at 9:15 AM, Jean-Baptiste Onofré<jb...@nanthrax.net>
> >> wrote:
> >>
> >>> I wonder what do you think about enhancing Archiva to act as an EBR
> >>> (Enterprise Bundle Repository).
> >>
> >> Sounds like fun. :) I know it (or something similar, I'm not familiar
> >> with the details of OSGi) has come up for discussion before and there
> >> was interest, [1] but I don't think the work was ever finished.
> >>
> >> [1]
> >>
> http://mail-archives.apache.org/mod_mbox/archiva-dev/200812.mbox/%3C4949EF39.3020807@atlassian.com%3E
> >>
> >
>
RE: Some refactoring [was Re: [DISCUSS] Archiva as an OSGi OBR/EBR ]
Posted by Randy Kamradt <Ra...@jda.com>.
If you decide that GWT is the way to go, I'd like to help out on that. I've been in the trenches for the last three years as a technical lead on a large GWT project, and I'd like to be able to use that experience to give back to Archiva, which we use in our development environment.
-----Original Message-----
From: Olivier Lamy [mailto:olamy@apache.org]
Sent: Monday, May 02, 2011 8:19 AM
To: dev@archiva.apache.org
Subject: Some refactoring [was Re: [DISCUSS] Archiva as an OSGi OBR/EBR ]
Hello,
Looks to be a nice feature.
But more generally could we think about some other refactoring ?
I have some ideas :
* ui , move to an other framework I have in mind : gwt, vaadin ....
(it looks ace use vaadin ?)
* removing all the current plexus(-spring) old components to real/only
spring components (this could be already done in trunk ? ) (or an
other container ?)
* remove redback and use something else for authz and role management (shiro ? )
WDYT ?
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
2011/5/2 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> Hi Wendy,
>
> thanks for the update.
>
> So it seems that the need is there :)
>
> I have checkout the sources but didn't see anything looking like OBR
> (repository.xml management, etc).
> So maybe the work didn't start yet.
>
> I'm quite sure that Archiva could be a great EBR, which can be very helpful
> for Apache projects such as ServiceMix, Karaf, and the other ones powered by
> Karaf (like Geronimo).
>
> Regards
> JB
>
> On 05/02/2011 03:26 PM, Wendy Smoak wrote:
>>
>> On Mon, May 2, 2011 at 9:15 AM, Jean-Baptiste Onofré<jb...@nanthrax.net>
>> wrote:
>>
>>> I wonder what do you think about enhancing Archiva to act as an EBR
>>> (Enterprise Bundle Repository).
>>
>> Sounds like fun. :) I know it (or something similar, I'm not familiar
>> with the details of OSGi) has come up for discussion before and there
>> was interest, [1] but I don't think the work was ever finished.
>>
>> [1]
>> http://mail-archives.apache.org/mod_mbox/archiva-dev/200812.mbox/%3C4949EF39.3020807@atlassian.com%3E
>>
>