Scott M Stark wrote:
This gets to this installer discussion thread:
http://www.jboss.com/index.html?module=bbop=viewtopict=83584
We need a common approach to defining how a component is integrated into
a distribution so whether a jar is an embedded aspect or a dependency in
the lib dir are
Both JBossSerialization and JBossAOP are using trove.jar, and on the
case of if JBossSerialization is being used for communication on
UnifiedInvokers, we need trove.jar on the client.
I used that thing to keep register of references so I could control
circular references without having to create
across all uses.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Clebert Suconic
Sent: Thursday, May 25, 2006 1:27 PM
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] trove.jar
Both JBossSerialization and JBossAOP are using trove.jar
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Thursday, May 25, 2006 6:08 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] trove.jar
This gets to this installer discussion thread:
http://www.jboss.com/index.html?module=bbop=viewtopict
The zip should also be created from the installer definitions.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Clebert Suconic
Sent: Thursday, May 25, 2006 9:35 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] trove.jar
