Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Change package name 'com.sun.jini.tool' to
 'org.apache.river.tool'?
From: Greg Trasuk <trasukg@stratuscom.com>
In-Reply-To: <BE56BB29-C6AD-4F17-A06C-00681C709F74@stratuscom.com>
Date: Thu, 20 Nov 2014 11:03:55 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4223CFB4-FEB8-461F-8BDF-2DD4437088C5@stratuscom.com>
References: <BE56BB29-C6AD-4F17-A06C-00681C709F74@stratuscom.com>
To: dev@river.apache.org


Actually, I had a better idea.

How about if I pull out the =91tools=92 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 =91river-tools=92
- Create a Maven project (I=92ll have a look at the modularization that =
Dennis did, I suspect this is already done) in that repository
- Integrate Peter=92s 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 =
Central=20
- 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 =
that uses the same tool, and one less piece of build system confusion to =
put off 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:
>=20
> I=92m working on getting the build system, particularly =
=91classdepandjar=92 to work under JDK8.  While I=92m in there, I=92m =
wondering if I should rename the affected package, =91com.sun.jini.tool=92=
, to =91org.apache.river.tool=92 or some such thing.
>=20
> Any opinions?  I would have to change the reference to classdepandjar =
in 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 =
=91com.sun.jini.tool=92 so as not to affect build scripts.
>=20
> Opinions?
>=20
> Cheers,
>=20
> Greg Trasuk
>=20