Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 15 Jan 2013 00:44:12 +0000 (UTC)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12612248.1350489366330.134029.1358210652620@arcas>
In-Reply-To: <JIRA.12612248.1350489366330@arcas>
References: <JIRA.12612248.1350489366330@arcas>
Subject: [jira] [Updated] (DERBY-5955) Prepare Derby to run with Compact
 Profiles (JEP 161)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-5955?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dag H. Wanvik updated DERBY-5955:
---------------------------------

    Attachment: derby-5955-add-cp2-to-jars.diff

Uploading patch derby-5955-add-cp2-to-jars.diff. This changes the top level=
 build.xml to add a new attribute to MANIFEST.MF in Derby's jar files:

Profile: compact2

This will ensure that if Derby is ever attempted run on a less capable plat=
form, i.e. compact1, java will issue an error informing the user that Derby=
 requires at least compact2 level.

Cf. this quite in http://openjdk.java.net/jeps/161:

"jar =E2=80=94 The JAR-file manifest specification will be extended with a =
new attribute which can be used to specify the minimum Profile required by =
the code in a JAR file."

In the current code line, the format used is the one shown above.

               =20
> Prepare Derby to run with Compact Profiles (JEP 161)
> ----------------------------------------------------
>
>                 Key: DERBY-5955
>                 URL: https://issues.apache.org/jira/browse/DERBY-5955
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation, JDBC, Services, SQL
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>         Attachments: apidiff.zip, client-graph.png, derby-5955-add-cp2-to=
-jars.diff, derby-5955-client-restructure-01.diff, derby-5955-client-restru=
cture-01.stat, derby-5955-client-restructure-02-delta.diff, derby-5955-clie=
nt-restructure-02.diff, derby-5955-client-restructure-02.stat, derby-5955-e=
mbed-restructure-01.diff, derby-5955-embed-restructure-01.stat, derby-5955-=
embed-restructure-02.diff, derby-5955-embed-restructure-02.stat, derby-5955=
-embed-restructure-03.diff, derby-5955-embed-restructure-03.stat, derby-595=
5-embed-restructure-04.diff, derby-5955-embed-restructure-04.stat, derby-59=
55-embed-restructure-followup.diff, derby-5955-embed-restructure-followup.s=
tat, derby-5955-new-non-jndi-ds-01.diff, derby-5955-new-non-jndi-ds-01.stat=
, derby-5955-new-non-jndi-ds-02.diff, derby-5955-new-non-jndi-ds-02.stat, d=
erby-5955-proof-of-concept-2.diff, derby-5955-proof-of-concept-2.stat, derb=
y-5955-proof-of-concept.diff, derby-5955-proof-of-concept.stat, derby-5955-=
ser.zip, embedded-graph.png, old-client-graph.png, old-embedded-graph.png, =
publishedapi.zip, publishedapi.zip
>
>
> While waiting for a Java module system (aka project Jigsaw), it has been =
decided to define a few subsets of the Java SE Platform Specification, cf J=
EP 161 ( http://openjdk.java.net/jeps/161).
> A quote from the JEP: "More broadly, this feature is intended to enable t=
he migration of applications currently built on top of the Java ME Connecte=
d Device Configuration (CDC) to appropriate Profiles of the Java SE Platfor=
m, part of the long-term effort to converge CDC with Java SE."
> It would be good if we make Derby to run on such limited profiles. The cu=
rrent proposal places JDBC in Compact Profile 2 (cf. link above), while oth=
er libraries used by Derby, e.g. javax.naming (JNDI) are in Profile 3 (larg=
er).
> It would be good if Derby could run on the smallest posible platform, i.e=
. Profile 2, but that will probably involve some changes to make Derby grac=
efully limit functionality when some libraries are missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira