db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3031) Improve Derby core plugin packaging & structure (solving MANY problems)
Date Fri, 29 Feb 2008 20:40:51 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dyre Tjeldvoll updated DERBY-3031:
----------------------------------

    Derby Info:   (was: [Existing Application Impact])

> Improve Derby core plugin packaging & structure (solving MANY problems)
> -----------------------------------------------------------------------
>
>                 Key: DERBY-3031
>                 URL: https://issues.apache.org/jira/browse/DERBY-3031
>             Project: Derby
>          Issue Type: Improvement
>          Components: Eclipse Plug-in
>    Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4
>         Environment: Any eclipse supported platform, rcp product, webstart-rcp-product
>            Reporter: Dominik Wagenknecht
>
> There are some problems with the current packaging of the core plugin. Since eclipse
3.3 it is highly recommended to package plugins as "jar packages". Additionally all current
eclipse plugins come jar'd and signed!
> I propose the following packaging:
> - Split plugin into several plugins. One plugin per old jar included -- this way a plugin
is a JAR and not a plugin-folder with n jars in it
> - These plugins need their requirements and exports set right thus separating db-server
from client-libraries and so on (reduce size)
> - Add a feature to get "full" derby support with branding (better representation is never
a bad idea)
> Why?
> - Conform with eclipse. No more plugin-folders. No update-manager hassles. No RCP developer
problems
> - When jar's are signed webstarting automatically works.
> - Feature for better representation & update manager support (preferred installation
method nowadays)
> - much lighter footprint
> How?
> - "inject" MANIFEST.MF into existing single jar's, renaming them to conform "eclipse-style"
with version indicator (as multiple plugin versions are supported)
> - provide download zip with "feature" and "plugins" directories where the feature/plugins
live in
> This solves the following long-standing bugs:
> http://issues.apache.org/jira/browse/DERBY-2175
> http://issues.apache.org/jira/browse/DERBY-631
> ...and includes...:
> http://issues.apache.org/jira/browse/DERBY-1488
> I always wanted to report this, because currently I'm repackaging every derby update
to keep my software running...so is this feasible??
> Thank you & Greetings from Vienna!

-- 
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