Kelvin summarized the chat nicely but I'd like to add a little
background.
Cutting the branch for SDO was a little fiddly and if we're going to
do this on a regular basis then the process should be simpler. We can
script it, but scripting something that's fairly fragile is not going
to be
FYI
Jeremy and I had a chat on IRC and here is the outcome, which Jeremy is
going to act on while I get some sleep
spec/sdo stays where it is
samples/sdo gets moved to sdo/samples
ditto distribution/sdo
the sdo source distribution is split into a spec archive and an
implementastion archive (imp
Jeremy,
yes EMF 2.2.1 is available, and I was looking to sort that on Friday
afternoon when I realised I had missed the samples from the distribution.
This again reflects the fact that our sub project organisation is a bit
awkward, However, I do recall a fairly extended mail exchange about how t
If we are going to start releasing these separately (or really just
being prepared to) then I think this would be worth doing. It's a
fairly simple change to do even now so should we do this for this
release?
Speaking of which, it looks like EMF 2.2.1 is available from their
maven repo. A
I have made a branch for SDO at
http://svn.apache.org/repos/asf/incubator/tuscany/branches/sdo-java-M2/which
I thought it might be worth drawing your attention to, since it might
be helpful that we had a common approach across the projects. I think we
are going to want separate branches per proje
