I jotted down some requirements for EclipseLink P2 related work for our
meeting.
Shaun
- Define and document all EclipseLink features, i.e., what bundles
they contain and what they depend on
- Although all EclipseLink features are defined as bundles, not
all should be included in features, e.g., meta model generation, ant
weaving tasks (when eventually extracted from JPA bundle)
- EclipseLink SDKto include all binary and source bundles
- EclispeLink SDK composite of existing features?
- EclipseLink SDK visible in both IDE and Target Platform software
install UIs
- EclipseLink SDK and sub-features visible both in categorized and
non-categorized views
- P2 Repository URLs for all releases (as applicable) documented on
download and release note pages
- EclipseLink Features for Helios available from both Helios P2 and
EclipseLink P2 repositories
On 14/4/2010 9:38 AM, Eric Gwin wrote:
I'm
adding some images I created that we will likely be talking about. For
remote attendees:
-Eric
David Twelves wrote:
We can use my conf call id for this meeting:
Time: Wednesday 14th, 10:00am EST
Meeting id: 9466105
Meeting passwd: 123456
Dial-in numbers: http://www.intercall.com/oracle/access_numbers.htm
For anyone in Ottawa, I have booked room 5012 (5th floor by kitchen)
- David
-----Original Message-----
From: eclipselink-dev-bounces@xxxxxxxxxxx
[mailto:eclipselink-dev-bounces@xxxxxxxxxxx]On Behalf Of Eric Gwin
Sent: Tuesday, April 13, 2010 1:01 PM
To: Dev mailing list for Eclipse Persistence Services
Cc: Ware, Tom
Subject: Re: [eclipselink-dev] EclipseLink "feature" layout for
Heliosonward...
Ok. I haven't confirmed with Peter, but it appears everyone else who
has responded can make 10am EST Wednesday (tomorrow), so let's plan for
that time. Since I don't have a conference ID, I'd like to volunteer
Peter's (the one we generally use for the EclipseLink Dev call), unless
only Shaun will be remote.
-Eric
Eric Gwin wrote:
Hello,
I'd like to have a quick discussion of our plans for our "feature"
layout for the Helios release and onward. There are several issues that
need to be resolved before the M7 freeze. I'm looking at Wednesday
(because I understand that is when Doug will be back) at 10. If you are
interested in attending but the time doesn't work let me know. The
afternoon around 1 should be good as well.
To give a quick overview of the major issues:
- we will need to remain compatible with our current scheme (3 product,
3 source features) for users of older installs
- There is a high level request to reduce our offering to a single sdk
(can easily be done by adding an sdk feature that depends upon the
others). Though there are questions about categorization of older
offerings.
- We have seen some bugs regarding our weaving bundle insinuating
itself upon an eclipse install and making all developed projects
dependent upon it (it is an OSGi fragment that Equinox will
automatically load if it is found). We need to work out a solution, and
determine its impact upon the above.
Any other issues that effect feature packaging will need to be worked
out before I can proceed with the composite repository process (Basics
are in place, but cannot be merged until the larger picture is
understood).
Thanks.
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
--
Shaun Smith | Principal
Product Manager
Phone: +19055023094
Oracle Server Technologies, Oracle TopLink
ORACLE Canada | 110 Matheson Boulevard West, Suite 100, Mississauga,
Ontario | L5R 3P4
Oracle is committed to
developing practices and products that help protect the environment
|
