Re: qa-refactor-namespace observations

No problem since keeping net.jini was a deliberate decision. On 6/1/2015 4:52 PM, Dennis Reedy wrote: On Mon, Jun 1, 2015 at 7:48 PM, Patricia Shanahan wrote: On 6/1/2015 4:33 PM, Dennis Reedy wrote: Patricia, I just did a clean checkout of the qa-refactor-namespace branch, and I do not se

Re: qa-refactor-namespace observations

+1 net.ini stays! Greg Trasuk > On Jun 1, 2015, at 7:52 PM, Dennis Reedy wrote: > > On Mon, Jun 1, 2015 at 7:48 PM, Patricia Shanahan > wrote: > >> On 6/1/2015 4:33 PM, Dennis Reedy wrote: >> >>> Patricia, >>> >>> I just did a clean checkout of the qa-refactor-namespac

Re: qa-refactor-namespace observations

On Mon, Jun 1, 2015 at 7:48 PM, Patricia Shanahan wrote: > On 6/1/2015 4:33 PM, Dennis Reedy wrote: > >> Patricia, >> >> I just did a clean checkout of the qa-refactor-namespace branch, and I do >> not see any references of old package names in package >> org.apache.river.example.hello.I'm lookin

Re: qa-refactor-namespace observations

On 6/1/2015 4:33 PM, Dennis Reedy wrote: Patricia, I just did a clean checkout of the qa-refactor-namespace branch, and I do not see any references of old package names in package org.apache.river.example.hello.I'm looking for com.sun.jini, perhaps I'm missing something. I was also looking for

Re: qa-refactor-namespace observations

Patricia, I just did a clean checkout of the qa-refactor-namespace branch, and I do not see any references of old package names in package org.apache.river.example.hello.I'm looking for com.sun.jini, perhaps I'm missing something. I do see an issue with qa/jtreg/net/jini/jeri/transport/multihomed

qa-refactor-namespace observations

I have checked out the qa-refactor-namespace branch, and done some initial checks. I noticed a couple of possible issues: Extensive use of old package names in package org.apache.river.example.hello. qa contains a binary file, tmp, that includes "com.sun". Should it really be checked in to S