Hi alls!

For the testsuite. In my local cvs repository I have removed the iiop tests
from stress test case and added in a new target which sets the properties to
make running the iiop part. These test are called from tests target. (I have
written this some mails ago :-) )

When I have time I retest alls with jdk 1.3 and if it works then I'll submit
the patch or, if you like, I'll commit it directly.

Francisco, can you patch org.jboss.iiop.WebCL?

        claudio

> -----Original Message-----
> From: Francisco Reverbel [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, April 15, 2002 5:31 PM
> To:   David Jencks
> Cc:   [EMAIL PROTECTED]
> Subject:      Re: [JBoss-dev] RC1 release branch occuring at 00:00
> 
> On Mon, 15 Apr 2002, David Jencks wrote:
> 
> > Sorry, I assumed that ./build.sh clean main would build everything,
> > especially since the iiop tests appear to be running (and failing)
> 
> I was not aware the iiop tests were running by default. They shouldn't,
> because right now they require three special actions:
> 
>  1 - The RMI/IIOP MBean entry in jboss-service.xml must to be 
>      uncommmented.
> 
>  2 - JBoss must be started with additional options:
> 
>      export JBOSS_CLASSPATH=$JBOSS_HOME/lib/jacorb.jar
>      export JAVA_OPTS="-Dorg.omg.CORBA.ORBClass=org.jacorb.orb.ORB
> -Dorg.omg.CORBA.ORBSingletonClass=org.jacorb.orb.ORBSingleton"
> 
>  3 - A special target (iiop-test) must be used to run iiop tests.
> 
> If you do these things then the iiop tests should not fail.
> 
> A question to all: Should we make 1 and 2 be the default case, so that 
> iiop tests run with no special arrangements?
> 
> > Could we perhaps have the default target compile everything, and have a
> > "core" target that compiles the things that are expected to work?  This
> > happened once before when I changed something that broke clustering and
> > didn't know it since it wasn't in the main build.
> 
> Yes, I think everything should compile by default.
> 
> Best,
> 
> Francisco
> 
> > Thanks
> > david jencks
> > 
> > On 2002.04.15 05:13:29 -0400 Scott M Stark wrote:
> > > It will have to be a seperate service release with instructions on how
> > > to incorporate because iiop is broken right now:
> > > 
> > > 
> > >     ==  Executing 'most' in module 'iiop'...
> > >     ==
> > > 
> > > _buildmagic:init:
> > > 
> > > configure:
> > > 
> > > init:
> > > 
> > > compile-classes:
> > >     [mkdir] Created dir:
> > > /home/starksm/3.0.0/jboss-all/iiop/output/classes/main
> > >     [javac] Compiling 75 source files to
> > > /home/starksm/3.0.0/jboss-all/iiop/output/classes/main
> > >
> /home/starksm/3.0.0/jboss-all/iiop/src/main/org/jboss/iiop/WebCL.java:11:
> > > cannot resolve symbol
> > > symbol  : class UnifiedClassLoader
> > > location: package system
> > > import org.jboss.system.UnifiedClassLoader;
> > >                         ^
> > >
> /home/starksm/3.0.0/jboss-all/iiop/src/main/org/jboss/iiop/WebCL.java:29:
> > > cannot resolve symbol
> > > symbol  : class UnifiedClassLoader
> > > location: class org.jboss.iiop.WebCL
> > >     public WebCL(ObjectName container, UnifiedClassLoader parent)
> > >                                        ^
> > >
> /home/starksm/3.0.0/jboss-all/iiop/src/main/org/jboss/proxy/compiler/IIOPS
> tu
> > > bCompiler.java:107: warning: org.jboss.proxy.compiler.ProxyAssembler
> in
> > > org.jboss.proxy.compiler has been deprecated
> > >    private static void generateMethodCode(ProxyAssembler asm,
> > >                                           ^
> > >
> /home/starksm/3.0.0/jboss-all/iiop/src/main/org/jboss/proxy/compiler/IIOPS
> tu
> > > bCompiler.java:107: warning: org.jboss.proxy.compiler.ProxyAssembler
> in
> > > org.jboss.proxy.compiler has been deprecated
> > >    private static void generateMethodCode(ProxyAssembler asm,
> > >                                           ^
> > >
> /home/starksm/3.0.0/jboss-all/iiop/src/main/org/jboss/proxy/compiler/IIOPS
> tu
> > > bCompiler.java:251: warning: org.jboss.proxy.compiler.ProxyAssembler
> in
> > > org.jboss.proxy.compiler has been deprecated
> > >       ProxyAssembler asm =
> > >       ^
> > >
> /home/starksm/3.0.0/jboss-all/iiop/src/main/org/jboss/proxy/compiler/IIOPS
> tu
> > > bCompiler.java:252: warning: org.jboss.proxy.compiler.ProxyAssembler
> in
> > > org.jboss.proxy.compiler has been deprecated
> > >          new ProxyAssembler(stubClassName,
> > >              ^
> > > 2 errors
> > > 4 warnings
> > > 
> > > ----- Original Message -----
> > > From: "Jason Dillon" <[EMAIL PROTECTED]>
> > > To: "Scott M Stark" <[EMAIL PROTECTED]>
> > > Cc: <[EMAIL PROTECTED]>
> > > Sent: Monday, April 15, 2002 2:01 AM
> > > Subject: Re: [JBoss-dev] RC1 release branch occuring at 00:00
> > > 
> > > 
> > > > Are you building with -Dgroups=most?
> > > >
> > > > Otherwise iiop will not be included in the build... or do you mean
> > > > instructions on how to build & configure?
> > > >
> > > > --jason
> > > >
> > > >
> > > > Quoting Scott M Stark <[EMAIL PROTECTED]>:
> > > >
> > > > >
> > > > > Then we can just post directions on how to setup and try iiop
> > > > > with the RC1 binary I'm building now. Next release it can be
> > > > > configured by default.
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Jboss-development mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > > 
> > > 
> > 
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > 
> 
> 
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to