This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: java.security.AlgorithmParamterGenerator.java


>>>>> "Raif" == Raif S Naffah <raif at fl dot net dot au> writes:

Raif> q/ since most of these are for new methods and some for new classes and 
Raif> interfaces, is there a special procedure to specify this in the Mauve 
Raif> tests; ie. include the new tests iff the new classes/interfaces/methods 
Raif> are checked out?

Did you get an answer to this?  (I haven't checked my mauve inbox
recently...)

In general I think we just add the new tests.  If a given
implementation can't compile them, they can disable the test easily
enough.  It's friendly to put the new tests in a new file.  And if the
method or class was added in some particular JDK version, tag the file
that way.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]