On Wed, 17 Apr 2002, David Jencks wrote:

> Maybe I missed some commits... but I didn't notice these going into
> Branch_3_0...

I am the one who missed something, David. Completely overlooked this
issue, thanks for pointing it out.

> Are you keeping Branch_3_0 and HEAD in synch?  My impression was these are
> bug fixes that we want in 3.0 final release?

I forgot to keep these branches in synch, sorry. I actually must learn
how to do it, my CVS knowledge does not go that far yet.

> Maybe we should run some kind of daily diff between the branches to keep
> track of how well in synch they are?

This would certainly help detecting mistakes like mine.

Cheers,

Francisco

> 
> Thanks
> david jencks
> 
> On 2002.04.17 10:06:38 -0400 Francisco Reverbel wrote:
> > Hi Claudio & Jason,
> > 
> > On Wed, 17 Apr 2002, Vesco Claudio wrote:
> > 
> > > Until yesterday these properties were setted (CVS HEAD tuesday)
> > > 
> > > In my system at work these properties does not resolve the problems
> > (Windows
> > > NT 4.0 + sun jdk 1.4)
> > > 
> > > In current implementation of jacorb we need to load the
> > > org.omg.CosNaming._NamingContextExtSub from jacorb.jar and not from
> > boot
> > > classes, I think.
> > 
> > You're right, Claudio. I saw the same thing on Linux + jdk 1.4. 
> > I've just commited a new version of jacorb.jar that should fix this.
> > It should allow you to get rid of the Xbootclasspath hack.
> > 
> > Some messages ago I've mentioned to Jason that a patch on jacorb.jar
> > would be needed. Then I redone my tests and the patch seemed 
> > unneccessary. I was wrong... The patch on jacorb.jar was not needed  
> > for jdk 1.3, but it is required for jdk 1.4.
> > 
> > Please try the patched version of jacorb.jar in CVS HEAD, Claudio.
> > Let me know if it works on NT without the Xbootclasspath hack.
> > 
> > The IIOP stuff is now a separate service, which sets the system props 
> > it needs. Just committed this change to CVS. So please forget about 
> > all my "-Dorg.omg.CORBA.ORBClass=org.jacorb.orb.ORB ..." crap. 
> > 
> > But IBM VMs still need to be handled as a special case. If we do not 
> > want IBM VM users to be required to say
> > 
> >       export JBOSS_CLASSPATH=$JBOSS_HOME/lib/jacorb.jar
> > 
> > before they start JBoss, then we need to change run.sh to do it for 
> > them.
> > 
> > Cheers,
> > 
> > Francisco
> > 
> > > 
> > >   Claudio
> > > 
> > > > -----Original Message-----
> > > > From:   Jason Dillon [SMTP:[EMAIL PROTECTED]]
> > > > Sent:   Tuesday, April 16, 2002 11:54 PM
> > > > To:     Francisco Reverbel
> > > > Cc:     Scott M Stark; [EMAIL PROTECTED]
> > > > Subject:        Re: [JBoss-dev] RC1 release branch occuring at 00:00
> > > > 
> > > > >
> > > > >
> > > > >-Dorg.omg.CORBA.ORBClass=org.jacorb.orb.ORB
> > > > >  -Dorg.omg.CORBA.ORBSingletonClass=org.jacorb.orb.ORBSingleton
> > > > >
> > > > 
> > > > Any reason why the service can not set these props?
> > > > 
> > > > >If the JVM is an IBM one I also add $JBOSS_HOME/lib/jacorb.jar to 
> > > > >the classpath. 
> > > > >
> > > > 
> > > > Why the special case for IBM?
> > > > 
> > > > --jason
> > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > 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