Re: C-JDBC rpm

[Emmanuel Cecchet <Emmanuel.Cecchet@xxxxxxxxxxxx>]

David,

> I see that for some reason c-jdbc targets a 1.3 jvm, but if 1.3 is not 
> needed then the dependency should be listed as jdbc-stdext, not 
> jdbc-stdext-ext. Then, if you install a JPackage 1.4 jdk you will get 
> this dependency satisfied. 

In fact, by default we compile our code for 1.3 but it compiles as well 
for 1.4. We think that a lot of users are still using 1.3 and therefore 
we ship by default a compiled version for 1.3. The main issue is that 
1.4 includes JDBC 3.0 which is not compatible with 1.3 (that's why we 
have some fake classes to allow JDBC 3.0 functionalities to compile with 
JDK 1.3).
Can we have separate binary packages for JDK 1.3 and JDK 1.4 with 
different dependencies?

> But, if you say that jdbc-stdext is not required to run at all (or 
> optional), I can remove it as a dependency.

Yes, this is optional, only for people who are using XAConnections or a 
DataSource. But in this case, they usually have an application server 
that already has the package.

> jgroups is in the free repository, but it depends on on-free jms. Both 
> jms and the 1.4 JDK (or jdbc-stdext-ext) are nosrc rpms in the 
> non-free repository. 

We are not using JMS at all in JGroups. Would it be ok to install 
JGroups without JMS?

> An odd thing about the law seems to be that most people think we are 
> not allowed to redistribute jms or jdbc-stdext, even though an 
> individual developer can bundle it with his application. Currently the 
> jboss rpm bundles non-free sun rpms, but I think that this is illegal, 
> and if I knew more, I would have to remove jboss from our site until 
> the dependencies are removed and put into the non-free repository. 

This is an interesting issue, I CC to the ObjectWeb architecture mailing 
list. We have a meeting of the college of architects this Wednesday, we 
will discuss the issue and let you know the outcome.

Thanks again for your prompt responses,
Emmanuel

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature