That is what is happening. I think it's possible that the outdated build of openejb is being refreshed by someone or some process, since a couple of days ago when I was so incautious as to build geronimo without -o maven pulled down a copy of openejb with the incorrect class references. I think the copy of openejb pulled down had been built within the last 2 days, although I haven't investigated thoroughly.

At the moment I am not a fan of snapshots on remote repositories. I'd prefer all projects to use subversion and to put versions labeled with the revision number on the repo, and dependencies to have a range of acceptable revisions. Of course this proposal undoubtedly has plenty of problems of its own.

Even though it is quite inconvenient I recommend building at least geronimo, tranql, tranql-connector, and openejb yourself. You can modify the uber-build to do this by simply deleting the activemq and howl directories after checkout. Also, I update each project by hand when necessary rather than using the m:update.

thanks
david jencks

On Dec 5, 2004, at 6:26 AM, anita kulshreshtha wrote:

Hi
    I do not build OpenEJB etc. from the source. Is it
possible that I am getting a different version of
OpenEJB in which
org.openejb.deployment.OpenEJBMOduleBuilder still
references
org.apache.geronimo.security.GeronimoSecurityException?
Any help will be appreciated.

Thanks
Anita
--- anita kulshreshtha <[EMAIL PROTECTED]> wrote:

Hi
   I have been having the same problem.  I have
rebuilt many times. The
geronimo-common-1.0-SNAPSHOT.jar does have
GeronimoSecurityException class. I am using winXP,
JDK1.5.
Thanks
Anita
--- Aaron Mulder <[EMAIL PROTECTED]>
wrote:

On Fri, 3 Dec 2004, David Blevins wrote:



+org/apache/geronimo/security/GeronimoSecurityException

This class was moved, no?

It was moved to Geronimo common... (which would
be
unavailable
why?)  I haven't seen this problem in my build
environments.  Is it
possible that we haven't pushed new JARs since the
move so this build
doesn't have the class at all?  I'll try to
manually
push JARs this
morning.

The build script i have has been dying like
crazy
as every few days or
week the build get's wedged loading plans in
assembly or in network
tests and just hangs. Don't think I've seen it
stay running longer
than 10 days.

I'd sure like to see some revisions to the networking code that would cause it to not wedge! I think Hiram and
Alan
had some thoughts on
that...

Aaron

P.S. Next time, could you send your commentary
without the 2.4MB log file
that we just got twice already?  Thanks.  (I
haven't
moved to GMail yet)



                
__________________________________
Do you Yahoo!?
Send a seasonal email greeting and help others. Do
good.
http://celebrity.mail.yahoo.com



                
__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250




Reply via email to