Hi Niclas,
Niclas Hedhman wrote:
> On Monday 23 July 2007 03:14, Jochen Wiedmann wrote:
>> On 7/22/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
>>> Last Incubating release - the com.sun.jini classes are the wrappers to
>>> the org.apache.river classes.
>> At that point (I don't see a necessity fo
Jim Hurley wrote:
> On Jul 23, 2007, at 12:30 PM, Robert Burrell Donkin wrote:
>> On 7/23/07, Jim Hurley <[EMAIL PROTECTED]> wrote:
>>> On Jul 22, 2007, at 2:15 PM, Ted Husted wrote:
>>> > IMHO, unless there are trademark or licensing issues involved,
>>> :
>>>
>>> I don't believe there are issues
On Jul 23, 2007, at 12:30 PM, Robert Burrell Donkin wrote:
On 7/23/07, Jim Hurley <[EMAIL PROTECTED]> wrote:
On Jul 22, 2007, at 2:15 PM, Ted Husted wrote:
> IMHO, unless there are trademark or licensing issues involved,
:
I don't believe there are issues involved - Sun filed a Software
Grant
On Tuesday 24 July 2007 00:30, Robert Burrell Donkin wrote:
> On 7/23/07, Jim Hurley <[EMAIL PROTECTED]> wrote:
> > On Jul 22, 2007, at 2:15 PM, Ted Husted wrote:
> > > IMHO, unless there are trademark or licensing issues involved,
> >
> > I don't believe there are issues involved - Sun filed a Sof
On 7/23/07, Jim Hurley <[EMAIL PROTECTED]> wrote:
On Jul 22, 2007, at 2:15 PM, Ted Husted wrote:
> IMHO, unless there are trademark or licensing issues involved,
:
I don't believe there are issues involved - Sun filed a Software Grant
to contribute the code to the Foundation.
does the grant co
On Jul 22, 2007, at 2:15 PM, Ted Husted wrote:
IMHO, unless there are trademark or licensing issues involved,
:
I don't believe there are issues involved - Sun filed a Software Grant
to contribute the code to the Foundation.
-Jim
---
On 7/22/07, Ted Husted <[EMAIL PROTECTED]> wrote:
IMHO, unless there are trademark or licensing issues involved,
do we have the required trademark license from sun?
- robert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For add
On Monday 23 July 2007 03:14, Jochen Wiedmann wrote:
> On 7/22/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> > Last Incubating release - the com.sun.jini classes are the wrappers to
> > the org.apache.river classes.
>
> At that point (I don't see a necessity for the previous steps, btw, it
> only
How about some tools to make the migration easier? I remember some like this
when the com.sun.swing got changed
(http://www.ternent.com/tech/regexp.html). Maybe we should whip up a
retroweaver like tool for migration efforts
(http://retroweaver.sourceforge.net/) - to support existing codebases.
I
I disagree .. and we've had this conversation here before; with ActiveMQ
IIRC. Org.apache.* is a way to let the programmer know that they're using
an Apache product and IMO its important to make that transition as part of
incubation.
I'm +1 to the staged model Niclas proposed.
Sanjiva.
Willi
On 7/22/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
Last Incubating release - the com.sun.jini classes are the wrappers to the
org.apache.river classes.
At that point (I don't see a necessity for the previous steps, btw, it
only complicates things, IMO) I'd also rec
Ted Husted wrote:
> IMHO, unless there are trademark or licensing issues involved, there
> should be no "Apache rules" about Java package naming schemes. Package
> names are an arbitrary implementation detail, and the one and only
> concern should be what makes the most sense to the individual
> co
IMHO, unless there are trademark or licensing issues involved, there
should be no "Apache rules" about Java package naming schemes. Package
names are an arbitrary implementation detail, and the one and only
concern should be what makes the most sense to the individual
community. When it comes to i
On Sunday 22 July 2007 17:52, Dan Creswell wrote:
> We would appreciate some clarification in respect of the above and some
> guidance on what the minimum requirements might be. For example would
> it be acceptable to create a compatibility layer and thus, for at least
> this first release, have b
Hello all,
After much grinding of gears, the Apache River project has now received
from Sun all the relevant source code pertaining to the Jini technology.
The process of source code handover has taken a substantial amount of
time and thus we (the Apache River project) propose to issue a release
15 matches
Mail list logo
