[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug crypto/27649] Addition of --standalone-crypto configure option

From: raif at swiftdsl dot com dot au
Subject: [Bug crypto/27649] Addition of --standalone-crypto configure option
Date: 18 Jun 2006 07:21:03 -0000

------- Comment #5 from raif at swiftdsl dot com dot au  2006-06-18 07:21 
(In reply to comment #3)
> Please refer to the patch in:
> http://developer.classpath.org/pipermail/classpath-patches/2006-June/002696.html
> In combination with the earlier patch, the requirements for this enhancement
> are met. Perhaps we would prefer providers split up into smaller jars? Anyway,
> the above patch should provide a good starting point.

i am not on IRC, so forgive me if this has been discussed there, but could you
briefly explain the benefit of replacing the dependency on SystemProperties to
a dependency on gnu.java.security.action?  specifically, how can that achieve
the goal of producing standalone providers (i.e. for use by VMs not using GNU

what would be very helpful is to be able to produce, at least, two separate
jars: one containing the strong stuff (classes and algorithms in
gnu.javax.crypto), and another for Jessie.  this can be of immediate use to
those packaging GNU Classpath with their applications under export-restricted

achieving this is much simpler since any dependencies on the main GNU Classpath
classes can remain as-is, and the problem is reduced to:

a. producing 3 or more jars (incl. the main GNU Classpath one), and
b. ensuring that classes from the additional jars are found at runtime.

does this sound reasonable?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]