Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Received-SPF: pass (athena.apache.org: domain of tvhobbs@googlemail.com
 designates 209.85.214.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4223CFB4-FEB8-461F-8BDF-2DD4437088C5@stratuscom.com>
References: <BE56BB29-C6AD-4F17-A06C-00681C709F74@stratuscom.com>
	<4223CFB4-FEB8-461F-8BDF-2DD4437088C5@stratuscom.com>
Date: Thu, 20 Nov 2014 16:57:48 +0000
Message-ID: 
 <CAEDB+kU54FYvYnB_7F3HwoCgsS9Q4UMB30cMkkMFtnMQOsat0w@mail.gmail.com>
Subject: Re: Change package name 'com.sun.jini.tool' to
 'org.apache.river.tool'?
From: Tom Hobbs <tvhobbs@googlemail.com>
To: dev@river.apache.org
Content-Type: multipart/alternative; boundary=001a113dbcfc6141a705084d3a6d

--001a113dbcfc6141a705084d3a6d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I don't see why it would need a vote.

It sounds like a good plan to me.

+1 (just in case)
On 20 Nov 2014 16:06, "Greg Trasuk" <trasukg@stratuscom.com> wrote:

>
> Actually, I had a better idea.
>
> How about if I pull out the =E2=80=98tools=E2=80=99 package to a separate=
 Maven project
> and integrate the changes that Peter did on qa_refactor?  Then both the 2=
.2
> branch and qa_refactor can use the same tools.
>
> Process would be as follows:
>
> - Create a project in Apache git repo for =E2=80=98river-tools=E2=80=99
> - Create a Maven project (I=E2=80=99ll have a look at the modularization =
that
> Dennis did, I suspect this is already done) in that repository
> - Integrate Peter=E2=80=99s updates from qa-refactor (which update to use=
 asm-5 in
> classdep)
> - Do a release on river-tools, so that tools.jar can go into Maven Centra=
l
> - Remove tools packages from 2.2. branch.  Modify build to get tools.jar
> from Central rather than building it.
>         - I can update qa_refactor at the same time.
> - Roll a release of the 2.2. branch.
>
> Which will leave a 2.2. release that builds under JDK1.8, qa_refactor tha=
t
> uses the same tool, and one less piece of build system confusion to put o=
ff
> new committers.
>
> Opinions?  Does this need a vote?
>
> Cheers,
>
> Greg Trasuk.
>
> On Nov 19, 2014, at 3:19 PM, Greg Trasuk <trasukg@stratuscom.com> wrote:
>
> > Hi all:
> >
> > I=E2=80=99m working on getting the build system, particularly =E2=80=98=
classdepandjar=E2=80=99
> to work under JDK8.  While I=E2=80=99m in there, I=E2=80=99m wondering if=
 I should rename
> the affected package, =E2=80=98com.sun.jini.tool=E2=80=99, to =E2=80=98or=
g.apache.river.tool=E2=80=99 or
> some such thing.
> >
> > Any opinions?  I would have to change the reference to classdepandjar i=
n
> the build scripts, but obviously it would also affect any external build
> scripts that use it.  I suppose I could leave a wrapper class in
> =E2=80=98com.sun.jini.tool=E2=80=99 so as not to affect build scripts.
> >
> > Opinions?
> >
> > Cheers,
> >
> > Greg Trasuk
> >
>
>

--001a113dbcfc6141a705084d3a6d--