Currently EclipseLink can be used as an all in one, or specific
bundles can be used to make a more customized install. So you can
just get one or the other, although I think the typical case is to
still use the eclipselink.jar.
We also have 2 consumers for our packaging, which includes users and
adopters. We have adopter requirements to allow for easy removal of
JAXB related functionality (as well as EclipseLink related
functionality), so at this level we will need to have a separate
feature for JAXB functionality. We could have layered features to
provide better package options for users. Something like:
Dali JPA Feature
-> Dali JPA Generic Feature
-> Dali JPA EclipseLink Feature
Dali JAXB Feature
-> Dali JAXB Generic Feature
-> Dali JAXB EclipseLink MOXy Feature
Neil
On 9/29/2010 2:50 PM, Brian Vosburgh wrote:
I guess it depends on what a user typically wants:
Would s/he want to pick our EclipseLink "product" and it comes
with everything?
I guess this would depend some on how EclipseLink itself is
packaged? Can you
get just EclipseLink JPA? Just EclipseLink
JAXB? If you can't, then it would
make no sense for us to break up our EclipseLink support. (?) I
don't have
strong feelings (yet :) ), but it just seems like this is a
reversion of what
we just did; or am I confused? I can't remember how exactly we
changed
the package names then.... (And the old packages were not
archived on
CVS. Or I can't find them.)
On 09/29/10 14:08, Neil Hauge wrote:
We discussed this briefly this morning (unfortunate that you had
a conflict) . The best documentation of this I could find was
in these notes:
http://wiki.eclipse.org/Dali_Project/Weekly_Meeting/August_20_2010
Not much related to o.e.jpt.eclipselink there, but thinking
about it now, it seems that the 2 main distinctions in our code
base will be ORM and OXM (JPA and JAXB). Generic or EclipseLink
seems like a secondary distinction, below the two base
components, but we can discuss further here and/or tomorrow
morning.
Neil
On 9/29/2010 1:29 PM, Brian Vosburgh wrote:
I thought we discussed a while back that all the
EclipseLink code would be under
o.e.jpt.eclipselink and not spread across various other
branches. It almost feels like
this is doing just the opposite of what we did as a result
of that discussion?
On 09/29/10 10:40, Paul Fullbright wrote:
A
new plugin:
org.eclipse.jpt.jaxb.core
has been added, and an existing plugin:
org.eclipse.jpt.eclipselink.jaxb.core.schemagen
has been renamed to:
org.eclipse.jpt.jaxb.eclipselink.core.schemagen
Those and the existing plugins:
org.eclipse.jpt.jaxb.ui
org.eclipse.jpt.jaxb.core.schemagen
have been added under a new "jaxb" component under
org.eclipse.jpa in CVS.
The existing jaxb plugins under the "jpa" component have
been replaced with stub projects.
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
|