On Thu, Sep 1, 2011 at 2:11 PM, Mark H. Wood <mw...@iupui.edu> wrote:

> On Thu, Sep 01, 2011 at 01:15:14PM -0500, Tim Donohue wrote:
> > I think the type of "add-on" you are talking about is somewhat similar
> > to something Richard Rodgers has begun to develop:
> >
> > https://jira.duraspace.org/browse/DS-976
>
> Hmmm, no, if I understand that one, they are quite different:  I want
> to build add-ons *outside of the DSpace source tree*, not scoop them
> in and rebuild the whole works.  This requires planning when designing
> the bits that are added onto:  what must be exposed to make it
> feasible to build a future add-on solely against the DSpace binary
> artifacts?
>
> (I don't think I made it clear previously that I want to build
> out-of-tree.)
>

Right, This is still a maven module.  The Addon Mechanism Richard discusses
uses a maven plugin to edit the maven reactor and persist it again to disk,
effectively, it alters your poms where required to add the addon to your
build. I hope we take a KISS approach here, I don't want alot of rules about
what an Addon is other than a Maven module that produces either a jar or an
overlay.

>
> > But, I agree with your point. It does seem like we can find ways to make
> > this easier post-1.8.0. You should be able to Install DSpace and then
> > "drop in" some add-ons & configure them as needed.
> >
> > Technically, you can basically do the "jar drop-in" thing with custom
> > Curation Tasks or separately-released Curation Tasks (like Replication
> > Task Suite, https://jira.duraspace.org/browse/DS-876).
>
>
Well, we need a framework for doing this... Ironically, this is what OSGi
is,  I don't think folks get that,  we should be watching DuraCloud and
Sakai CLE (http://sakaiproject.org/sakai-cle)  both are Felix based, both
provide a framework to inject "addons" into a running instance of the
application.  I hope we do not reinvent the wheel simply because we can't
grok the acronym OSGi, even the Attlasian folks get this (
http://confluence.atlassian.com/display/DEVNET/Atlassian+Plugin+SDK+Documentation
)

The current proposed work in the JIRA ticket is still too minimal for our
use, we do not have simple drop-ins, the transitive dependency analysis
"needs to happen" for our addon products to properly evaluate the required
dependencies from our local maven repositories.

We need to have our addons inserted as dependencies into dspace/lib, sword,
xmlui, oai, etc and our maven repositories inserted into the dspace and
modules pom's to support the deployment and update of our addons during
normal DSpace build processes.

-- 
Mark R. Diggory
@mire - www.atmire.com
2888 Loker Avenue East - Suite 305 - Carlsbad - CA - 92010
Esperantolaan 4 - Heverlee 3001 - Belgium
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to