Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Received-SPF: pass (nike.apache.org: domain of jeff.ramsdale@gmail.com
 designates 209.85.220.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1327338085.15308.53.camel@cameron>
References: <4F1B8858.1050900@zeus.net.au>
	<1327338085.15308.53.camel@cameron>
Date: Mon, 23 Jan 2012 11:45:42 -0800
Message-ID: 
 <CACf_hY2P-DKg90uUD1HCg+j+7fnXbtOX2-hrKRStY3zZm8yd0Q@mail.gmail.com>
Subject: Re: Surrogate
From: Jeff Ramsdale <jeff.ramsdale@gmail.com>
To: dev@river.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Maven archetypes are the way to go. IDE agnostic and all IDEs support
Maven. Dennis Reedy with Rio has done a lot of work with Maven and
Jini services, using multi-module projects to write services, keeping
interface, proxy, service, and UI classpaths distinct and managing
dependencies, etc. It's a huge improvement over building multiple jars
from the same batch of code using classdep-type approaches.

-jeff

On Mon, Jan 23, 2012 at 9:01 AM, Greg Trasuk <trasukg@stratuscom.com> wrote=
:
>
> On Sat, 2012-01-21 at 22:54, Peter Firmstone wrote:
>> Greg,
>>
>> Are there any areas where you could use some help with the Surrogate
>> implementation?
>>
>> This year, we could make an impact with fresh releases for River,
>> Surrogate and the LDJ Kit.
>>
>> Cheers,
>>
>> Peter.
>
> Well, there's probably lot's to do, but I'm thinking it's best if I
> finish off =A0the "first-cut" myself (it's one of those "not sure of the
> architecture til the first pass is done" things). =A0There's really only
> the security manager integration left to make it a functional container
> (as it sits in the source tree now, it can host Reggie successfully,
> including hosting the codebase server). =A0I'm planning on working on it
> this week and part of next week, so with some luck, it'll be ready for
> demo soon. =A0Once the first cut is done, then we'll have all kinds of
> usability features that folks can dig in to.
>
> I'll tell you what the outside world really needs, though: IDE
> integration. =A0We need to get to the point where you can go to Netbeans
> and select "New...Jini Service Project" and then go into your web app
> and select "New...Jini client".
>
> Anybody interested in Netbeans or Eclipse integration? =A0My personal
> taste is for Netbeans, and I suspect it'll be relatively easy to add in
> a Jini project template, given the Ant-driven nature of it, but I
> haven't looked too deeply.
>
> Cheers,
>
> Greg.
>
>