Sorry for the delay in responding.
Thanks Jukka -- the plan is to bring in the code as is
and make the changes you described (essentially
com.sun.* --> org.apache.river.*).
Question, though -- is it required that we make that
change before we make an initial release?
thanks -Jim
On Jun 1, 2007, at 8:14 AM, Craig L Russell wrote:
+1
It's ok to bring in source code with the original package name and
do the rename/move in the Apache repository. Or rename it
beforehand, your choice.
Just remember to rename it to the official apache names before you
make a release! ;-)
Craig
On Jun 1, 2007, at 1:13 AM, Dan Creswell wrote:
John McClain - Sun Microsystems, Inc. wrote:
Jukka Zitting wrote:
Hi,
On 5/31/07, Gianugo Rabellino <[EMAIL PROTECTED]> wrote:
Before formally stating my +1 (I have no objections), and with
a lot
of excuses from my part given I probably missed that bit, I see
that
no contribution is under an org.apache namespace. Is this the
way it
was agreed to proceed?
There was some discussion earlier on how to handle the package
namespaces with most of the specifications in net.jini, but some of
the essential parts also in com.sun.jini. I think (didn't pay
too much
attention at the time, so I might be wrong) the rough consensus
was to
keep net.jini as the spec namespace and to migrate from
com.sun.jini
to org.apache.river by time as the potential backwards
compatibility
issues are sorted out. I think it makes sense to bring the code in
as-is and sort out the migration to org.apache before the first
release.
This is my memory also
+1
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!
