This is caused when you don't have all of the modules checked out yet.
I believe that if you drop your current checkout and checkout again
with m:co, m:update will start working for you.
BTW I have been using m:update on my mac laptop and a windows desktop,
which is checking out
Message:
The following issue has been closed.
Resolver: David Jencks
Date: Wed, 6 Oct 2004 7:10 PM
This is actually not a dup of 365, but a parallel issue for outbound adapters.
Anyway, a similar fix was needed, don't return a NamedXAResource if the
ManagedConnection doesn't
David,
Thank you!
Toby
Hi
BTW, I find the name contextPriorityClassLoader a bit non-intuitive,
what do other app servers call this (specifically weblogic and
webshpere).
I'm still interested in this if anyone has the info...
The admin console talks about WAR Classloader Policy (Module,
Application) and Classloader
On 7/10/2004 3:34 PM, Dain Sundstrom wrote:
On Oct 6, 2004, at 5:33 PM, Dain Sundstrom wrote:
BTW, I find the name contextPriorityClassLoader a bit
non-intuitive, what do other app servers call this (specifically
weblogic and webshpere).
I'm still interested in this if anyone has the info...
For
It worked for me... but..
A bit off topic, as my problems don't have anything to do with Dain's
changes, but I have some questions on the build processing.
I tried the following (without cleaning my repository but with an empty
geronimo directory):
maven m:co
maven m:build
I
Jules Gosnell [EMAIL PROTECTED] wrote on 10/06/2004 08:21:31 PM:
[EMAIL PROTECTED] wrote:
Hi,
I am trying to get a feel for how EJB/JNDI clustering will be
implemented
in Geronimo and when it might be implemented.
I remember reading somewhere in the mail archives that the
Yuo might be interested in GERONIMO-364 in JIRA -- which is to
provide a build target to do all the downloads in one shot so the rest of
the build can be run quickly in offline mode. Dain was going to look into
it in his copious free time... :)
Aaron
On Fri, 8 Oct 2004 [EMAIL
After some thinking, I don't think this can be done directly with
maven... let me explain.
I thought we could simple do a standard reactor build (the thing that
executes maven for each sub-module) with a do nothing target such as
build:start. This would cause maven to download the
I think I missed this earlier, but how do you set your CVS account
to check out a subproject with write permissions if you use m:co? Does it
use the same properties that maven getotherprojects does?
Thanks,
Aaron
On Thu, 7 Oct 2004, Dain Sundstrom wrote:
On Oct 7, 2004, at
On Oct 7, 2004, at 12:44 PM, Dain Sundstrom wrote:
On Oct 7, 2004, at 12:30 PM, David Jencks wrote:
Right, I was trying to use a checkout from the previous version of
maven.xml. I don't know why it didn't work, but after m:co m:update
works.
Cool
Now I'm having what I consider a severe
On Oct 7, 2004, at 1:39 PM, David Jencks wrote:
On Oct 7, 2004, at 12:44 PM, Dain Sundstrom wrote:
On Oct 7, 2004, at 12:30 PM, David Jencks wrote:
Right, I was trying to use a checkout from the previous version of
maven.xml. I don't know why it didn't work, but after m:co m:update
works.
On Oct 7, 2004, at 3:06 PM, Dain Sundstrom wrote:
On Oct 7, 2004, at 1:39 PM, David Jencks wrote:
On Oct 7, 2004, at 12:44 PM, Dain Sundstrom wrote:
On Oct 7, 2004, at 12:30 PM, David Jencks wrote:
Right, I was trying to use a checkout from the previous version of
maven.xml. I don't know why it
13 matches
Mail list logo
