It looks like log4j-old.jar (which contains classes in org.log4j) is not
being referenced by any files in the jboss or contrib/log4j modules (except
log4j-old.jar).
So, it is *probably* safe to remove this file.
--jason
On Sun, 15 Apr 2001, Juha Lindfors wrote:
>
> Wanna take a look at the Ope
Hi,
On Mon, 16 Apr 2001, Jason Dillon wrote:
> Any preferences on how to continue? My bias would be to commit these
> changes soon, so I can move on to other bits. This will effect OpenJMS
> users, so we should probably add that to a release note also.
yeah I think you can commit it.. if peop
I think that I have finished moving the openjms specific fluff outside of
the main jboss module. I was able to run the mdbtest.sh script against the
JBossMQ provider, though I have not even tried to test the OpenJMS provider
classes. They are mostly unmodified, so I would expect them to continue
Hi,
On Sat, 14 Apr 2001, Jason Dillon wrote:
> Just to clarify, I should talk to Peter about adding a openjms contrib
> module.
Yes, he knows the code.
> And for the tests, this is from the jbosstest module... perhaps
> the bin/mdbtest.sh script?
Yep.
> Is there more documentation on this
Just to clarify, I should talk to Peter about adding a openjms contrib
module. And for the tests, this is from the jbosstest module... perhaps
the bin/mdbtest.sh script? Is there more documentation on this anywhere?
--jason
On Sun, 15 Apr 2001, Juha Lindfors wrote:
>
> Factoring out the open
Factoring out the openjms stuff from the server to a contrib module seems
like a good idea to me. Ping Peter Antman for comments/help (the email is
at SF) before commiting. Also run mdb tests from test module.
the log4j should be as easy as removing the log4j-old.jar from the cvs,
don't remove a
Ok, it looks like the OpenJMS is only referenced directly in these
files:
o src/main/org/jboss/jms/asf/OpenJMSServerSessionPoolFactory.java:
import org.exolab.jms.client.OpenJMSServerSessionPool;
import org.exolab.jms.client.JmsServerSessionPool;
org.exolab.core.logger.LoggerIfc
Wanna take a look at the OpenJMS stuff too? :)
It takes a meg in our package, and seems unnecessary as we use JBossMQ for
MDB.
The old log4j might be a good candidate for removal as well.
-- Juha
At 14:17 14.4.2001 -0700, you wrote:
>DependencyManager and jboss.dependencies have been removed.
DependencyManager and jboss.dependencies have been removed. I also
updated Main to remove the import of DependencyManager. I verified that
the system builds correctly and runs with no other modifications too.
--jason
On Sat, 14 Apr 2001, marc fleury wrote:
> |>From my investigation I would sa
|>From my investigation I would say that it is not being used anywhere
|inside of the jboss project. If this is true, it might be a good
|idea to at
|least remove the jboss.dependencies from the conf/default directory so that
|it does not confuse anyone.
correct,
|I think that the DependencyMan
> Oh you dont want to start a war againsee dev archives. Yes it is not
I sure don't.
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
>
> I think that the DependencyManager is a good one, so I would not be so
> quick to suggest that it be removed.
>
Oh you dont want to start a war againsee dev archives. Yes it is not
bad but I would say it is too explicit and verbose and doesn't do runtime
dependencies. It would be nic
ECTED]
Subject: RE: [JBoss-dev] DependencyManager & jboss.dependencies
why don't you figure it out?
let us know if it is depracated...
marc
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
|Dillon
|Sent: Friday, April 13, 2001 7:24
>From my investigation I would say that it is not being used anywhere
inside of the jboss project. If this is true, it might be a good idea to at
least remove the jboss.dependencies from the conf/default directory so that
it does not confuse anyone.
I think that the DependencyManager is a good o
I'm pretty sure it is...
but do take a look, just to make sure :)
-- Juha
At 19:23 13.4.2001 -0400, you wrote:
>why don't you figure it out?
>
>let us know if it is depracated...
>marc
>
>
>|-Original Message-
>|From: [EMAIL PROTECTED]
>|[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
>|D
No more poor doco excuses:
http://www.jboss.org/documentation/HTML/ch02s03.html
On 2001.04.13 19:23 marc fleury wrote:
> why don't you figure it out?
>
> let us know if it is depracated...
> marc
>
>
> |-Original Message-
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On
why don't you figure it out?
let us know if it is depracated...
marc
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
|Dillon
|Sent: Friday, April 13, 2001 7:24 PM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] DependencyManager & jboss.dependenci
17 matches
Mail list logo
