Hi All, Geronimo has a version of the JPA spec jar as well. I've not reviewed it in a few weeks but its what Cayenne compiles against. Its Apache 2.0 licensed and thus removes any doubt about the usability. I don't know if it is any public m2 repo but I'm sure it could be added to the geronimo spec jars. http://svn.apache.org/repos/asf/geronimo/specs/branches/jee5_exp/ geronimo-spec-jpa/ is the url to the src. HTH, -bd- On Jun 15, 2006, at 8:05 AM, Patrick Linskey wrote: > I'm not sure. I don't really understand the legal subtleties between > manually typing up an interface while reading the spec vs. > including the > one supplied by the spec. I also don't understand legal issues > regarding > distributing a compiled jar provided by GlassFish (vs. distributing > Java > sources under the GlassFish licensing terms). Probably the answer to > this question will require reading the terms under which the compiled > jar is published. > > Certainly it'd be good if we could bundle what's in the spec, since > there are a couple of classes with meaningful logic in the spec jars > (javax.persistence.Persistence in particular). It's not hard to > replicate that behavior, but the bodies of the methods aren't provided > in the spec, so it's likely that a re-implementation of this would > be a > tad different than the spec impl. > > My guess is that we'll end up doing one of the following (listed in my > preference order): > > 0. ship with the GlassFish-provided jars > 1. re-implement the spec jars manually > 2. require users to download their own copy of the jars > > -Patrick > > -- > Patrick Linskey > BEA Systems, Inc. > >> -----Original Message----- >> From: Jongjin Choi [mailto:jongjin.choe@gmail.com] >> Sent: Thursday, June 15, 2006 1:38 PM >> To: open-jpa-dev@incubator.apache.org >> Subject: Re: Improving the Maven story for GlassFish >> >> If we use the spec api jars from glassfish maven repo, can we >> redistribute it within openjpa under Apache License? >> >> -- Jongjin >> >> On 6/15/06, Patrick Linskey wrote: >>> I think that we should not maintain a separate set of jars. >>> >>> -Patrick >>> >>> -- >>> Patrick Linskey >>> BEA Systems, Inc. >>> >>>> -----Original Message----- >>>> From: Craig.Russell@Sun.COM [mailto:Craig.Russell@Sun.COM] >>>> Sent: Wednesday, June 14, 2006 9:00 PM >>>> To: open-jpa-dev@incubator.apache.org >>>> Subject: Improving the Maven story for GlassFish >>>> >>>> Hi, >>>> >>>> Please note, the official spec jars and reference >> implementation of >>>> the Java Persistence are now available in the glassfish maven >>>> repository. >>>> >>>> We should talk about whether we want to have our own competing >>>> implementation of the spec jars since they now contain >> only the spec >>>> apis and not the TopLink implementation of the spec. >>>> >>>> To make it easier to discuss, here's the location of the >> glassfish >>>> java persistence maven repository. It includes the spec and >>>> implementation jars separately. >>>> >>>> https://maven-repository.dev.java.net/nonav/repository/javax.p >>> ersistence/ >>>> >>>> >>>> Craig >>>> >>>> Begin forwarded message: >>>> >>>> >>>> We just pushed a few more >> components >>>> to our maven repository (see >>>> >>>> >>>> http://blogs.sun.com/roller/page/theaquarium?entry=java_persis >>> tence_and_ejb_jars) >>>> >>>> and we will continue adding >>>> components, and I expect that, as part of >>>> >>>> GlassFish v2, we will normalize and >>>> automate the creation of these >>>> >>>> components. >>>> >>>> >>>> Craig Russell >>>> >>>> Architect, Sun Java Enterprise System >>>> http://java.sun.com/products/jdo >>>> >>>> 408 276-5638 mailto:Craig.Russell@sun.com >>>> >>>> P.S. A good JDO? O, Gasp! >>>> >>>> >>>> >>> >> _____________________________________________________________________ >> _ >>> _ >>> Notice: This email message, together with any attachments, may >>> contain information of BEA Systems, Inc., its >> subsidiaries and >>> affiliated entities, that may be confidential, proprietary, >>> copyrighted and/or legally privileged, and is intended >> solely for the >>> use of the individual or entity named in this message. If >> you are not >>> the intended recipient, and have received this message in error, >>> please immediately return this by email and then delete it. >>> >> > ______________________________________________________________________ > _ > Notice: This email message, together with any attachments, may > contain > information of BEA Systems, Inc., its subsidiaries and > affiliated > entities, that may be confidential, proprietary, copyrighted > and/or > legally privileged, and is intended solely for the use of the > individual > or entity named in this message. If you are not the intended > recipient, > and have received this message in error, please immediately return > this > by email and then delete it.