Thanks for sending this out, Michael. I hope to get started on the federation (especially SCM) capability in the next few weeks, after the initial release goes out the door. Are you using any SVN library that suits your needs? On Apr 1, 2008, at 9:46 PM, Michael Neale wrote: > > > > 2 things: > > * drools-repository (which is just back end code, only depends on > jackrabbit, not web component) to be extracted, and "genericised" - > this could serve as a very useful test bed for the DNA repository back > end, at the very least, as it excercises all the features that we will > use in the SOA repository - that are needed by JCR (ergo, DNA > repository). > > * Whilst hopefully DNA repository can give us SCM sync ability > (ClearCase, SVN, CVS etc etc) - we are building a component to allow > IDEs, Command line etc to add/list/remove/update content from SOA > repository (like a Very Simple Version System) - so we can edit/SCM > file artifacts in the IDE (eg rules, interface contracts) yet have > them available on the web and managed in the SOA repository (keep devs > and managers happy). > > Regards, > > -- > Michael D Neale > home: www.michaelneale.net > blog: michaelneale.blogspot.com > _______________________________________________ > dna-dev mailing list > dna-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/dna-dev >

I think it makes sense. You're basically creating a client library that does the "SCM-like" operations, and which interacts with the (remote?) Guvnor repository (server?). On Apr 8, 2008, at 4:57 PM, Michael Neale wrote: > We were using SVNKit - but for the moment, we are going to sidestep > the SVN sync directly (the code we have works, and people are free to > use it, but we may not). > > Instead, we will have a simple remote api for the repository, and have > a little client lib (and ant task) to allow SCM "like" operations on > the Guvnor repository. We have also looked at Eclipse team support, > and its possible to do this in such a way that eclipse knows about it > (so a file can also be in a regular SVN). This means we are not tied > to SVN for this feature. > > A richer SVN sync would be nice - but as you mentioned once before, > this is kind of a funciton that DNA/meta matrix could provide as a > data service, in the future. > > Does that make sense? bit hard to explain - happy to chat it out if it helps. > > > On Tue, Apr 8, 2008 at 11:04 PM, Randall Hauch <rhauch(a)redhat.com&gt; wrote: > > > Thanks for sending this out, Michael. I hope to get started on the > > federation (especially SCM) capability in the next few weeks, after the > > initial release goes out the door. Are you using any SVN library that suits > > your needs? > > > > > > > > On Apr 1, 2008, at 9:46 PM, Michael Neale wrote: > > > > > > > > > > > > > > > > 2 things: > > > > > > * drools-repository (which is just back end code, only depends on > > > jackrabbit, not web component) to be extracted, and "genericised" - > > > this could serve as a very useful test bed for the DNA repository back > > > end, at the very least, as it excercises all the features that we will > > > use in the SOA repository - that are needed by JCR (ergo, DNA > > > repository). > > > > > > * Whilst hopefully DNA repository can give us SCM sync ability > > > (ClearCase, SVN, CVS etc etc) - we are building a component to allow > > > IDEs, Command line etc to add/list/remove/update content from SOA > > > repository (like a Very Simple Version System) - so we can edit/SCM > > > file artifacts in the IDE (eg rules, interface contracts) yet have > > > them available on the web and managed in the SOA repository (keep devs > > > and managers happy). > > > > > > Regards, > > > > > > -- > > > Michael D Neale > > > home: www.michaelneale.net > > > blog: michaelneale.blogspot.com > > > _______________________________________________ > > > dna-dev mailing list > > > dna-dev(a)lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/dna-dev > > > > > > > > > > > > > > > > -- > Michael D Neale > home: www.michaelneale.net > blog: michaelneale.blogspot.com >