Bug 297711 - Build: default and dev-package-bundles target missing missing o.e.p.jpa.osgi jar for OSGI users in plugins dir
Summary: Build: default and dev-package-bundles target missing missing o.e.p.jpa.osgi ...
Status: RESOLVED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Eric Gwin CLA
QA Contact:
URL: http://dev.eclipse.org/mhonarc/lists/...
Whiteboard:
Keywords:
Depends on: 296269
Blocks: 316365
  Show dependency tree
 
Reported: 2009-12-14 02:51 EST by Michael OBrien CLA
Modified: 2022-06-09 10:03 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael OBrien CLA 2009-12-14 02:51:45 EST 
>We need an ant target that will generate the 6 separate bundle jars required by Glassfish V3 - so we can replace the jars with the latest split-bundled eclipselink.jar in the absence of overriding them on the classpath or domain.xml.
org.eclipse.persistence.antlr
org.eclipse.persistence.asm
org.eclipse.persistence.core
org.eclipse.persistence.jpa
org.eclipse.persistence.jpa.modelgen
org.eclipse.persistence.oracle
Comment 1 Eric Gwin CLA 2009-12-18 09:44:12 EST 
Is this really necessary? do we want to start adding high-level targets to the build for multiple usecases and configurations? Cannot Glassfish use a custom buildfile to call the component build scripts themselves? I want to understand the need before I impliment the solution.
Comment 2 Michael OBrien CLA 2009-12-18 09:50:44 EST 
>Yes, forgot about glassfish.xml in eclipselink.jpa.test - this is a better place for a custom build-eclipselink-jar target - not in the main build.
Comment 3 Eric Gwin CLA 2009-12-18 10:02:31 EST 
So we don't need this? Will you withdraw the bug? or am I misunderstanding?
Comment 4 Doug Clarke CLA 2009-12-18 10:16:11 EST 
Marking as WORKSFORME until further specific details can be added explaining what is needed and why.
Comment 5 Michael OBrien CLA 2010-05-02 21:10:19 EDT 
>indirect user request for split jars to override shipped 6 with GlassFish V3
http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg04525.html
Comment 6 Michael OBrien CLA 2010-06-09 15:48:05 EDT 
>actually there is an existing dev-package-bundles that we can use on the root that writes to <trunk>/bundles in the form
    <target name="dev-package-bundles" depends="clean-runtime-checkedin">

F:\view_w35f\plugins\org.eclipse.persistence.antlr_2.2.0.qualifier.jar
F:\view_w35f\plugins\org.eclipse.persistence.asm_2.2.0.qualifier.jar
F:\view_w35f\plugins\org.eclipse.persistence.core_2.2.0.qualifier.jar
F:\view_w35f\plugins\org.eclipse.persistence.jpa_2.2.0.qualifier.jar
F:\view_w35f\plugins\org.eclipse.persistence.oracle_2.2.0.qualifier.jar
>non-standard
F:\view_w35f\plugins\org.eclipse.persistence.jpa.modelgen_2.2.0.qualifier.jar
Comment 7 Michael OBrien CLA 2010-07-23 07:31:55 EDT 
>We are missing the following OSGI library in the [plugins] dir for users who upgrade via OSGI
Adrian and an EclipseLink user discovered this.
I did not previously get this because I manually upgraded my Glassfish and NetBeans releases instead of using OSGI.

equinox.lib=org.eclipse.osgi_3.6.0.v20100517.jar
for

org.eclipse.persistence.jpa.osgi_2.2.0.qualifier.jar

>see posts
http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg04642.html
Comment 8 Michael OBrien CLA 2010-07-26 07:25:08 EDT 
>My mistake the target builds the osgi jars when the configuration is set
       <ant antfile="build.xml" dir="${eclipselink.osgi}"             target="jar"/>
       <ant antfile="build.xml" dir="${eclipselink.equinox}"          target="jar"/>
Comment 9 Eclipse Webmaster CLA 2022-06-09 10:03:05 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink