openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pinaki Poddar (JIRA)" <>
Subject [jira] Commented: (OPENJPA-463) OpenJPA jar should self-describe its build information
Date Tue, 11 Dec 2007 17:05:43 GMT


Pinaki Poddar commented on OPENJPA-463:

The enhancement request is to make openjpa jar a self-describing not a self-executing archive
(which requires a broader scope of discussion).  
Given the impressive array of tools/features/configuration supported by OpenJPA, using a Main-Class
as a multi-prong swiss knife such as 
$ java -jar openjpa.jar -enhance 
$ java -jar openjpa.jar -map
does not appeal to me mainly because the sheer explosion of its possible command-line options
and arguments. 

The scope of self-description can be broaden to include other manifest information (e.g. Class-Path),
explicit dependencies, patch information etc. But, overall, it should be informational, not
an execution vehicle.  

> OpenJPA jar should self-describe its build information
> ------------------------------------------------------
>                 Key: OPENJPA-463
>                 URL:
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: build / infrastructure
>            Reporter: Pinaki Poddar
>            Priority: Minor
> End user should be able to do:
> $ java -jar /path/to/openjpa.jar
> To get a self-description of OpenJPA
> Currently, org.apache.openjpa.conf.OpenJPAVersion does output useful information. 
> This enhancement request is to mark org.apache.openjpa.conf.OpenJPAVersion as the Main-Class
in manifest.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message