Re: [JBoss-dev] trove.jar

2006-05-26 Thread Bill Burke



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 handled consistently across all uses.



Yes, the build system needs to be refactored so that the invidual 
modules have this information and it is easily maintainable on a 
per-project basis.  Our current implementation is not very object oriented.


Bill


---
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] trove.jar

2006-05-25 Thread Clebert Suconic
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 intermediate objects.
This forum here will explain why I decided to use trove:
http://www.jboss.com/index.html?module=bbop=viewtopict=79587


Right now, trove.jar only exists on /jboss-aop.deployer, and in an
installation without AOP, JBossSerialization won't work, and besides
that anyone using UnifiedInvokers with JBossSerialization will have to
manually add trove.jar on the client classpath.

So... Can we move trove.jar to /lib and /client?



---
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnkkid7521bid$8729dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


RE: [JBoss-dev] trove.jar

2006-05-25 Thread Scott M Stark
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 handled consistently 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, 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 
 intermediate objects.
 This forum here will explain why I decided to use trove:
 http://www.jboss.com/index.html?module=bbop=viewtopict=79587
 
 
 Right now, trove.jar only exists on /jboss-aop.deployer, and 
 in an installation without AOP, JBossSerialization won't 
 work, and besides that anyone using UnifiedInvokers with 
 JBossSerialization will have to manually add trove.jar on the 
 client classpath.
 
 So... Can we move trove.jar to /lib and /client?


---
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnkkid7521bid$8729dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


RE: [JBoss-dev] trove.jar

2006-05-25 Thread Clebert Suconic
I agree we need to take care of this on the installer.

But we are still distributing jboss as a ZIP bundle, and trove.jar is
only under /jboss-aop.deployer while jboss-serialization is part of
/client. It would be nice IMO if we could move it to a more generic
place. 

-Original Message-
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=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 handled consistently 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, 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 
 intermediate objects.
 This forum here will explain why I decided to use trove:
 http://www.jboss.com/index.html?module=bbop=viewtopict=79587
 
 
 Right now, trove.jar only exists on /jboss-aop.deployer, and 
 in an installation without AOP, JBossSerialization won't 
 work, and besides that anyone using UnifiedInvokers with 
 JBossSerialization will have to manually add trove.jar on the 
 client classpath.
 
 So... Can we move trove.jar to /lib and /client?


---
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications
in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=kkid7521bid$8729dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnkkid7521bid$8729dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


RE: [JBoss-dev] trove.jar

2006-05-25 Thread Scott M Stark
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
 
 I agree we need to take care of this on the installer.
 
 But we are still distributing jboss as a ZIP bundle, and 
 trove.jar is only under /jboss-aop.deployer while 
 jboss-serialization is part of /client. It would be nice IMO 
 if we could move it to a more generic place. 


---
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnkkid7521bid$8729dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development