contribution in the project
by Stefano Maestri
Hi folks,
my name is Stefano Maestri, I'm a contributor of overlord project. In
fact Overlord just on its kickoff and one of the most important building
block of soa governance is a repository to store services artifacts.
As I described in this post
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146445#4146445
one of the fist things I'd like to contribute is DNA project, since it
would become our primary repository as Mark Little suggested me.
Well, I took a look to the code and wiki, and I generally understand
architecture and code. Of course I have to make my had dirty to go in
deep and full understand both. Where can I start? Ideally I would lend
and hand with jcr and federated jcr, but of course it's better you
suggest areas where you need help and eventually specific issues.
I took a look to Jira, and I see a lot of open unassigned issues, but I
need an help to select right ones.
Are there a public irc channel where we can discuss about? It would be
an easier media for me at the beginning to better understand your code
and make effective changes, since it's better than email for question
and answer. I'm available to be contacted also by IM (send me a private
mail and I'll get you back my contacts).
Thanks for your time, and congrats for the project!! It's really
exciting and I can see a lot of possible application.
have fun
--
bye
Stefano
www.javalinux.it www.wibo.it
17 years, 12 months
Latest status
by Randall Hauch
It looks like we're progressing nicely for the 0.1 release, which I
hope will occur next week. The last big item is the Getting Started
document, which I'm working on now. That document will (among other
things) walk through an example that uses the sequencing framework
with an existing JCR repository, and how to write and use a
sequencer. I'll be looking for some reviewers next week.
We've recently added a mailing list for automatic notification of SVN
commits (dna-commits(a)lists.jboss.org), another for JIRA issue changes (dna-issues(a)lists.jboss.org
), and a third for announcements (dna-announce(a)lists.jboss.org). For
the complete list, see http://www.jboss.org/dna/lists.html.
Also, we have Hudson running continuous integration jobs, and the
results are available at http://hudson.jboss.org/hudson/job/DNA%20continuous%20on%20JDK1.5/
. Hudson polls SVN (about every 15 minutes), and if there are changes
it will do "mvn package" to build all the projects and run the unit
tests. Note that the unit tests in the "dna-integration-tests"
project are now run only during the "integration-test" phase, which we
run during our nightly build in Hudson (results are available at http://hudson.jboss.org/hudson/job/DNA%20nightly%20integration%20on%20JDK...)
. Right now I've configured these jobs to email this list with any
failed builds; hope that's okay.
Finally, if you haven't taken a look at JIRA lately, please look at
our roadmap (http://jira.jboss.org/jira/browse/DNA?report=com.atlassian.jira.plugin.sy...
). The next release will be focusing on the federation engine and
additional sequencers. Please pass any thoughts along to this list.
More to come next week!
Randall
18 years
Refactored projects
by Randall Hauch
I've refactored some of the projects, in preparation for future work.
"dna-services" was renamed to "dna-repository", and a few of the
interfaces related to sequencers were moved to a new project "dna-
spi". Packages within these projects were also renamed accordingly.
I suggest updating all of "trunk" (using 'svn' command line tool), and
then adjusting your Eclipse environments by closing "dna-services" and
importing "dna-repository" and "dna-spi".
We'll be renaming "dna-common" to "dna-core" tomorrow AM (CDT), and
that will have a major impact on the code base. Hopefully, that's the
last significant refactoring before the 0.1 release.
Randall
18 years
What michael is up to lately
by Michael Neale
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
18 years
