openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-463) OpenJPA jar should self-describe its build information
Date Tue, 11 Dec 2007 03:12:43 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550286
] 

Patrick Linskey commented on OPENJPA-463:
-----------------------------------------

Good point. I still think that we should not make the default action be to print out the version,
since that will impact our future compatibility possibilities if we decide to ship a jar that
contains dependencies or Class-Path manifest entries or something.

> OpenJPA jar should self-describe its build information
> ------------------------------------------------------
>
>                 Key: OPENJPA-463
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-463
>             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.


Mime
View raw message