Ticket #298 (closed enhancement: fixed)

Opened 9 years ago

Last modified 8 years ago

Make JVM creation method generic

Reported by: hinerm Owned by: hinerm
Priority: minor Milestone: imagej-2.0-alpha5
Component: SCIFIO Version:
Severity: non-issue Keywords: BFITK
Cc: Blocked By:
Blocking:

Description

Currently in the BF-ITK plug-in, when a JVM is created the code is local to the module currently using the JVM. Ideally, we would have a single JVM creation method to facilitate simpler code maintenance.

This method should set all the appropriate options and accept 2 parameters - a dir and path string.

Change History

comment:1 Changed 9 years ago by hinerm

  • Owner changed from hinerm to curtis
  • Status changed from new to assigned

a jtools library has been added to Jar2Lib. Bf-cpp and bf-itk-jace have been modified to use this new library. However, it is not yet fully functional.

Desired modifications:

  • Allow for Jar2Lib to create a list of Jars to be automatically included if no classpath/jar list is provided
  • Allow for overriding the java library path

comment:2 Changed 9 years ago by curtis

  • Milestone changed from biweekly-2011: May-23 to Jun-03 to biweekly-2011: Aug-01 to Aug-12

comment:3 Changed 8 years ago by curtis

  • Owner changed from curtis to hinerm

Sorry Mark, I had no time to work on this. I am passing back to you. We can discuss whether it is really a priority, though.

comment:4 Changed 8 years ago by curtis

  • Milestone changed from biweekly-2011: Aug-01 to Aug-12 to imagej-2.0-alpha5

Milestone biweekly-2011: Aug-01 to Aug-12 deleted

comment:5 Changed 8 years ago by hinerm

  • Status changed from assigned to closed
  • Resolution set to fixed

jtools now automatically checks for a "jar" subdirectory, either in the working directory (if no classpath is provided) or in <classpath>/jar if a path is provided. All files in this directory are added to the classpath used to instantiate the JVM.

Note: See TracTickets for help on using tickets.