9 Replies Latest reply on Mar 6, 2008 5:24 AM by trustin

A compilation error in Remoting 2

trustin Mar 3, 2008 3:54 AM

'ant test' fails with the following output:

[javac] /home/trustin/workspace/checkout/jboss/remoting2/src/tests/org/jboss/test/remoting/transport/bisocket/BisocketTestCase.java:1813: cannot find symbol
 [javac] symbol : method setDisconnectTimeout(int)
 [javac] location: class org.jboss.remoting.Client
 [javac] client.setDisconnectTimeout(0);
 [javac] ^
 [javac] Note: Some input files use unchecked or unsafe operations.
 [javac] Note: Recompile with -Xlint:unchecked for details.
 [javac] 1 error
 [javac] 5 warnings

It seems like org.jboss.remoting.Client doesn't have such a method. Is it gone, or is something not checked in yet?

1. Re: A compilation error in Remoting 2

trustin Mar 3, 2008 4:09 AM (in response to trustin)
No, I'm checking out from the trunk:
https://svn.jboss.org/repos/jbossremoting/remoting2/trunk
Actions
2. Re: A compilation error in Remoting 2

dmlloyd Mar 3, 2008 8:01 AM (in response to trustin)

You should be working from the "2.x" branch. The "trunk" branch is sort of dead at this point.
Actions
3. Re: A compilation error in Remoting 2

trustin Mar 3, 2008 8:35 AM (in response to trustin)

doh! Thanks for the information. Then what do you think about replacing trunk with brahches/2.x? Is there any reason that we are keeping something dead?
Actions
4. Re: A compilation error in Remoting 2

dmlloyd Mar 3, 2008 6:25 PM (in response to trustin)

I'm OK with that - though Ron is the one working with it on a day-to-day basis. Consider also that 3.x has its own trunk, and that chances are good that 2.4 will be the last release in the 2.x series.
Actions
5. Re: A compilation error in Remoting 2

trustin Mar 4, 2008 5:43 AM (in response to trustin)

What do you think, Ron?
Actions
6. Re: A compilation error in Remoting 2

ron_sigal Mar 4, 2008 9:45 PM (in response to trustin)

My anal retentive side is reluctant to let go of remoting2/trunk without at least looking to see if Tom Elrod added anything interesting there. Of course, I guess we could move trunk to "oldtrunk" and 2.x to trunk.
Actions
7. Re: A compilation error in Remoting 2

trustin Mar 5, 2008 2:43 AM (in response to trustin)

OK. Then what about renaming trunk to branches/oldtrunk, and branches/2.x to trunk? :)
Actions
8. Re: A compilation error in Remoting 2

dmlloyd Mar 5, 2008 7:16 PM (in response to trustin)

Seems like a lot of work for little gain, all in the name of compulsive tidiness :-)
Actions
9. Re: A compilation error in Remoting 2

trustin Mar 6, 2008 5:24 AM (in response to trustin)

Hmm it's just two commits, no? :)
Actions

Go to original post