You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Peter <ji...@zeus.net.au> on 2014/11/20 06:15:18 UTC
Re: Change package name 'com.sun.jini.tool' to
'org.apache.river.tool'?
The code in qa-refactor has been upgraded to support jdk8, could backport that if you want.
No objection to changing package name.
Cheers,
Peter.
----- Original message -----
> Hi all:
>
> I’m working on getting the build system, particularly ‘classdepandjar’
> to work under JDK8. While I’m in there, I’m wondering if I should
> rename the affected package, ‘com.sun.jini.tool’, to
> ‘org.apache.river.tool’ or some such thing.
>
> 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
> ‘com.sun.jini.tool’ so as not to affect build scripts.
>
> Opinions?
>
> Cheers,
>
> Greg Trasuk
>
Re: Change package name 'com.sun.jini.tool' to
'org.apache.river.tool'?
Posted by Peter <ji...@zeus.net.au>.
I haven't tested new language features, it's only been modified to allow River to build on JDK8
----- Original message -----
> The code in qa-refactor has been upgraded to support jdk8, could
> backport that if you want.
>
> No objection to changing package name.
>
> Cheers,
>
> Peter.
>
> ----- Original message -----
> > Hi all:
> >
> > I’m working on getting the build system, particularly ‘classdepandjar’
> > to work under JDK8. While I’m in there, I’m wondering if I should
> > rename the affected package, ‘com.sun.jini.tool’, to
> > ‘org.apache.river.tool’ or some such thing.
> >
> > 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
> > ‘com.sun.jini.tool’ so as not to affect build scripts.
> >
> > Opinions?
> >
> > Cheers,
> >
> > Greg Trasuk
> >
>