I like the structure. Go ahead and reorg so I can add an example to
jpa-moxy. With GIT we are free to change our minds or tune the
structure without losing history so we don't have to over think
this.
And I don't think it's necessary to create the SDO directory until
we have content.
Shaun
On 16-04-2013 10:44 AM, Rick Barkhouse
wrote:
Hi all,
The JPA team has recently created an EclipseLink Examples git
repository and I'd like to propose that we do some organizing in
there. Currently it's a one-level directory of examples and I
think it would be good to get some structure before we start
adding more.
Somthing along the lines of:
examples.git
- jpa
- jpa-rs
- moxy
- jpa-moxy
- jpa-rs-moxy
- sdo
- dbws
jpa and moxy would contain jpa-only and moxy-only examples,
anything that combined the two would go into one of the "hybrid"
directories.
We don't need to add all of these directories now (for example may
not provide any SDO examples any time soon) but this demonstrates
the hierarchy.
Thoughts?
- Rick
--
Rick Barkhouse | Software
Developer, TopLink / EclipseLink | 613.288.4613
Oracle Development
45 O'Connor Street, Suite 400 | Ottawa, Ontario K1P 1A4
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
--
Shaun Smith | Senior Principal Product Manager
Oracle Cloud Application Foundation
- TopLink
Mobile: +1 416 558 6244
| Phone: +1 905 502 3094
ORACLE Canada | 100 Milverton Drive, Mississauga, Ontario | L5R
4H1
Oracle is committed to developing practices and
products that help protect the environment
|